Source: Signavio GmbH ( Bastian Steinert)
The processing of lists of data is fundamental to business decisions. Some kind of multiplicity should be indicated at the DRD level, and iteration should be supported visually at the decision logic level. In spite of the attached figures (meant to provoke discussion), the scope of this issue is limited to "flat" DRDs, that is, no "sub-DRDs" nested inside an outer decision or BKM. DRD proposal should specify what the multiplicity marker or other DRD notation looks like, and where it may appear, e.g. attached to head or tail of a requirement arrow, or inside a decision or BKM shape left of the name, etc.
Reported: DMN 1.1 — Wed, 4 May 2016 08:49 GMT
Disposition: Deferred — DMN 1.2
No workable proposal after several discussions over 2 years
How should iteration be visualized at the logic level and at the requirements level?
Updated: Tue, 23 Feb 2021 17:54 GMT
- Cardinality.pdf 276 kB (application/pdf)
- FanProposal_JTJP.pdf 297 kB (application/pdf)
- MID.jpg 30 kB (image/jpeg)
- iteration.PNG 9 kB ()
DMN12 — Lack of visual notation for processing of / iteration over lists
- Key: DMN12-27
- OMG Task Force: Decision Modeling and Notation 1.2 RTF