BPMN 2.

0 - Business Process Model and Notation Innovator for Business Analysts

Events Processes and Collaborations Edges and connectors Data
Events: represent all incidents within a process. An event may be used as a start, intermediate, Collaboration: describes the interaction between participants (in this Sequence Flow Association Data Object Data Association List of data objects
interrupting and end event. example: customer, company and supplier).
A data object represents data which is relevant for
Shows the flow in a process. The sequence flow cannot cross a Is mainly used as data association for modeling data flows. the process. They can only be referenced inside the
Process: describes the flow of activities in an organization (in this ex- pool boundary but can switch between lanes. For modeling compensations it is used as compensation Data associations model the
process.
ample: quote creation). association. flow of data including data
continuation Name
create confirm [state]
transformations. Name Name Name
[state] [state] [state]
invitation participant Lane: represents the responsibilities within a process like involved Default Flow
plan event invitation commitment
roles or systems (in this example: clerk and approver). Message Flow
10 invitation cards
still remain Data Input quotation processing
delete Is traversed if none of the conditions after a gateway is true. order
order participant Shows the flow of messages between two participants. It can Data Inputs represent data which has to be passed to a
create invitation

invitation cards cancelation

not available
canceled
start or end at a participant or at any element of the process. It process or subprocess from the outside i.e. the calling
always goes beyond participant borders. process for further processing.
inquire confirmed Conditional Flow quote quotation items
order
Name database

request for quote

by phone
[state]

customer
14 days continuation quote requested quote created
create
A means to attach a condition to a sequence flow that does acquire
order
archive
cancelation quote order
not belong to a gateway.
Data Output quote received send order

cancel
invitation request quote
Analogous to the data input the data output repre-
event canceled termination
Artifacts sents data which is returned from the process or

Collaboration
create complete subprocess to the calling process. order creation

Clerk
quote quote
Text annotation Groups Name

quote creation
quote requested quote created customer

company
information price list [state]
N

No

Text annotations enable to Groups help to structure ele-

on

n-
-In
In E

capture important additional ments and do not influence

Approver
In

In
te ve

te Eve ou ted

approve
te

te

quote creation
Data Store (Reference)
In

In

quote quotation items order

rr nt

rr n

rru

rru

information. the process flow.

te

te

up C

up t C dar

pt S

pt Sta ess
rm

rm

tin on

ing tar ry

ing r
i

Using a data store (reference) instead of a data object

ng nn
ed C

ed Th t

gB e
St

Su t Ev

Su Ev

query answer
En
ia au

ia ro

B ec

Text annotations may emphasizes that the data used is persistant rather
o
ar

bp en

bp en
ou cte
te gh

te w

acquire create
d
t

contain additional
n

create send
ro t

ro t
Ev

Supplier than transient data and that it is accessible from dif-

n

nd d
Ev t

Ev n

Ev

quote data order

c

ce

information quote quote

en

en

en

en

ss

ferent processes rather than having a local scope.

y
t

quote sent Name

[state]
None

Participant/Pool (Black Box)

Instantiation
Message

message message message message message

Instantation: is mainly relevant in the process automation realized by gateways and events.
(trigger) (trigger) (trigger) (trigger) (trigger)
Signal

Subprocess (with loop feature) Event-Based - Event-Based -

Timer Exclusive Parallel

condition
The occurence of the first events instantiates the process. All other The occurence of the first event instantiates the process. The
paths of the event-based exclusiv gateways are no longer valid. process may only terminate normally if further events occured.
Conditional Send Task
timer escalation
intermediate event intermediate event quote
accepted
create send
order order
Escalation

travel expense accounting

order
travel expense

quotation processing
sent
Text annotation as accounting received settle travel
list customer

perform
loop condition exception answer link answer revise send expenses
[state1, intermediate event quote quote
Error
Lane 2 (subordinate)

quote
state 2] declined quote
sent

cancel
quote
event based
Participant/Pool (White Box)

15th of the month

Collaboration

Compensation gateway
deadline

Call Activity condition

Subprocess
Manual Task Script Task
Process

Lane (superior)

Cancel message parallel

failure boundary event otherwise
standard answer message
Multiple- Parallel Multiple-
start event gateway (default) end event
(interrupting) Start Event Start Event
data store
Terminate [end state] The process can be instantiated through different events. All events have to occur so that the process can be instantiated.
data store
[state 1,
state 2]
data object

travel expenses accounting

Link [state]
signal termination
Call Activity
Global Task settle travel

correct defect
intermediate event end event perform

perform
deadline expenses
defect correction
15th of the month
Multiple request defect correction defect correction
travel expenses
defect correction declined reported
accounting received

condition Event-based subprocess

Parallel Multiple
Lane 1 (subordinate)

Multi-Instance
Intermediate Event Business Rule
Task
Service Task
Sequential
Gateways
link exclusive inclusive multiple escalation start event failure
Start End intermediate event gateway gateway end event (non-interrupting) end event
Gateways are used to control how the process flows through sequence flows as they converge
Event Event and diverge within a process. quote ok accept
quote
caught thrown
inform
data-based check quote
customer
only one path can be taken
exclusive (either OR)
Activities
quote
incorrect decline
quote

inclusive (OR/AND) none, one or more paths can be taken

Task: represents a single step in a process Call Activity Global Task: identifies a point in the process Transactions: are subprocesses which require special actions Event-based subprocess: is started by an external event. It does exclusive: exactly one path is taken
or a work unit. where a global task is used. Activation of a call activity trans- to be taken in case of failure or hazard. not have any incoming or outgoing sequence flows.
fers control to the called task. parallel (AND) all paths are taken
room
desired
book room

Manual Task: is expected to be performed Call Activity Subprocesses: is an independent process that defect correction failed

without the aid of any business process can be called from various processes. drinks

can be used to model complex determine desired

order inform

execution engine or any application. complex customer‘s wish drinks customer

create account synchronization behavior
Subprocess: is a graphical object within a process but it also correct
defect
check
quality
defect corrected inform
customer
Performing defect corrections

User Task: is executed by a user with the as- can be „opened up“ to show a lower-level process. It is not save account information save contact information one path is taken depending on the first
sistance of a software application. event-based
an independent process and may not be devided in different occuring event inclusive: more than one path can be taken
Transaction

lanes. roll back error when

saving
error when
saving
identify reason of failure

reason of failure
Service Task: is performed automatically. delete account
information reason of failure
From a technical point of view, it is a call of cancel
find
buy
drinks process
a service operation. monitor response time
loop condition:
no sultion had
cause submit
quote
answer
complete
process
yet been found defect correction
failed
plan buy invite answer
Processing support request

perform
Business Rule Task: provides a mechanism measurement inform event food friends
customer
for the process to provide input to a busi-
ness process engine. Ad-hoc Subprocess: do not impose a sequence on its contained select 14 days
Compensation Association activities. The sequence and number of performances of the ac- music

Script Task: is executed by a business pro-

process
request on 1st level
occurs outside the normal sequence flow and connects a com- tivities is up to those persons or resources doing the work.
pensation event with a compensation activity at a roll back. parallel: all paths are taken event-based: the flow is forwarded to the path whose
cess engine. events occured first.
prepare dinner

Send Task: sends messages and complies

Markers for Tasks and Subprocesses Multi-Instance Parallel: multiple, simultane- Compensation: undoes steps which have al-
buy prepare set the
Ad-hoc Subprocess

with the semantics of an intermediate ingredients main course table

event for messages thrown. ous execution for a number of objects. ready been successfully completed. Find more information about the Innovator for Business Analysts
This activity implies a subprocess.
and business process modeling with BPMN 2.0!
prepare prepare polish invite friends
dessert starter cutlery
Receive Task: receives messages and com-
plies with the semantics of an intermediate Multi-Instance Sequential: multiple, sequen- Ad-hoc: whether and how often an activity is

www.mid.de
event for messages caught. Loop: repeats the performance as long as the tial execution for a number of objects. performed is left to the discretion of the per-
loop condition is met. son responsible.

© 2019 MID GmbH