Conversation diagram |
|
Conversation diagrams visualize messages exchange between pools. Design workflow with business process diagram and visualize communications with BPMN conversation diagrams.
|
|
|
Business process diagram
|
Conversation diagram
|
Data flow diagram
|
EPC diagram
|
Process map diagram
|
Organization chart
|
|
|
|
|
Conversation diagram |
|
|
|
Notation
 | | Participant |  | | Conversation Link | |  | | Sub-Conversation Link |  | | Call-Conversation Link | |  | | Group |  | | Text Annotation | |  | | Association | |
| DefinitionConversation diagrams visualize messages exchange between pools. Design workflow with business process diagram and visualize communications with BPMN conversation diagrams. |
|
| |
Participant | |  | | Definition | | A Participant in a Collaboration or a Choreography. |
| | Properties | | | Name | The name of participant. | | ID | Used to uniquely identify BPMN elements. | | Process | The process the participant contains | | Participant | A Participant represents a specific PartnerEntity (e.g., a company) and/or a more general PartnerRole (e.g., a buyer, seller, or manufacturer) that Participants in a Collaboration | | Children | Flow elements within the participant | | Categories | Categories have user-defined semantics for documentation or analysis purposes. For example, flow elements can be categorized has being customer oriented vs. support oriented. The value attribute specifies one or more values of the category. | | Documentation | Used to annotate the participant, such as descriptions and other documentation. | | Black box | An empty participant that does not contain a process. |
|
|
|
|
| |
Conversation Link | |  | | Definition | | Conversation Links are used to connect ConversationNodes to and from Participants (Pools). |
| | Properties | | | Name | The name of conversation link. | | ID | Used to uniquely identify BPMN elements. | | From | The source of conversation link. | | To | The target of conversation link. | | Documentation | Used to annotate the conversation link, such as descriptions and other documentation. |
|
|
|
|
| |
Sub-Conversation Link | |  | | Definition | | A Sub-Conversation is a ConversationNode that is a hierarchical division within the parent Conversation. |
| | Properties | | | Name | The name of sub-conversation link. | | Documentation | Used to annotate the sub-conversation link, such as descriptions and other documentation. |
|
|
|
|
| |
Call-Conversation Link | |  | | Definition | | A Call Conversation identifies a place in the Conversation where a global Conversation or a GlobalCommunication is used. |
| | Properties | | | Name | The name of call-conversation link. | | Called element | The element to be called, which will be either a Conversation or a GlobalCommunication. | | Documentation | Used to annotate the call-conversation link, such as descriptions and other documentation. | | Participany Associations | This attribute provides a list of mappings from the Participants of a referenced GlobalCommunication or Conversation to the Participants of the parent Conversation. |
|
|
|
|
| |
Group | |  | | Definition | | A Group is a grouping of Activities that are within the same Category. |
| | Properties | | | Name | The name of group. | | ID | Used to uniquely identify BPMN elements. | | Documentation | Used to annotate the group, such as descriptions and other documentation. | | Categories | Categories have user-defined semantics for documentation or analysis purposes. For example, flow elements can be categorized has being customer oriented vs. support oriented. The value attribute specifies one or more values of the category. |
|
|
|
|
| |
Text Annotation | |  | | Definition | | Text Annotations are a mechanism for a modeler to provide additional information for the reader of a BPMN Diagram. |
| | Properties | | | Name | The name of text annotation. | | ID | Used to uniquely identify BPMN elements. | | Text | Text is an attribute that is text that the modeler wishes to communicate to the reader of the Diagram. | | Documentation | Used to annotate the text annotation, such as descriptions and other documentation. | | Categories | Categories have user-defined semantics for documentation or analysis purposes. For example, flow elements can be categorized has being customer oriented vs. support oriented. The value attribute specifies one or more values of the category. |
|
|
|
|
| |
Association | |  | | Definition | | A data association is used to model how data is pushed into or pulled from item-aware elements |
| | Properties | | | Name | The name of association. | | ID | Used to uniquely identify BPMN elements. | | From | Identifies the source of the data association. | | To | Identifies the target of the data association. | | Direction | The direction of association | | Documentation | Used to annotate the association, such as descriptions and other documentation. | | Categories | Categories have user-defined semantics for documentation or analysis purposes. For example, flow elements can be categorized has being customer oriented vs. support oriented. The value attribute specifies one or more values of the category. |
|
|
|
|
| |
| Definition of notations is quoted from Object Management Group Unified Modeling Language (OMG UML) Superstructure Version 2.2 and former versions (for notations that do not exist anymore in latest specification). |
| |
|
Business process diagram
|
Conversation diagram
|
Data flow diagram
|
EPC diagram
|
Process map diagram
|
Organization chart
|
