Standards families
DMN decision requirements diagram
Decisions, input data and knowledge sources as nodes; information-requirement arrows saying what each decision needs.
dmn.drd@1New DDN source
Why use it?
The DRD is the table of contents for the decision logic — reviewers can demand to see every input's source.
When it helps
Before writing the decision tables: agree what is decided from what.
How to read it
- Rectangles are decisions, ovals are input data; arrows point from requirement to the decision that requires it.
- Variants open the actual decision tables behind two of the decisions.
What you need
- The decisions
- The input data
- The authority (knowledge sources)
Things to check
- Do not let a decision read data that never enters the diagram.
- A decision nobody requires is dead logic — delete it or wire its consumer.
Scope of this diagram
Declared requirements graph with reference validation; the tables' logic is validated separately (see the decision-table chapters).
Work with the converted example
- Open the viewer and select
drd. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.