You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
What is it for?
The Decision Requirements Diagram (DRD) is used to get a graphical overview of how a particular attribute is derived.
Opening a Decision Requirements Diagram
A DRD can be opened using one of the options listed below:
- Click the
icon in the attribute screen (located beside the unit test icon). - Click the icon in a logic element such as a business rule, decision table, external rule, or data rule.
Shapes in a Decision Requirements Diagram
| Name | Shape | Description |
|---|---|---|
| Decision |
| All attributes that are used in the inference path to set a value for the main decision are displayed as a decision. The name of the decision is the functional name when available. Otherwise the (technical) name is used. |
| Business knowledge |
| A reference to the logic, that will be used to answer the question for the decision. The name of the business knowledge model is the functional name of the used logic element, when not available the (technical) name is used. A default expression gets the name: Expression A default constant gets the name: Constant |
| Input data |
| The input data displays a list of attributes that can not be derived (user inputs) and that can be used by the knowledge element to set derive a value for the decision. |
Example Decision Requirements Diagram in Blueriq Encore
In the example DRD above, a main decision is made based on 5 sub decisions.
- The main decision is a boolean value and uses a decision table to derive its result which uses six different input values.
- Even though the knowledge nodes for sub decision 1 are collapsed, we can see it uses a default attribute value and a business rule to derive its result.
- Sub decisions 2-5 use default attribute values to derive their result.
Quick test and the Decision Requirement Diagram
It is possible to source an attribute using a quick test while viewing a DRD. In this case, all Blueriq Elements that are 'hit' during sourcing will be highlighted:
Overview
Content Tools