This chapter discusses the use of logic throughout Blueriq. The role of decision requirements graphs when designing and running is discussed, followed by prime examples of logic constructs in Blueriq.

Using Decision requirements graphs when designing

text

Using Decision requirements graphs when running

text

Prime examples

In this paragraph prime 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 4. Design considerations.

Business rule

A prime 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:

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 recurrenc and a calculated risk score, the risk category is either verylow, low, medium, high or decline.

Default value expression

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. In most cases, the result will be a number, date or constructed string. See an example below, where the required monthly installment is determined by a formula containing - amongst others - monthly interest and monthly fee.

Data rule

text