Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Image Removed  This chapter discusses what to do when working with lots of (logic) elements and multiple versions of logic.toc

Lots of logic

When projects grow bigger, the need to neatly organize the model grows accordingly, especially concerning logic elements. Dealing with large numbers of decision tables, business rules etc. can become a challenge. It is possible to use clusters. A cluster is a global element that can be created in the menu Globals and is a word (label) that can be chosen at will. labels. One or more labels can be assigned to one or more elements. 

Examples of meaningful clusters labels are "Housing benefit eligibility" and "Housing benefit amount" in a housing benefit model or at a more specific level "Income", "Rent" and "Savings". A cluster in itself is just a word and A label has no function other than representing a logical group of elements. Clusters Labels are not present in the project export and have therefore no effect in the runtime. Labels can be created from various perspectives, like a logical functional unit, a specific task, a specific product or a specific decision.

Image Removed

Image Removed

Clusters Labels appear in the lists of elements and can be filtered and sortedmodule elements as expansion panels.

Image RemovedImage Added

The All module elements that can be clustered are:

  • Decision tables
  • Business rules
  • Reusable expressions
  • External rules
  • Decision trees

Multiple versions

When logic changes, e.g. due to new legislations, multiple versions of logic might be modeled. Rule groups are a means to accomplish this. They are groups of logical elements than can be conditional. Therefore, they allow the business engineer to choose when to apply which set of logic elements, since the logic elements that are part of a rule group will only be applied when the pre condition set on the rule group is true.

Image Removed

can be labeled. 

Panel
Section
Column
width50%

Main chapter: Design considerations

Previous: Setting a business valueMultivalued attributes in decision tables

Column

Next: Constants Dealing with multiple versions of logic