BPMN_Poster_A3_ver_1.0.10.pdf

Business Process Modelling Notation (BPMN) Poster

cbfgh

Check for the latest version at: http://bpmn.itposter.net

Business Process Diagram Graphical Objects

Business Process Diagram Connecting Objects

Events

Activities

Gateways

Agatewayisusedtosplitormergemultipleprocess

flows.Thusitwilldeterminebranching,forking,

mergingandjoiningofpaths. Examples:'Conditiontrue?

– yes/no','Choosecolour?– red/green/blue',...

Graphicalconnectingobjects

SequenceFlowandMessageFlowrules

Onlyobjectsthatcanhaveanincomingand/oroutgoingSequenceFlow/Message

FlowareshownintheTablesBelow.

Aneventissomethingthat»happens«duringtheprocess.Theseeventsaffectthe

flowoftheprocessandusuallyhaveacause(trigger)oranimpact(result).

Examples:'Emailreceived','3o'clock','Warehouseempty','Criticalerror',...

Anactivityisagenerictypeofworkthatacompanyperforms.An

activitycanbeatomic(task)orcompound(process,subprocess).

Examples:'Sendaletter','Writeareport','Calculatetheinterests',...

TherearethreewaysofconnectingFlow objects (Events, Activities,

Gateways) witheachotherorwithotherinformation– usingsequence

flows,messageflowsorassociations.

Graphicalconnectingobjects

A Sequence Flow is used to show the order In which the activities in a

process will be performed.

To:

Ataskisusedtorepresentthe

activityonthelowestabstraction

level.

Process

Expanded

sub-process

Event flow

Normal

sequenceflow

Conditional

sequenceflow

Default

sequenceflow

Messageflow

Description

Collapsed

sub-process

Transaction

Gatewaycontroltypes

Event type

Moreinformationaboutthe

transactionandcompensation

attributecanbefoundunder

»CompensationAssociation«.

The Start Event indicates where a particular process will start. Intermediate

Events occur between a Start Event and an End Event. It will affect the flow

of the process, but will not start or (directly) terminate the process. The End

Event indicates where a process will end.

Task

XOR

(DATA)

Databasedexclusivedecisionor

merging.Bothsymbolshaveequal

meaning.SeealsoConditionalflow.

A Sequence Flow can have condition expressions which are evaluated

at runtime to determine whether or not the flow will be used.

For Data-Based Exclusive Decisions or Inclusive Decisions, one type

of flow is the Default condition flow. This flow will be used only if all

other outgoing conditional flows are NOT true at runtime.

General

XOR

(EVENT)

Eventbasedexclusivedecisiononly.

A Message Flow is used to show the flow of messages between two

participants that are prepared to send and receive them. In BPMN,

two separate Pools in a Diagram can represent the two participants.

An Association (directed, non-directed) is used to associate

information with Flow Objects. Text and graphical non-Flow Objects

can be associated with Flow objects.

A message arrives from a participant and triggers the Event. This causes

process to {start, continue, end} if it was waiting for a message, or changes

the flow if exception happens. End type of message event indicates that a

message is sent to a participant at the conclusion of the process.

Task/Subprocessspecialattributes

Thetaskorsubprocessisrepeated.

Thetasksinthesubprocesscannotbeconnectedwith

sequenceflowsatdesigntime.

Multipleinstancesoftaskorsubprocesswillbecreated.

Message

Looping

Ad Hoc

Association

Databasedinclusivedecisionor

merging.

A specific time or cycle can be set that will trigger the start of the Process

or continue the process. Intermediate timer can be used to model the time-

based delays.

Timer

Multiple instances

COM

PLEX

Complexcondition(acombinationof

basicconditions)

Sequenceflowmechanism

CompensationAssociation

Compensation

Error

This type of End indicates that a named Error should be generated. This

Error will be caught by an Intermediate Event within the Event Context.

Thesymbolrepresentsacompensationtaskorsubprocess.

This type of Event is used within a Transaction Sub-Process. This type of

Event MUST be attached to the boundary of a Sub-Process. It SHALL be

triggered if a Cancel End Event is reached within the Transaction Sub-

Process.

AND

Parallelforkingandjoining

(synchronization).

The Sequence Flow mechanisms is divided into types: Normal flow, Exception flow,

Conditional flow, Link Events and Ad Hoc (no flow). Refer also to specific

ÇWorkflow PatternsÆ.

Incaseoftransactionsitisdesiredthatallactivitieswhichconstitute

atransactionarefinishedsuccessfully.Otherwisethetransactionfails

androllback(compensation)activitiesoccurwhichundodone

activities.

Cancel

Artefacts

Normal sequence flow

Ad Hoc Î

No flow

This is used for compensation handling--both setting and performing

compensation. It calls for compensation if the Event is part of a Normal

Flow. It reacts to a named compensation call when attached to the

boundary of an activity. Very useful for modelling roll-back actions within

the transaction.

Artefactsareusedtoprovideadditionalinformationabouttheprocess.If

required,modellersandmodellingtoolsarefreetoaddnewartefacts.

Examplesofdataobjects:'Aletter','Emailmessage','XMLdocument',

'Confirmation',...

Swimlanes

Task

Compensation activity

Compensation

Intermediate

link used as

GOTO

Poolsandlanesareusedtorepresentorganizations,

roles,systemsandresponsibilities.Examples:

'University','Salesdivision','Warehouse','ERPsystem',...

Task A

This type of event is triggered when the conditions for a rule

become true. Rules can be very useful to interrupt the loop process, for

example: 'The number of repeats = N'. Intermediate rule is used only for

exception handling.

A Link is a mechanism for connecting the end (Result) of one

Process to the start (Trigger) of another. Typically, these are

two Sub-Processes within the same parent Process. It can be used, for

example, when the working area (page) is too small Îgo to another page.

This type of event indicates that there are multiple ways of triggering the

Process. Only one of them will be required to {start, continue, end} the

Process.

Intermediate link

used as GOTO

Transaction boundary

Rule

Setofstandardizedartefacts

ExceptionX

Undo task A

APoolMUSTcontain0or1

businessprocess.

APoolcancontain0ormore

lanes.

Twopoolscanonlybeconnected

withmessageflows.

Until Loop

Looped subprocess

Start

transaction

Successfull

transaction

Data objects provide information about what activities are required to be

triggered and/or what they produce. They are considered as Artefacts

because they do not have any direct effect on the Sequence Flow or

Message Flow of the Process. The state of the data object should also be

set.

Grouping can be used for documentation or analysis purposes. Groups

can also be used to identify the activities of a distributed transaction that is

shown across Pools. Grouping of activities does not affect the Sequence

or Message Flow.

Text Annotations are a mechanism for a modeller to provide additional

information for the reader of a BPMN Diagram.

Expanded sub-process

Link

Dataobject

Task B

Error - compensation

events cannot be

triggered

[state]

Exception flow

ExceptionX

Undo task B

Try again

Multiple

Group

APool representsaparticipantinaprocess.Itcontainsabusiness

processandisusedinB2Bsituations.

Interrupt

loop rule

This type of End indicates that all activities in the Process should be

immediately terminated. This includes all instances of Multi-Instances. The

Process is terminated without compensation or event handling.

Conditional flow

ExceptionX

Transaction

exception

Handle through

other services

Terminate

Annotation

ALane isasubpartitionwithinapoolusedtoorganizeand

categorizeactivities.

Description

~ Collapsed adhoc sub-process

Failed transaction

Cancel - compensation events are triggered.

Cancel event can be used only with transaction.

Waitafewminutes

Business Process Diagram Notation -Common Patterns and Antipatterns

Wronguseofflowsin/between

pools

WhenmodellingPools,sequenceflowsandstart/endeventsare

oftenmissing,becauseitiswronglypresumedthatmessage

flowssubstitutesequenceflows.Additionally,sequenceflows

areincorrectlyusedtoconnectpools.

(Wrong)Useoftimeevents

Useofflowswithinlanes

Useofgateways

Workflowpatterns

Therearetwocommonmistakeswhenusingtimeevents.First,

startingeventsareoftenusedinsteadofintermediateevents.

Second,intermediateeventsareoftenusedasadelay

mechanismbutmodelledasanexceptionmechanism

(representingthedurationofatask)andviceversa(seethe

rightusebelow).

Multiple merge, uncontrolled flow

Normal sequence flow

LanesareoftenwronglyusedinsimilarwaysasPools.They

wronglycontainmorebusinessprocessesorcontainmessage

flowsbetweendifferentlanes.

Gatewaysareconnectedonlywithsequenceflows.AlsoAvoid

potentialdeadlockswhenusinggateways.

ModeltheprocessineachPoolindependentlyandafterwards

definemessageflowsbetweenPools.

A message flow is not

allowed within a process

A Pool can contain only one

(1) process

Message flow cannot

influence the gateway

Parallel split, uncontrolled flow

Exclusive choice with

decision gateway

Simple merge,

uncontrolled flow

Here a time event Is used as

a DELAY mechanism.

Missing end event

Task A

Missing sequence flows

Task C

...

Task A

Task B ...

Decision

information

from Pool X

A conditional flow Is not

allowed (necessary) here

Multiple choice

Delay

Task B Task C

Task A

Parallel split,

forking gateway

Discriminator,

merging gateway

No output flow from the task

exists.

Task A

Task B

Task C

Synchronization

(pararel join)

...

Exception time

(e.g. Çafter 2 hoursÆ)

Task B

Simple merge,

uncontrolled flow

Message

flow AD

Message

flow EB

Sequence flows are not

allowed between Pools

Task A

Here it represents the

DURATION of a task.

The decision must

contain at least two

output flows

Alter. 1

Task B ...

An intermediate event

has to be used.

Task B Task C

Send message to

Pool X

Alter. 2

Task D

Task E

Task F

A message flow cannot be

a gateway alternative

Alter. 3

Event based decision

Complex decision

(gateway)

Missing start event

Useofmessageeventsand

messageflows

Useofthesequenceflow

mechanism

Task C

Useoftasksandevents

Task A

Analysing

decision

information

Whenusingexpandedsubprocesses,sequenceflowsshould

beconnectedtotheboundariesofsubprocesses.Processes

andsubprocessesshouldstartandendproperly!

Startingandintermediateeventscannotbesourcesof

messageflows.

Multiple choice, inclusive

decision gateway

Analystsoftenwronglymodeleventsandtasks.For

example:eventsarewronglymodelledastasks,taskstates

aremodelledasnewtasks.

...

Both examples are wrong - intermediate

message events can not produce

message flows. Events can be only

triggered by a message flow.

Task B

Synchronization merge,

merging gateway

Example of a

deadlock

Message

from Pool X

A sequence flow cannot cross

the boundary of a sub-process

This task is redundant.

Task A is automatically

finished at output

sequence flow.

...

Send message

to Pool X

This task is redundant.

Task automatically

starts at input

sequence flow

Document X

...

Message A

About the BPMN Poster

Sub-process ÇPÆ

Message to Pool X

Wrong positioning of

message event

Message B

Thisposterislicensedunderthe

CreativeCommonsAttributionShareAlike (bysa)License

Task A

Task B Task C

Receiving

document

Starting

task A

Performing

task A

Task A

finished

ExplanationofPosterSymbols

...

Task A

Task B ...

The sub-process should

have a start event

The process should have an

end event

Authors:

GregorPolančič&TomislavRozman

Email:info@itposter.net

UniversityofMaribor

FacultyofElectricalEngineeringandComputerScience

InstituteofInformatics

Posterversion:1.0.10 (6 th October 2008)

Literatureused:BPMNSpecification1.0@http://www.bpmi.org

Important note, explanation

This task is redundant.The act of receiving

a document is a task itself.

...

Sub-process ÇPÆ

Warning or error in the BPMN model

...

Task A

Task B Task C

Recommendation

Message A

Message B

Document X

Document Y

Exception flow

Wrong model

Event Y

Althoughitisrecommendedthataprocesshasanexplicitstartandend

event,thisisnotarule.Infactstartandendeventscanbehiddeninasub

process,ifneeded,orattachedtotheboundaryofthetasksoasnotto

interruptthenormalsequenceflowbetweenthesubprocessandtherestof

theprocess.

...

Right (corrected) model

Task A

Normal flow

...

Task A

Task B ...

http://bpmn.itposter.net

Event X

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: