Page History

...

This chapter discusses how decision management is supported in Blueriq by means of Decision Requirements Graphs.

Decision Requirements Graph (DRG)

Blueriq adopted the Object Modeling Group (OMG) standard of Decision Model and Notation (DMN) with regards to the Decision Requirements Graph (DRG).
However, some constructs in Blueriq's DRG differ from the standard. Furthermore, Blueriq offers a DRG in design time and a slightly different DRG in runtime. For more info on DRG's see Decision Requirements Graph (DRG) [9.3].

Design time Decision Requirements Graph

When designing a decision, make use of the Decision Requirements Graph (DRG), depicted by a scale icon:.
(for more info on and where to open DRG's see Decision Requirements Graph (DRG) [9.3])

Let's say we are modeling a simple decision that determines whether someone will receive a discount on some sort of insurance.
Females are eligible for this discount, males are not. The decision requirements graph will probably look something like the one shown below.
In Studio, use Ctrl-click on the various elements to open them and verify that the discount is modeled correctly.

...

It is possible to completely expand all decisions, knowledge models, input data and sources in one single graph, but this will most likely result in a diagram that is not usable for any type of audience. Therefore it is advised to expand sub decisions in separate DRG's. Shown below is such a DRG for the sub decision Bureau call type.

Runtime Decision Requirements Graph

Although OMG´s standard DMN does not contain any specifications for it, Blueriq also uses a runtime decision requirements graph. This graph resembles the design time decision requirements graph, but differs mainly with regards to the fact that it shows all given answers and derived values. See the example below, also about the risk score example.

...