Versions Compared

Key

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

...

One way of organizing constant values is combining them in a singleton entity. Of course the attributes of this entity do not share any commonality, except for the fact that they are constants. Business engineers that uphold strict rules of elegant modeling might frown upon such an entity, whereas the more pragmatic business engineers favor one particular space in the business model where all constants are stored and managed.

Image Removed

Image Added

Attributes, set by a single decision table

Another way of organizing constant values is setting them in one single decision table, while the constants themselves are declared wherever the business engineer thinks they belong. This scenario can also be used when using a one entity to store all constants together. The default value of these constants is left out, but one (or perhaps even more) decision table sets the values.

Image Removed

Image Added

Reusable expressions

Perhaps the most intuitive way of organizing constant values is setting them in reusable expressions. The main reason many business engineers favor this option is that some constants do not belong to an entity. Reusable expressions - used in this manner - are "orphaned" single-valued-attributes; they have the most in common with actual constants.

Image Removed

Image Added

One might argue in favor of using any of the three scenarios discussed here. Other scenarios may be possible as well. There is one con that the three scenarios mentioned here have in common: It is not possible to add a justification for default values and for reusable expressions. Decision tables can have a justification, but only for the complete set of derived attributes (i.e. for one column). If a justification for each constant is necessary, a business rule (or even a decision table) for each constant would work.

...

See the example below where the maximum amount of savings is not declared as a constant. The value 27500 is merely used in a decision table to determine if an applicant does not have too much savings.

Image Removed

Image Added

Of course the decision shown above could also have been modeled using a constant default value combined with a business rule or a default value expression, as shown below.

Image Removed

Image Added

Image Removed

Image Added

Using a default value expression:

Image Removed

...

Image Added

 



Panel
Section
Column
width50%

Main chapter: Design considerations

Previous: Dealing with multiple versions of logic

Column

Next: Local variables

 

...