Versions Compared

Key

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

Image Removed  This chapter discusses the use of decisions throughout Blueriq. Some best practices in designing decisions are discussed, followed by typical examples of the logic constructs in Blueriq.

...

1Main

Ask yourself the question what the main decision is. If you think of more than one answer, split these decisions if possible.
For instance, if you main decision is "the amount and duration of a child care benefit" or "the fee for a small building permit" you are are actually modeling two decisions. Design them separately and reuse attributes that accommodate both decisions.

2Sub
decisions
For each identified decision, determine if the decision is preferably built up out of meaningful sub decisions. These sub decisions could be reusable decisions - in fact reusable decisions will most likely be sub decisions - but not every sub decision has to be a reusable decision.
Think of a complex calculation where intermediate results are never reused but are created nevertheless, for the sake of understandability.
3CircularityAvoid circularity. When decision A depends on the outcome of decision B and decision B needs the result of decision A as input, you're in trouble! When designing decisions top-down circular references can easily be avoided.
note
UI Text Box
type
Info

Note that a decision is not bound to be a Boolean. In general, there are three types of decisions:  Image Removed  

  • Boolean decision (you are eligible for benefit X),
  Image Removed  
  • Classification (you will receive category 'medium' for benefit X) or
  Image Removed  
  • Calculation result (you will receive € 100,- per year for benefit X).

Typical examples

In this paragraph typical examples of Blueriq's logic contructions are given.
Of course it is subject to discussion whether one logic construction or another is used best, but that will be discussed in chapter Design considerations.

...

A typical example of a business rule is a rule that has a boolean as result. Let's say that any applicant can request a certain insurance, and all women receive a discount. In this particular case, a default constant value for Discount is set to False and a business rule can be created that overwrites this attribute to true whenever the applicant is female:

Info
icon

...

Image Removed

...

false

Image Added   Image Added


Decision table

A decision table is used best when the possible outcome of the logic is one of many values. Let's say that when applying for a certain loan, a risk category is determined. Based upon applicant characteristics such as recurrence and a calculated risk score, the risk category is either very low, low, medium, high or decline.

...

Info
iconfalse

Image Added

For more information on Decision tables and Business rules, see

...

A default value, combined with an expression, is used most often when the outcome of the logic is determined/calculated by some sort of formula. See an example below, where the required monthly installment is determined by a formula containing - amongst others - monthly interest and monthly fee.

...

Info
iconfalse

Image Added

There are two typical scenarios in which default value expressions are used:

...

See How to use a data rule to derive attribute values. 


Panel
Section
Column
width50%

Previous: Decision management in Blueriq

Column

Next: Design considerations