© 2013 MID GmbH

www.mid.de

BPMN 2.0 - Business Process Model and Notation Innovator for Business Analysts

Find more information about the Innovator for Business Analystsand business process modeling with BPMN 2.0!

Events

StartEvent

EndEvent

Intermediate Event

caught thrown

Escalation

Conditional

Error

Timer

Message

Terminate

Link

Signal

Cancel

None

Compensation

Multiple

Parallel Multiple

Caught

Intermediate Event

Start Event

Start Event

Start Event

Event Connected

Event Connected

Thrown

End Event

orderinvitation cards

inquireby phone

createinvitation

deleteparticipant

confirmparticipant

cancelinvitation

cancelation

crea

te in

vita

tion

plan event

14 days

cancelation

commitment

event canceled termination

continuation

canceled

confirmed

not available

continuation

10 invitation cardsstill remain

invitation

Events: represent all incidents within a process. An event may be used as a start, intermediate, interrupting and end event.

Intermediate Event

Interrupting Boundary

Non-Interrupting Boundary

Interrupting Subprocess-

Non-Interrupting Subprocess-

Conditional Flow

Sequence Flow

Massage Flow

Shows the flow of messages between two participants. It can start or end at a participant or at any element of the process. It always goes beyond participant borders.

Shows the flow in a process. The sequence flow cannot cross a pool boundary but can switch between lanes.

Association

Is mainly used as data association for modeling data flows. For modeling compensations it is used as compensation association.

A means to attach a condition to a sequence flow that does not belong to a gateway.

Is traversed if none of the conditions after a gateway is true.

Default Flow

Edges and connectorsCollaboration: describes the interaction between participants (in this example: customer, company and supplier).

Process: describes the flow of activities in an organization (in this ex-ample: quote creation).

Lane: represents the responsibilities within a process like involved roles or systems (in this example: clerk and approver).

Processes and Collaborations

Supplier

cust

omer

requ

est f

or q

uote

approvequote

Appr

over

createquote

completequoteCl

erk

com

pany

quot

e cr

eatio

n

Collabo

ratio

n

quote requested quote created

quote requested quote created

request quote

query answer

Artifacts

Groups help to structure ele-ments and do not influence the process flow.

Text annotations enable to capture important additional information.

GroupsText annotation

createquote

sendquote

quote sent

price list

quot

e cr

eatio

n

customerinformation

Text annotations may contain additional information

Task: represents a single step in a process or a work unit.

User Task: is executed by a user with the as-sistance of a software application.

Service Task: is performed automatically.From a technical point of view, it is a call of a service operation.

Business Rule Task: provides a mechanism for the process to provide input to a busi-ness process engine.

Manual Task: is expected to be performed without the aid of any business process execution engine or any application.

Activities

Script Task: is executed by a business pro-cess engine.

Call Activity Global Task: identifies a point in the process where a global task is used. Activation of a call activity trans-fers control to the called task.

Call Activity Subprocesses: is an independent process that can be called from various processes.

Receive Task: receives messages and com-plies with the semantics of an intermediate event for messages caught.

Send Task: sends messages and complies with the semantics of an intermediate event for messages thrown.

Event-based subprocess: is started by an external event. It does not have any incoming or outgoing sequence flows.

Subprocess: is a graphical object within a process but it also can be „opened up“ to show a lower-level process. It is not an independent process and may not be devided in different lanes.

Transactions: are subprocesses which require special actions to be taken in case of failure or hazard.

Ad-hoc Subprocess: do not impose a sequence on its contained activities. The sequence and number of performances of the ac-tivities is up to those persons or resources doing the work.

save contact information

delete accountinformation

save account information

create account

Tran

saction

error whensaving

roll back error whensaving

cancel

informcustomer

performmeasurement

monitor response time

processrequest on 1st levelPr

oces

sing

sup

port

requ

est

loop condition:no sultion had yet been found

correctdefect

checkquality

findcause

identify reason of failure

informcustomer

Perf

orm

ing

defe

ct c

orre

ctio

ns

reason of failure

reason of failure

defect correctionfailed

defect correction failed

defect corrected

preparemain course

buyingredients

set thetable

polishcutlery

preparedessert

preparestarter

prepare dinner

Ad-h

oc S

ubpr

oces

s

invite friends

Ad-hoc: whether and how often an activity is performed is left to the discretion of the per-son responsible.

This activity implies a subprocess.

Loop: repeats the performance as long as the loop condition is met.

Multi-Instance Parallel: multiple, simultane-ous execution for a number of objects.

Multi-Instance Sequential: multiple, sequen-tial execution for a number of objects.

Compensation: undoes steps which have al-ready been successfully completed.

Markers for Tasks and Subprocesses

Compensation Associationoccurs outside the normal sequence flow and connects a com-pensation event with a compensation activity at a roll back.

Data Object

Data Store (Reference)

Data Output

Data Input

A data object represents data which is relevant for the process. They can only be referenced inside the process.

Data Inputs represent data which has to be passed to a process or subprocess from the outside i.e. the calling process for further processing.

Analogous to the data input the data output repre-sents data which is returned from the process or subprocess to the calling process.

Using a data store (reference) instead of a data object emphasizes that the data used is persistant rather than transient data and that it is accessible from dif-ferent processes rather than having a local scope.

DataData Association List of data objects

Name[state]

Name[state]

Name[state]

Name[state]

Name[state]

Name[state]

Name[state]

Data associations model the flow of data including data transformations.

createorder

acquirequote data

order creation

archiveorder

acquirequote

createorder

quotation processing

send order

orderdatabasequotation itemsquote

quote received

order

orderquotation items

Instantiation

Instantation: is mainly relevant in the process automation realized by gateways and events.

The occurence of the first events instantiates the process. All other paths of the event-based exclusiv gateways are no longer valid.

revisequote

sendorder

createorder

sendquote

cancelquote

quot

atio

n pr

oces

sing

customeranswer

deadline

quoteaccepted

quotedeclined

ordersent

quotesent

The occurence of the first event instantiates the process. The process may only terminate normally if further events occured.

Multiple-Start Event

Parallel Multiple-Start Event

The process can be instantiated through different events. All events have to occur so that the process can be instantiated.

settle travelexpenses

perfo

rm

trav

el e

xpen

se a

ccou

ntin

g

travel expense accounting received

15th of the month

performdefect correction

corr

ect d

efec

t

request defect correctiondefect correction declined

defect correctionreported

settle travelexpenses

perfo

rmtr

avel

exp

ense

s acc

ount

ing

15th of the monthtravel expenses

accounting received

Event-Based -Exclusive

Event-Based -Parallel

all paths are taken

Gateways

data-basedexclusive (either OR)

parallel (AND)

inclusive (OR/AND)

event-basedexclusive

complex

event-based: the flow is forwarded to the path whose events occured first.

Gateways are used to control how the process flows through sequence flows as they converge and diverge within a process.

only one path can be taken

one path is taken depending on the first occuring event

declinequote

informcustomer

acceptquote

check quote

quote ok

quoteincorrect

exclusive: exactly one path is taken

selectmusic

buydrinks

buyfood

planevent

invitefriends

processanswer complete

processsubmitquote

answer

14 days

determinecustomer‘s wish

informcustomer

book room

orderdrinks

drinksdesired

roomdesired

inclusive: more than one path can be taken

none, one or more paths can be taken

can be used to model complexsynchronization behavior

parallel: all paths are taken

Business RuleTask

Multi-InstanceSequential

Event-based subprocess

Service Task

Lane

1 (s

ubor

dina

te)

Call ActivitySubprocess

Manual Task

Call ActivityGlobal Task

Send Task

Script Task

Subprocess (with loop feature)

Lane

2 (s

ubor

dina

te)

Lane

(sup

erio

r)

Parti

cipa

nt/P

ool (

Whi

te B

ox)

Proc

ess

Participant/Pool (Black Box)

Colla

bora

tion

Text annotation asloop condition

escalationintermediate event

timerintermediate event

terminationend event

parallelgateway

list[state1,state 2]

messageend event

data object[state]

failure boundary event(interrupting)

signalintermediate event

event basedgateway

standard answer

exception answer

deadline

messagestart event

data store[state 1,state 2]

data store[end state]

linkintermediate event

failureend event

escalation start event(non-interrupting)

exclusivegateway

multipleend event

linkintermediate event

inclusivegateway

condition

otherwise(default)

condition

condition

message(trigger)

message(trigger)

message(trigger)

message(trigger)

message(trigger)