Page History

...

Decision
Between the decision tags, the DRG components are placed to identify and determine the decision.
The name attribute of the decision refers to an entity attribute where a decision had to be made for.
The id attribute uniquely indentifies the decision in the entire diagram.
Inside the decision other default and custom XML components are included. The custom components can be indentified by the bq prefix.
The value element contains the value after determination of the decison.
To determine a decision, information is needed. To accomplish this, "informationRequirement" tags are included inside a decision.
The "informationRequirement" tags point on their way forth to input data ("inputData") or other decisions ("decision").

For determining a decision, logic is needed. This logic can come from different sources, for example a decision table, bussiness rule, default rule etc.
To indicate which logic is used to determine the decision, a "knowledgeRequirement" tag is placed inside the decision.
For example the entity attribute "RequiredMonthlyInstallment where are DRG is made for, uses a default rule ("A rule that is linked to this attribute and evaluated each time a underlying component changes.").

When an entity attribute contains a justification text, it will also be displayed inside the DRG graph and the XML variant.
In XML this text is displayed between the "JustificationText" start and end tags inside a decision.

BusinessKnowledeModel
Inside the name attribute of the BusinessKnowledeModel the name of a logic component, such as a decision table, default rule, bussines rule is placed.

InputData
The data that is direct available is  placed inside the "InputData" element tags.

The metamodel of a DMN element

...