The merger of Lawson and Intentia in 2006 left developers with an important problem to solve - the integration and presentation of legacy applications and business services that are constructed in Java, .NET, and other technologies. This case study looks under the hood at the new architecture at Lawson and how they got there.
Boris Lublinsky and Didier Le Tien discuss how business process engines and business rule engines differ, where their respective strengths are and when to use what in an SOA context. They discuss commonalities and differences between business rules and business processes and present some guidelines on positioning business rules in SOA implementation and appropriate usage of each technology.
James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.
Geoffrey Wiseman explains rules engines and shares practical experiences applying them with Drools in financial services. 13