Versions Compared

Key

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

...

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 each constant. After all, default values do not have justifications, neither do 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 per for each constant is necessary, a decision table business rule for each constant is the only optionwould work.

None

Another possible scenario is to not gather constants at all and just make use of the values that are affiliated with these constants. The con of this approach is clear: when a constant is changed, you will have to update each occurence of that constant in your model.

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.

...