Legacy Issue Number: 15901
Source: scch.at ( Christine NatschlÃ¤r)
According to the Message Flow Class Diagram (Figure 9.14), Interaction Node has four subclasses: Participant, ConversationNode, Task and Event.
However, according to page 124:
Of the types of InteractionNode, only Pools/Participants, Activities, and
Events can be the source of a Message Flow.
The question now is, whether Task or Activity should be the subclass of Interaction Node.
Suggestion: The Message Flow Connection Rules on page 44 specify that Message Flows can also connect to Sub-Processes. Therefore, I think it is necessary to define that Activity is a subclass of InteractionNode.
Reported: BPMN 2.0 — Wed, 15 Dec 2010 05:00 GMT
Updated: Fri, 6 Mar 2015 20:57 GMT
BPMN21 — Subclasses of Interaction Node (Task vs. Activity)
- Key: BPMN21-275
- OMG Task Force: BPMN 2.1 RTF