Page History

Within organizations decisions are made frequently and have an important impact on reaching the organizations goals. Decisions are made using logic, even if that is not always obvious. There are many organizations that have automated their operational decision making. Blueriq is a platform that is often used to make decisionsautomate (parts of) the decision making process.

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

...

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 Blueriqs DRG differ from the standardThis means that Blueriq generates a DRG at design time in Studio, based on the decisions and sub decisions that have been modeled. Furthermore, Blueriq offers a DRG in design time and a slightly different DRG in runtime.

For more info on DRGs see Project modeling - Decision Requirements Graph (DRG) [9.3].

...

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 DRGs see Project modeling - Decision Requirements Graph (DRG) [9.3])

...

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

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

Runtime Decision Requirements Graph

...