BPMN 2.0 - Business Process Model and Notation http://bpmb.

de/poster

Conversations Choreographies
Activities
Events
Participant A Participant A Participant A Start Intermediate End
A Conversation defines a set of
A Task is a unit of work, the job to be logically related message exchanges. Choreography Call

Event Sub-Process

Event Sub-Process
Sub-Choreography

Non-Interrupting
performed. When marked with a symbol When marked with a symbol it Task Choreography

Boundary Non-
Task

Interrupting

Interrupting

Interrupting
it indicates a Sub-Process, an activity that can indicates a Sub-Conversation, a

Boundary

Throwing

Standard
Standard

Catching
Participant B Participant B
be refined. compound conversation element. Participant B
A Choreography Task
A Call Conversation is a wrapper for a Participant C A Call Choreography is a
represents an Interaction
A Transaction is a set of activities that logically globally defined Conversation or Sub- (Message Exchange) A Sub-Choreography contains wrapper for a globally
Transaction belong together; it might follow a specified Conversation. A call to a Sub-conversation between two Participants. a refined choreography with defined Choreography Task
transaction protocol. is marked with a symbol. several Interactions. or Sub-Choreography. A call None: Untyped events,
to a Sub-Choreography is indicate start point, state
A Conversation Link connects marked with a symbol. changes or final states.
An Event Sub-Process is placed into a Process or Conversations and Participants.
Event
Sub-Process. It is activated when its start event
gets triggered and can interrupt the higher level Multiple
Choreography Diagram Message: Receiving and
sending messages.
Sub-Process Participants Marker Participant A
process context or run in parallel (non-
interrupting) depending on the start event. Conversation Diagram denotes a set of Initiating
Timer: Cyclic timer events,
Participant A points in time, time spans or
Participants of the Message
Conversation same kind. (decorator) Choreography timeouts.
A Call Activity is a wrapper for a globally defined Task
Pool Participant B Escalation: Escalating to
Call Activity Task or Process reused in the current Process. A Participant A
(Black Box) an higher level of
call to a Process is marked with a symbol. Participant B
Message Choreography responsibility.
Task Conditional: Reacting to
a decorator depicting Participant A
the content of the Participant B changed business conditions
Activity Markers Task Types message. It can only Choreography or integrating business rules.
Pool Multi Instance Pool be attached to Task
Markers indicate execution Types specify the nature of Response Link: Off-page connectors.
(Black Box) (Black Box) Choreography Tasks. Participant C
behavior of activities: the action to be performed: Message Two corresponding link events
Sub-Conversation (decorator) equal a sequence flow.
Sub-Process Marker Send Task Participant B Error: Catching or throwing
Participant C named errors.
Loop Marker Receive Task
Collaboration Diagram Cancel: Reacting to cancelled
Parallel MI Marker User Task transactions or triggering
(Black

cancellation.
Box)
Pool

Sequential MI Marker Manual Task

Pool (Black Box)
Compensation: Handling or

~ Ad Hoc Marker Business Rule Task Message Flow triggering compensation.

Signal: Signalling across differ-

Compensation Marker Service Task Attached
ent processes. A signal thrown
Ad-hoc Subprocess Intermediate
Receive Task Timer Event can be caught multiple times.
Script Task Event-based Manual Task Multiple: Catching one out of
Gateway
Lane

Task a set of events. Throwing all

Collapsed End
Subprocess Event events defined
Sequence Flow Default Flow Conditional Flow Message Parallel Multiple: Catching
Start Event Task all out of a set of parallel
Link events.

defines the execution is the default branch has a condition

Timer
Intermediate
Escalation
End Event ~ Intermediate
Event
Terminate: Triggering the
immediate termination of a
Pool (White Box)

Data Object Collection

order of activities. to be chosen if all assigned that defines Event process.
other conditions whether or not the
evaluate to false. flow is used.
Subprocess Text Annotation
Signal
End
Attached Event Group
Data
Looped Intermediate
Store

Gateways Data
Subprocess Error Event
Multi Instance
Lane

Start End
Event Event condition Task (Parallel)
Exclusive Gateway When splitting, it routes the sequence flow to exactly A Data Object represents information flowing
one of the outgoing branches. When merging, it awaits Link Parallel Event Subprocess
through the process, such as business
one incoming branch to complete before triggering the Intermediate Multiple documents, e-mails, or letters.
outgoing flow. Event Intermediate
Event Call Activity Send Task
Conditional Error End
Event-based Gateway Is always followed by catching events or receive tasks. A Collection Data Object represents a
Start Event Event
Sequence flow is routed to the subsequent event/task Message collection of information, e.g., a list of order
Exclusive Parallel
which happens first. Gateway Gateway
End Event items.

Parallel Gateway When used to split the sequence flow, all outgoing A Data Input is an external input for the
branches are activated simultaneously. When merging Input
entire process.A kind of input parameter.
parallel branches it waits for all incoming branches to
Swimlanes
Pool
Lane

complete before triggering the outgoing flow. Task

A Data Output is data result of the entire
Pool

Inclusive Gateway Out- process. A kind of output parameter.

Exclusive Event-based Gateway
When splitting, one or more put
Lane

(instantiate)
Pool

branches are activated. All
active incoming branches must
complete before merging.
Complex Gateway
Complex merging and
branching behavior that is not
captured by other gateways.
Task
Each occurrence of a subsequent Message Flow symbolizes A Data Association is used to associate data
event starts a new process information flow across elements to Activities, Processes and Global
instance. organizational boundaries. Tasks.
Pools (Participants) and Lanes The order of message
Message flow can be attached
Parallel Event-based Gateway represent responsibilities for exchanges can be A Data Store is a place where the process can
to pools, activities, or
(instantiate) activities in a process. A pool specified by combining read or write data, e.g., a database or a filing
message events. The Message
The occurrence of all subsequent or a lane can be an message flow and cabinet. It persists beyond the lifetime of the
Flow can be decorated with Data Store
events starts a new process organization, a role, or a sequence flow. process instance.
an envelope depicting the
instance. system. Lanes subdivide pools
content of the message.
or other lanes hierarchically. © 2011