---
title: "12.4 Example(s)"
chapter: "12 BPMN Notation and Diagrams"
source: "OMG BPMN 2.0.2 — formal/2013-12-09"
pages: "412-422"
---
> 12 BPMN Notation and Diagrams · páginas 412-422 · [índice](../README.md)
## 12.4 Example(s)
This sub clause provides examples to support interpretation of the BPMN DI specification. Some BPMN diagram depictions along with their XML BPMN DI serializations are provided. The XML samples provided in this sub clause present only BPMN DI instances and omit the BPMN 2.0 abstract syntax. For readability purposes, the bpmnElement that is referenced by the BPMNPlane, BPMNShape, and BPMNEdge use a representative string pattern. This string pattern is:
- BPMNModelClassName_BPMNModelNameAttributeValue
For example: “Task_Activity” for a Task named “Activity.” In the provided XML serializations, the di namespace refers to the Diagram Interchange namespace defined in Annex B, and the dc namespace refers to the Diagram Common namespace also defined in Annex B.
### 12.4.1 Depicting Content in a Sub-Process
This sub clause shows various ways of depicting the content of a Sub-Process of the same BPMN model. The BPMN model contains a process composed of a none start event (named “StartEvent”), a sub-process (named “SubProcess”) and a none end event (named “EndEvent”). There is a sequence flow (named “a”) between the start event (named “StartEvent”) and the sub-process (named “SubProcess”) and a sequence flow (named “d”) between the subprocess (named “SubProcess”) and the end event (named “EndEvent”). The sub-process (named “SubProcess”) is composed of a none start event (named “SubProcessStart”), an abstract task (named “Activity”) and a none end event (named “SubProcessEnd”). There is a sequence flow (named “b”) between the start event (named “SubProcessStart”) and the task (named “Activity”) and a sequence flow (named “c”) between the task (named “Activity”) and the end event (named “SubProcessEnd”).
#### Expanded Sub-Process
First, a BPMN diagram depicts the BPMN model with the expanded sub-process showing its content (see Figure 12.8). This leads to a BPMN DI serialization of a single diagram that depicts this process (see Table 12.37).
StartEvent SubProcess SubProcess EndEvent
*Figure 12.8 – Expanded Sub-Process Example* (p. 413)
**Table 12.36 – Expanded Sub-Process BPMN DI instance**
```xml
```
#### Expanded Sub-Process with Start and End Events on Border
An alternative to depicting the same BPMN model of 12.4.1 would be to place the sub-process start and end events on the border of the sub-process (see Figure 12.9). In the BPMN DI serialization of this diagram (see Table 12.40), the target of the sequence flow named “a” and the source of the sequence flow named “d” are the start and end events on the boundary of the sub-process. Compare the target of the sequence flow named “a” and the source of the sequence flow named “d” of Table 12.37 with that of Table 12.38.
StartEvent SubProcess SubProcess EndEvent
*Figure 12.9 – Start and End Events on the Border Example* (p. 414)
**Table 12.37 – Start and End Events on the Border BPMN DI instance**
```xml
```
#### Collapsed Sub-Process
Alternatively, one could depict the same BPMN model of 12.4.1 as two diagrams. A first diagram (Figure 12.10) depicts the process with the sub-process collapsed, while a second diagram (Figure 12.11) depicts the content of the sub-process.
*Figure 12.10 – Collapsed Sub-Process* (p. 415)
*Figure 12.11 – Contents of Collapsed Sub-Process* (p. 416)
**Table 12.38 – Collapsed Sub-Process BPMN DI instance**
```xml
```
**Table 12.39 – Sub-Process Content BPMN DI instance**
```xml
```
### 12.4.2 Multiple Lanes and Nested Lanes
In this next example, a diagram depicting a BPMN Process is composed of a LaneSet that contains 2 lanes is presented. The second lane contains 2 sub lanes (See Figure 12.12).
*Figure 12.12 – Nested Lanes Example* (p. 417)
**Table 12.40 – Multiple Lanes and Nested Lanes BPMN DI instance**
```xml
```
### 12.4.3 Vertical Collaboration
In this example, a Collaboration between two Participants (Pool A and Pool B) is depicted. The first Participant is depicted with a white box Pool and the second Participant is depicted with a black box Pool. This diagram also depicts message flows that are decorated with message envelopes (See Figure 12.13).
*Figure 12.13 – Vertical Collaboration Example* (p. 418)
**Table 12.41 – Vertical Collaboration BPMN DI instance**
```xml
```
### 12.4.4 Conversation
The following diagram depicts a Collaboration between 3 Participants (Participants 1, 2, and 3) including two Conversations. The diagram also has an annotation connected to a message flow (see Figure 12.14).
*Figure 12.14 – Conversation Example* (p. 420)
**Table 12.42 – Conversation BPMN DI instance**
```xml
```
### 12.4.5 Choreography
The following diagram depicts a Choreography consisting of 3 Choreography Activities (2 Choreography Tasks and 1 SubChoreography). This diagram also depicts Participant Bands with and without envelope decorator.
S ta rtE ve n t P a rticip an t 2 E n d E ve n t
*Figure 12.15 – Choreography Example* (p. 422)
**Table 12.43 – Choreography BPMN DI instance**
```xml
```