Software programmers are used to a procedural approach when it comes implementing Business requirements. The consequence is that the business rule implementation solely depends on the competence and understanding the software developer has of the Business Rules he has to implement. This limitation was already seen and identified by researches. Object oriented programming may be seen as "the solution" to business implementation and agility and many developers rely on this paradigm. In the end, Object oriented approach ends up with the classical "Spaghetti code". To avoid this ending, a new approach was taken called "declarative programming". This is a big shift and we shall try to focus on that before learning the tooling around drools.

  • the first set of tutorials called "drools tutorials" start from the base concepts (there are few and is concentrated on the core engine) up to more language concepts

  • the second set of tutorials called "BRMS tutorial" will introduce the management tooling (called workbench) around the lifecycle of the rule artifact. but the workbench also introduces more artifacts type like decision table, rule templates, etc.. that will help when modeling business requirements.

  • the third set of tutorials called "BRMS runtime tutorials" starts to introduce possible software architectures in a real project. In our exercise, we will use the ideas that we describe in that part.

Last updated