Versions Compared

Key

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

...

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

Table of Contents

Decision Requirements Graph (

...

DRD)

Blueriq adopted the Object Modeling Group (OMG) standard of Decision Model and Notation (DMN) with regards to the Decision Requirements Graph Diagram (DRGDRD). This means that Blueriq generates a DRG DRD at design time in StudioEncore, based on the decisions and sub decisions that have been modeled. Furthermore, Blueriq offers a DRG DRD at design time and a slightly different DRG at runtime.

For more info on DRGs see Project modeling - Decision Requirements Graph (DRG).see Decision Requirements Diagram or DRD in Encore

Design time Decision Requirements

...

Diagram

When designing a decision, make use of the Decision Requirements Graph Diagram (DRGDRD), depicted by a scale icon:.
(for more info on and where to open DRGs see Project modeling - see Decision Requirements Graph (DRG)Diagram or DRD in Encore)

Let us 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 StudioEncore, use Ctrl-click on the various elements to open them and verify that the discount is modeled correctly.

...

Although even for simple decisions the DRG DRD is useful while designing or reviewing, the true strength of the DRG DRD is exemplified when designing or reviewing multi-layered complex decisions. See the example DRG DRD below, that shows the decision that determines Strategy. At level 1 this decision looks trivial.

...

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 DRGsDRDs. Shown below is such a DRG DRD for the sub decision Bureau call type.

...

In the examples above, knowledge sources are shown. These knowledge sources appear in a DRG DRD when a specification is linked to a decision (decision table, business rule, attribute with expression, etc.).

...

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 graphdiagram, but differs mainly with regards to the fact that it shows all given answers and derived values. See the example below.

...