-
Key: BPMN2-278
-
Legacy Issue Number: 15119
-
Status: closed
-
Source: BPM Advantage Consulting ( Dr. Stephen White)
-
Summary:
Collaborations and Choreographies have a large degree of overlap in underlying capabilities--basically being a collection of Participants and Message Flow. Choreography only adds the sequencing of the Message Flow. It would be useful to be able to take the same interaction model and display it as either a Collaboration or a Choreography. The definition of those views would determine what should be displayed and how they are displayed.
A merger of the two diagrams in the metamodel would greatly simplify the implementation, add flexibility, and improve BPMN support of other specifications, such as SoaML. -
Reported: BPMN 2.0b1 — Thu, 4 Mar 2010 05:00 GMT
-
Disposition: Resolved — BPMN 2.0
-
Disposition Summary:
The resolution of issue 14654 provides the resolution for this issue.
Disposition: Duplicate -
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN2 — Merge Collaboration and Choreography in Metamodel
- Key: BPMN2-278
- OMG Task Force: BPMN 2.0 FTF