4.2. DMN decision requirements diagram (DRD) components
A decision requirements diagram (DRD) is a visual representation of your DMN model. A DRD can represent part or all of the overall decision requirements graph (DRG) for the DMN model. DRDs trace business decisions using decision nodes, business knowledge models, sources of business knowledge, input data, and decision services.
The following table summarizes the components in a DRD:
表4.1 DRD components
| Component | Description | Notation | |
|---|---|---|---|
| Elements | Decision | Node where one or more input elements determine an output based on defined decision logic. |  |
| Business knowledge model | Reusable function with one or more decision elements. Decisions that have the same logic but depend on different sub-input data or sub-decisions use business knowledge models to determine which procedure to follow. |  | |
| Knowledge source | External authorities, documents, committees, or policies that regulate a decision or business knowledge model. Knowledge sources are references to real-world factors rather than executable business rules. |  | |
| Input data | Information used in a decision node or a business knowledge model. Input data usually includes business-level concepts or objects relevant to the business, such as loan applicant data used in a lending strategy. |  | |
| Decision service | Top-level decision containing a set of reusable decisions published as a service for invocation. A decision service can be invoked from an external application or a BPMN business process. |  | |
| Requirement connectors | Information requirement | Connection from an input data node or decision node to another decision node that requires the information. |  |
| Knowledge requirement | Connection from a business knowledge model to a decision node or to another business knowledge model that invokes the decision logic. |  | |
| Authority requirement | Connection from an input data node or a decision node to a dependent knowledge source or from a knowledge source to a decision node, business knowledge model, or another knowledge source. |  | |
| Artifacts | Text annotation | Explanatory note associated with an input data node, decision node, business knowledge model, or knowledge source. |  |
| Association | Connection from an input data node, decision node, business knowledge model, or knowledge source to a text annotation. |  | |
The following table summarizes the permitted connectors between DRD elements:
表4.2 DRD connector rules
| Starts from | Connects to | Connection type | Example |
|---|---|---|---|
| Decision | Decision | Information requirement |  |
| Business knowledge model | Decision | Knowledge requirement |  |
| Business knowledge model |  | ||
| Decision service | Decision | Knowledge requirement |  |
| Business knowledge model |  | ||
| Input data | Decision | Information requirement |  |
| Knowledge source | Authority requirement |  | |
| Knowledge source | Decision | Authority requirement |  |
| Business knowledge model |  | ||
| Knowledge source |  | ||
| Decision | Text annotation | Association |  |
| Business knowledge model |  | ||
| Knowledge source |  | ||
| Input data |  |
The following example DRD illustrates some of these DMN components in practice:
図4.1 Example DRD: Loan prequalification
The following example DRD illustrates DMN components that are part of a reusable decision service:
図4.2 Example DRD: Phone call handling as a decision service
In a DMN decision service node, the decision nodes in the bottom segment incorporate input data from outside of the decision service to arrive at a final decision in the top segment of the decision service node. The resulting top-level decisions from the decision service are then implemented in any subsequent decisions or business knowledge requirements of the DMN model. You can reuse DMN decision services in other DMN models to apply the same decision logic with different input data and different outgoing connections.
