-
Key: DMN12-45
-
Status: closed
-
Source: Trisotech ( Mr. Denis Gagne)
-
Summary:
The DMN metamodel has Decision with M:N relations that point to BPMN and BMM. This may/will create undesirable referencing issues. While it It is desirable to maintain "loose coupling" between DMN and these external sources (BPMN, BMM, and even CMMN) to do so normally requires these kinds of relations be defined in the caller (or source) rather than the callee (or target). In the particular context of DMN, with respect to BPMN, BMM and event CMMN, the Decision will mostly likely be the target (and not the source). It is recommended to remove the BPMN20::Process, the BPMN20::Task, the BMM::Objective elements from the metamodel and their associated relations and rather make sure that a BPMN, BMM and/or CMMN models can point to a Decision that it uses rather than a DMN Decision pointing to (the potentially not enumerable) places where it is used.
-
Reported: DMN 1.1 — Mon, 16 May 2016 15:37 GMT
-
Disposition: Closed; Out Of Scope — DMN 1.2
-
Disposition Summary:
Cannot remove objects from meta-model, would not be backward compatible.
DMN 1.1 models may reference BPMN or BMM elements. These models must also be valid in DMN 1.2. As I understand backward compatibility requirements, this issue is out of scope for an RTF.
-
Updated: Wed, 3 Oct 2018 14:17 GMT
DMN12 — Remove tight coupling with BPMN and BMM
- Key: DMN12-45
- OMG Task Force: Decision Modeling and Notation 1.2 RTF