Page History

Example Decision Requirements Graph

XML representation

In the example decision requirements graph (DRG), the decision was made on the amount of a monthly installment. When storing this decision in the trace engine, an XML representation of that decision is generated. The XML document contains the entire DRG from the image shown above. All the XML components for a single DRG are placed between the definitions start and end tag.

...

XML representation of the decision requirements graph shown above.

Decision

Between the decision tags, the DRG components are placed to identify and determine the decision. The attribute name of the decision refers to an [entity.attribute] that was subject to a decision. The id attribute uniquely identifies the decision in the entire diagram. Inside the decision other default and custom XML components are included. The custom components can be identified by the bq prefix. The value element contains the value after determination of the decision. To determine a decision, information is needed. To accomplish this, informationRequirement tags are included inside a decision. These tags point on their way forth to input data (inputData) or other decisions (decision).

...

When an 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.

Business knowledge model

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

Input data  

The data that is set by the user is placed inside the InputData element tags.