This chapter discusses typical design considerations when designing and implementing decisions using Blueriq.

Setting a boolean value?

Blueriq offers multiple possibilities to set a value for a boolean result, these are listed below:

1. Using a constant value and a business rule to set the contrasting value if a condition is true.

2. Use two business rules that set a value

     

3. Using a decision table

   It is tempting to skip the column for male, but it is advised to model a complete table.

What to use?

The choice of method is often based on the preference of the business engineer. But the recommendations are listed below:

1. When the result is dependent on multiple input values, use the decision table
2. When the result is dependent on a calculation use a form with a business rule
3. Make an agreement in an architecture document which form to use. A consistent use of a style throughout a project will help the maintainability of a project.

Gaan we hier een echte voorkeur uitspreken???? ik vind de decision table het netste

Size of decision table

With multiple inputs or value categories decision table can get very large in size. Decision tables that are to large in size are not easy to oversee and by that to understand. In general you can state that a table should have a maximum of 12 columns. When the number of columns exceeds this number it is advised to split up the table. 

Decision table or data rule?

text

Attributes and (reusable) expressions

text

Decisions in a process?

text