Bpmn-poster2014 Final En

BPMN 2.0 - Business Process Model and Notation

Innovator for Business Analysts

Processes and Collaborations

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

confirm participant

invitation 10 invitation cards still remain

not available

canceled confirmed

inquire by phone 14 days

continuation

cancelation

quote requested

cancel invitation

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

request

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

quote

Clerk

company quote creation

create quote quote requested

Groups

rm

te

Text annotations enable to capture important additional information.

approve quote

St t ar

query

answer

customer information

Groups help to structure elements and do not influence the process flow.

en Ev

Text annotations may contain additional information

Supplier

Name [state]

price list

Data Input

create quote

Name [state]

Name [state]

order

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.

quote

Name [state]

order database

quotation items create order

acquire quote

Data Output

archive order

quote received

send order

order creation

quotation items

t

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 different processes rather than having a local scope.

send quote

Name [state]

order

acquire quote data

create order

Instantiation

Participant/Pool (Black Box) message (trigger)

Name [state]

quotation processing

Data Store (Reference)

None

Message

Data associations model the flow of data including data transformations.

Name [state]

quote sent

Signal

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

Analogous to the data input the data output represents data which is returned from the process or subprocess to the calling process.

Text annotation

quote created

List of data objects

Data Association

Artifacts

complete quote

Approver

In

ss ce ro t bp en Su Ev t ing r pt Sta ess c rru ro t te bp en In nSu t Ev No ing tar ry pt S a rru nd d te ou cte In gB e n tin on y up t C dar rr n n te Eve ou ted B ec -In ng nn on i t o N t up C rr nt en te ve Ev In E d En t en Ev n te w ia ro ed Th t rm en te Ev t In te gh ia au ed C

Collaboration

Conditional Flow

quote created

termination

event canceled

Default 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. customer request for quote

cancelation

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

Massage Flow

delete participant

order invitation cards

create invitation

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

commitment

Data Object

Association

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

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

create invitation

Data

Sequence Flow

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

continuation

plan event

Edges and connectors

quote creation

Events

message (trigger)

message (trigger)

message (trigger)

message (trigger)

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

Event-Based Exclusive

Subprocess (with loop feature)

Timer

Event-Based Parallel

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

condition

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

escalation intermediate event

quote accepted

Escalation

Terminate

message start event

parallel gateway

Link

standard answer

otherwise (default)

message end event data store [end state]

deadline

Lane 1 (subordinate)

Start Event

End Event caught

link intermediate event

exclusive gateway

Business Rule Task

Multi-Instance Sequential

Service Task multiple end event

inclusive gateway

escalation start event (non-interrupting)

failure end event

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

roll back

Processing support request

perform measurement

save contact information

error when saving

error when saving

Performing defect corrections

save account information

delete account information

monitor response time

correct defect

request defect correction defect correction declined

defect correction reported

settle travel expenses 15th of the month travel expenses accounting received

Gateways Gateways are used to control how the process flows through sequence flows as they converge and diverge within a process. data-based exclusive (either OR)

only one path can be taken

inclusive (OR/AND)

none, one or more paths can be taken

parallel (AND)

all paths are taken

complex

can be used to model complex synchronization behavior

event-based exclusive

one path is taken depending on the first occuring event

quote ok

accept quote inform customer

check quote quote incorrect

decline quote

exclusive: exactly one path is taken room desired

check quality

defect corrected

inform customer

determine customer‘s wish

book room

drinks desired

order drinks

reason of failure reason of failure

buy drinks

find cause defect correction failed

plan event

inform customer

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

Compensation Association occurs outside the normal sequence flow and connects a compensation event with a compensation activity at a roll back.

buy food

process answer

submit quote

invite friends

select music

parallel: all paths are taken

© 2013 MID GmbH

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

Compensation: undoes steps which have already been successfully completed.

This activity implies a subprocess. Loop: repeats the performance as long as the loop condition is met.

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

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

Ad-hoc Subprocess

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

Markers for Tasks and Subprocesses

buy ingredients

prepare main course

set the table

prepare dessert

prepare starter

polish cutlery

invite friends

14 days

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

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

www.mid.de

complete process

answer

prepare dinner

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

inform customer

inclusive: more than one path can be taken

identify reason of failure

cancel

loop condition: no sultion had yet been found

process request on 1st level

perform defect correction

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

defect correction failed

Transaction

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.

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

Script Task: is executed by a business process engine.

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

create account

User Task: is executed by a user with the assistance of a software application.

Business Rule Task: provides a mechanism for the process to provide input to a business process engine.

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

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

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

Parallel MultipleStart Event

Event-based subprocess

thrown

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

settle travel expenses

15th of the month

The process can be instantiated through different events.

Call Activity Global Task

condition

Intermediate Event

quote sent

MultipleStart Event

Multiple

Parallel Multiple

send quote

travel expense accounting received

Script Task

termination end event

signal intermediate event

quote declined

revise quote

deadline

data store [state 1, state 2]

data object [state]

customer answer

cancel quote

Manual Task failure boundary event (interrupting)

link intermediate event

event based gateway

condition

Call Activity Subprocess

exception answer

send order order sent

quotation processing

Lane 2 (subordinate)

list [state1, state 2]

correct defect

Cancel

Lane (superior)

Compensation

Participant/Pool (White Box) Process

Collaboration

Error

Text annotation as loop condition

create order

perform travel expenses accounting

timer intermediate event

perform travel expense accounting

Send Task

Conditional