BPMN 2.

0 Business Process Model and Notation

Enterprise Architecture

BPMN is a registered TM of the Object Management Group

Activities Conversations Events start intermediate end

Event Sub-Processing
Task - Unit of work. The work or communications that identify a group

Event Sub-Process

Non-Interrupting

Non-Interrupting
job that needs to be accomplished. of logically related message exchanges.
Task
+ indicates a sub-process or an + shows a sub-conversation or

Interrupting

Interrupting
activity that can be refined. compound conversation element.

Throwing
Boundary

Boundary
Top-Level

Catching
Conversation Link connects
Transaction - activities that sensibly Communications to Participants.

transaction go together. May follow particular
transactional protocol. Forked Conversation Link attaches
None: Untyped events,
Communications and many Participants. indicate start point, state
Event Sub-Process is placed into a or changes or final states.
Process or Sub-Process. It is activated Conversation Diagram
Message: Receiving
event when its start event gets triggered and communication
sub-process and sending messages.
can interrupt the higher level process con- Pool
(collapsed)
text or run in parallel (non-interrupting) Timer: Cyclic timer events,
depending on the start event. points in time, time spans
or timeouts.
call Call Activity is a wrapper for a globally Pool multi instance pool Escalation: Escalating to a
activity defined Sub-Process or Task that is (collapsed) (collapsed)
higher level of responsibility.
reused in the current process.
sub-conversation Conditional: Reacting to
changed business conditions
or integrating business rules.
Activity Markers Task Types
Markers indicate execution Types specify the nature of Link: Off-page connectors.
behavior of activities: the action to be performed: Data Two corresponding link
events equal a sequence flow.
A Data Input is an external input
Sub-Process Marker Send Task for the entire process. It can be Error: Catching or throwing
input Task out- read by an activity. named errors.
Loop Marker Receive Task put
A Data Output is a variable avail- Cancel: Reacting to
Parallel MI Marker User Task able as result of the entire process. cancelled transactions
or triggering cancellation.
Sequential MI Marker Manual Task A Data Object represents infor-
mation flowing through the process, Compensation: Handling
~
Ad Hoc Marker Business Rule Task

such as business documents,
e-mails, or letters.
or triggering compensation.

Compensation Marker Service Task Signal: Signaling across

A Collection Data Object different processes.
Script Task represents a collection of infor- A signal thrown can be
mation, e.g., a list of order items. caught multiple times.

Multiple: Catching one

Sequence Flow Default Flow Conditional Flow A Data Store is a place where the out of a set of events.
process can read or write data, Throwing all events defined.
data store e.g., a database or a filing cabinet.
It persists beyond the lifetime of Parallel Multiple: Catching
the process instance. all out of a set of parallel
events.
defines the is the default has a condition A Message is used to depict the
execution order branch to be assigned that contents of a communication Terminate: Triggering
of activities. chosen if all defines whether between two Participants. the immediate termination
other conditions or not the flow of a process.
evaluate to false. is used.

www.visumpoint.com | 931 Monroe Drive, Suite 102 | Atlanta, GA 30308 USA | Phone: 404.474.1813 | info@visumpoint.com
 BPMN 2.0 Business Process Model and Notation

Enterprise Architecture

Collaboration Diagram Choreographies

Participant A
Participant A Choreography
Pool (Collapsed) Sub-Process
Choreography
Message Flow
Task
Attached Participant B
Intermediate
Ad-hoc Sub-Process Participant B Participant C
Timer Event
Event- Receive Task Manual Task
Task
Choreography Multiple Participants Choreography
based
Task- Is an ex- Marker- represents a Sub-Process-
Gateway
End
Lane

change between group of participants holds a refined

Collapsed Event two participants. that are of the same choreography
Sub-Process
Its an interaction kind. with a number
Task
Message (Message Exchange). of Interactions.
Start
Choreography Diagram
Event
~
Pool (Expanded)

Link
Collection
Intermediate Participant A
Timer Intermediate Escalation
Data Object Event
Event End Event Participant A
initiating
message
Text Annotation] Choreography
Sub-Process Participant A Task
Signal
Event Sub-Process End Group Choreography Participant B
Attached Event Task
Participant A
Intermediate

Participant B
data store Error Event Choreography
Multi Instance
Conditional Error End
response Task
Task (Parallel) message
Start Event Event
Lane

condition Participant B

Participant B
Participant C

Looped
Sub-Process Call
Link Parallel Activity Send Task
Intermediate Multiple
Event Intermediate Start End
Exclusive Parallel Message
Event
Swimlanes
Event Event
Gateway Gateway End Event

Pool
Lane
Task

Pool

Gateways

Lane

Pool
Complex Gateway Gateways Task

Exclusive Gateway Parallel Gateway When that represent actions not cap-
Split routes sequence flow to splitting sequence flow outgoing tured by other gateways. Can be
a precise outgoing branch. branches are initiated simultane- complex, merging or branching Pools (Participants) Message Flow- The order of
Merge waits for one incoming ously. When merging parallel actions/behaviors. and Lanes- show can be connected message exchange-
branch to finish before triggering branches- the gateway awaits all Exclusive Event-based Gateway what an activity is to pools, activities can be determined
an outgoing flow. incoming branches to finish before responsible for in or message events. by various combina-
(instantiate) Each occurrence
triggering outgoing flow. a process. Pools or Illustrate how tions of message
of a subsequent event starts a
lanes can represent information flows and sequence flows.
Event-based Gateway Must be new process instant. the organization as across organizational
followed by a catching event(s) or a Inclusive Gateway One or more Parallel Event-based Gateway a whole, a system borders.
receiving task(s). Sequence flow is branches are activated when split- (instantiate) The occurrence or a role. Lanes are
sent to the subsequent event/task ting. All active incoming branches of all subsequent events begins used to hierarchically
which happens first. must complete before merging. a new process instance. separate pools or
other lanes.

Copyright Visumpoint and any reuse only through permission.