-
Key: DMN11-47
-
Status: closed
-
Source: Bruce Silver Associates ( Mr. Bruce Silver)
-
Summary:
In the chapter 11 example, Fig 63 contains an information requirement connector linking Adjudication to Routing. But in reality Routing is not an input to Adjudication. What is meant is that Adjudication is only performed if Routing has certain output value. That relationship is what Vanthienen calls an action subtable, whereas information requirement reflects a condition subtable relationship. Still it is useful to depict such relationships in DRD. I suggest adding a new connector type, association - an artifact as meant by BPMN, i.e. no operational semantics just annotation - to reflect it. A text label could indicate a particular output value that enables the dependent decision.
-
Reported: DMN 1.0 — Tue, 28 Apr 2015 21:20 GMT
-
Disposition: Closed; No Change — DMN 1.1
-
Disposition Summary:
Close - no change required
Consensus is not to add new type of information requirement connector.
-
Updated: Tue, 29 Mar 2016 15:07 GMT
DMN11 — Add association connector (artifact) with text label to represent conditional decision
- Key: DMN11-47
- OMG Task Force: Decision Modeling and Notation 1.1 RTF