#1 Quick Reference Guides

Business Process Management

Using BPMN V2.0
By David Jones and Roderick Brown

Table of Contents Table 11: Types of Data .............................................. 8

Table 12: Types of Artefacts ....................................... 8
Introduction................................................................ 1
Table 13: Types of Connecting Objects....................... 8
Business Process Model and Notation V2.0 ............... 2
List of Figures
Background ............................................................ 2
Types of BPMN Models .......................................... 2
Figure 1: BPM Lifecycle ............................................... 2
Understanding Swim Lanes ........................................ 3
Figure 2: Descriptive Process Model sub-set of Core
Overview ................................................................ 3 Element....................................................................... 2
Pools ....................................................................... 3 Figure 3: Analytical Process Model sub-set of Core
Lanes ...................................................................... 3 Element....................................................................... 2

Understanding Events ................................................ 4 Figure 4: Example Collaboration diagram................... 3

Overview ................................................................ 4 Figure 5: Example Process Diagram ............................ 3

Start Events ............................................................ 4 Figure 6: Example Choreography diagram ................. 3

Intermediate Events ............................................... 4 Figure 7: Example Conversation Diagram ................... 3

Intermediate Boundary Events Triggers ................ 5 Figure 8: BPMN Symbol for a Pool .............................. 3
Business Process Modeling with BPMN V2.0

End Triggers............................................................ 5 Figure 9: BPMN Symbol for Lanes and Sub-Lanes ...... 3

Overview ................................................................ 5 Figure 10: Example Collaboration Diagram ................ 9

Tasks ....................................................................... 6 Figure 11: Example Process Diagram .......................... 9

Sub-Processes ........................................................ 6
Additional Forms of Activity ................................... 6 Introduction
The importance of documenting Business Processes
has been covered in many Management articles and
List of Tables texts.
Documenting business processes has been something
Table 1: Type of Events............................................... 4 organizations have commonly undertaken for more
Table 2: Start Event Triggers....................................... 4 than 30 years. In fact many productivity and quality
movements had their foundation before or during
Table 3: Intermediate Event Triggers ......................... 4
World War II. To illustrate the importance of
Table 4: Intermediate Boundary Event Triggers ......... 5 documenting your business processes, virtually all
Table 5: End Event Triggers ........................................ 5 Process Improvement approaches, such as Six Sigma
and Lean, start with documenting the business
Table 6: Types of Tasks ............................................... 6 processes being studied.
Table 7: Sub-Types of Tasks ........................................ 6 However, it is only more recently, such as over the
last 10 to 15 years, that we have seen the new
Table 8: Types of Sub-Process Activities..................... 6
discipline of Business Process Management.
Table 9: Additional Activity Markers .......................... 7
The well-known Business Process Management (BPM)
Table 10: Types of Gateways ...................................... 7 related website, BPTrends defines BPM as referring:
“…to aligning processes with the organization's
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 2

strategic goals, designing and implementing Types of BPMN Models

process architectures, establishing process The BPMN 2.0 Specification defines three “sub-
measurement systems that align with classes” (or types) of Process Models:
organizational goals, and educating and 1. Descriptive Process Models
organizing managers so that they will manage
Descriptive models document Business
processes effectively.”
Processes at an overview or high-level (i.e.
Wikipedia defines to Business Process Management minimal details) and use a limited sub-set of
as referring: BPMN’s visible elements and attributes as shown
“…to as a "holistic management" approach to below.
aligning an organization's business processes with
the wants and needs of clients. It promotes
business effectiveness and efficiency while striving
for innovation, flexibility, and integration with
technology. BPM attempts to improve processes
continuously.”

Business Process Management is based around

Figure 2: Descriptive Process Model sub-set of Core
lifecycle, which is usually defined as: Element
1.
Design 2. Analytical Process Models
6.
2. Model
Analytical models provide more detail than the
Improve
Descriptive type with an expanded sub-set of
BPM
Lifecycle BPMN’s visible elements and attributes, about
5. 3.
half the complete set.
Optimise Execute

4.
Monitor

Figure 1: BPM Lifecycle

Although this lifecycle does vary slightly between

different authors, for example some combine Design
and Mode and / or Optimize and Improve, the basic
components of the life cycle are relatively consistent.
Consequently, we will be concentrating on the Design
Figure 3: Analytical Process Model sub-set of Core Element
and Modeling of Business Processes.
3. Common Executable.
Business Process Model and Notation V2.0 Common Executable models focus on the detail
needed to explain how Business Processes can
Background be executed and use the complete set of BPMN’s
The lack of common diagramming approaches and visible Elements and attributes.
standards were a barrier to developing Business
Process Modeling as a more professional discipline.
This need for a common process diagramming
standard in late 1990’s was a key driver in a number TIP:
of different initiatives beginning in the early 2000’s. Descriptive Process Models are typically used
BPMN V1.0 was first published in 2004 by the for the process models requiring minimal
levels of detail that do not need significant
Business Process Management Initiative (BPMI).
detail, whereas Analytical Process Models are
Shortly after, in 2005, the BPMI merged with a larger
normally used to document the more
group, the Object Management Group (OMG). Since detailed process models.
2005, OMG has continued to develop BPMN, with the
latest finalized version of BPMN Version 2.0 and was
published in January 2012.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 3

The BPMN 2.0 Specification also defines that Process Understanding Swim Lanes
Models must, allow Business Processes to be
documented in the form of one of 4 different types of Overview
Process diagrams: Swim Lanes are used to represent the various Parties
1. Collaboration diagrams and Roles involved in a Process. They are represented
on the Collaboration and Process Diagrams by Pools
and Lanes.

Pools
A Pool represents a Party involved in a process.
The Pool is often used to represent a Party external to
the organization being modeled or alternatively
different areas within the organization.
Figure 4: Example Collaboration diagram

2. Process diagrams;

Figure 8: BPMN Symbol for a Pool

Under some circumstances, a Pool can also be used

Figure 5: Example Process Diagram to show a Process. However, this should be seen as
the exception rather than the norm.
3. Choreography diagrams; and
Pools can be shown as either a “White Box” or “Black
Box”:
A “White Box” Pool contains the Process details;
whereas
A “Black Box Pool” does not.
Figure 6: Example Choreography diagram

4. Conversation diagrams. TIP:

Use Black Box Pools to represent External
Parties, Organization Units outside the scope
of the Process or an IT Application or system.
Use White Box Pools to represent
Organization Units or possibly a Process.

Lanes
A Lane represents a position or role position within
Figure 7: Example Conversation Diagram the Party defined by the Pool in which it contains.
Only the Collaboration and Process diagrams are Lanes can also be further divided into sub-Lanes.
routinely used.

TIP:
Collaboration Models are frequently defined
using the Descriptive Process Modeling set of
BPMN’s visible elements. Similarly Process
Figure 9: BPMN Symbol for Lanes and Sub-Lanes
diagrams are usually defined using the
Analytically Process Modeling set of BPMN’s
visible elements. TIP:
Use Lanes to represent smaller Organization
Units, such as a Team, Positions or Roles.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 4

Understanding Events Intermediate Events

Intermediate Events trigger types sometimes occur in
Overview
two forms:
Events “happen” during the course of a Process and
Throwing – when Intermediate Event causes
affect the flow. Events have a cause (trigger) or an
something to happen; and
impact (result).
Catching – when Intermediate Event is listening and
There are three basic types of events: waiting for something to happen.
Table 1: Type of Events Typical Intermediate Events used include:

Event Type Description BPMN Symbol

Table 3: Intermediate Event Triggers
Start Events Occur at the start of a process and
Trigger Type Trigger cause BPMN Symbol
cause the initiation of a process.
None Has no specific
Intermediate Occur anywhere between the start defined trigger. Intermediate
Events and end events within the process. Event
(None)

End Events Occur at the end of a process and Message Arrival of a message
describe the results that are (Catch) or sending a Intermediate Intermediate
leading to the exit of the process. message (Throw). Event Event
(Message - (Message -
Catching) Throwing)

Start Events Timer Wait for a specific

The typical Start Events used include: date (and time),
cycle or delay, e.g.
Intermediate
Table 2: Start Event Triggers Monday at 9am, End Event
(Timer)
of the Month or 12
Trigger Type Trigger cause BPMN Symbol hours.
None Has no specific defined trigger. Compensation When the need for
Start Event compensation is Intermediate Intermediate
(None) Event Event
identified. (Compensation - (Compensation -
Catch) Throw)
Message Arrival of a message from another
process or participant. Start Event Conditional When a specified
(Message) condition is reached,
Intermediate
e.g. credit limit is Event
Timer Arrival of a specific date (and time) (Conditional)
exceeded.
or after a cycle, e.g. 9am on Start Event
Monday or 1st of the Month. (Timer)
Signal Arrival of a signal
broadcast by
Conditional When a specified condition is
another activity or Intermediate Intermediate
reached, e.g. credit limit is Conditional Event Event
sending of a signal (Signal – (Signal –
exceeded. Start Event
broadcast by Catch) Throw)

Signal Arrival of a signal broadcast by another activity.

another activity or process. Signal
Start Event
Escalation Need for escalation
is identified. Intermediate Intermediate
Event Event
Escalation Need for escalation is identified. (Escalation – (Escalation –
Catch) Throw)
Start Event
(Escalation)
Link Connect two parts of
Error Error state has been identified. the process, usually
Start Event across page Intermediate Intermediate
(Error) Event Event
boundaries or to (Link – (Link –
remove the need for Catch) Throw)

crossed lines
TIP:
Error Error state has been
The key types of Start Events commonly used
identified.
are the None, Message, Timer and Error. Intermediate
Event
However, Conditional and Escalation Start (Error)

Events are also very useful.

Use of the Signal Start Event causes a lot of
confusion with novices, so should be used
with care.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 5

TIP: TIP:
The key types of Intermediate Events The key types of Intermediate Boundary
commonly used are the None, Message, Events commonly used are Message, Timer
Timer and Error. However, Conditional, and Error. However, Conditional and
Compensation and Escalation Intermediate Escalation Start Events are also very useful.
Events are also very useful. The Link Use of the Signal Start Event causes a lot of
Intermediate Event is used for on and off confusion with novices, so should be used
page connectors. with care.
Use of the Signal Intermediate Event causes a
lot of confusion with novices, so should be
used with care. End Triggers
The typical End Events used include:

Intermediate Boundary Events Triggers Table 5: End Event Triggers

Intermediate Boundary Events are a special form of Trigger Type Trigger cause BPMN Symbol
Intermediate Events, which are triggered during the
None Has no specific defined trigger.
execution of an Activity and are defined in two forms:
End Event
(None)
Interrupting Boundary Events – which interrupts the
execution of the Activity when the trigger occurs; and Message Sending of a message to another
Non-interrupting Boundary Events – which does not process or participant. End Event
(Message)
interrupt the execution of the Activity when the
trigger occurs. Compensation When the need for
compensation is identified. End Event
The typical Boundary Intermediate Events used (Compensation)

include:
Signal Sending of a signal broadcast by
another activity. End Event
Table 4: Intermediate Boundary Event Triggers (Signal)

Trigger Type Interrupting Boundary Non-Interrupting Escalation Need for escalation is identified.
Events Boundary Events
End Event
(Escalation)
Message
Boundary Message Boundary Message
Intermediate Intermediate Event Intermediate Event
Error Error state has been identified.
Boundary Event
End Event
(Error)
Timer Intermediate
Boundary Event Boundary Timer
Intermediate Event
Boundary Timer
Intermediate Event
Terminate Indicates that all Activities in the
Process should be immediately End Event
ended. (Terminate)

Conditional
Boundary Boundary
Intermediate Conditional
Intermediate Event
Conditional
Intermediate Event
Boundary Event
TIP:
Error Intermediate The key types of End Events commonly used
Boundary Error
Boundary Event Intermediate Event are the None, Message, Timer and Error.
However, Conditional, Escalation and
Terminate End Events are also very useful.
Escalation
Intermediate Boundary Escalation Use of the Signal End Event causes a lot of
Intermediate Event

Boundary Event confusion with novices, so should be used

with care.
Signal Intermediate
Boundary Signal Boundary Signal
Boundary Event Intermediate Event Intermediate Event

Understanding Activities

Overview
Activities are used to represent work undertaken
within a Business Process. They are used to represent

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 6

the points in a Process flow where work is actually Receive A Receive Task is designed to
performed. receive a Message from an Task (Receive)

external Participant
An Activity is represented, within a Process, as either:
Business Rule A Business Rule Task is designed
An Atomic Activity – called a Task, is the simplest Task
to evaluate a business rule or to (Business Rules)
level form of Activity, i.e. cannot be broken down integrate with a Business Rule
further; or engine
A non-Atomic Activity – called a Sub-Process, is the
compound level form of Activity, i.e. able to be
broken down further. TIP:

Tasks The key types of Tasks used include, Service,

User, Manual and Business Rule.
Tasks are defined in one of two forms:
However, there are good reasons why you
Table 6: Types of Tasks
may want to also use the Send and Receive
Tasks.
Type of Task Description BPMN Symbol
Although not commonly used, the Call
Task A Task shares the same basic outline Activity form of Task can be used for re-
(Standard shape in as the Sub-Process, which is usable Tasks.
form) a rectangle with rounded corners
with a single thin line.

Call A Task used in its Call Activity form,

Activity i.e. a re-usable Task used by many
Sub-Processes
Task Processes, the thin line is changed to A Sub-Process is an Activity whose internal details
a thick line have been modeled using Activities, Gateways,
Events, and Sequence Flows in another Process
Model.
A Task represents the work performed and generally
is executed by: Sub Processes are defined in one of two sub-types
and also occur in one of two forms:
An end-user, who may optionally use an application;
or Table 8: Types of Sub-Process Activities
An application. Sub-Process Description BPMN Symbol
Type Standard Form Call Activity
Tasks can also be divided into a number of sub-types, Form
which identify specific details of how the Task is Expanded Details of the Sub-
performed or who the Task is performed by. Process are
embedded inside the
For example, the following sub-types of Tasks are Sub-Process symbol
defined: contained on the
Process Model
Table 7: Sub-Types of Tasks
Collapsed Details of the Sub-
Sub-Type Description BPMN Symbol
Process are shown
Service A Service Task is where the Task on a separate
is performed by a service, i.e. Task (Service) defined Process
some form of automation, e.g. a Model
Web service or an automated
application

User A User Task is a “workflow” Task

performed by a person with the Task (User)
TIP:
assistance of an application and
Both the Expanded and Collapsed types of
is scheduled through a task list
manager Sub-Processes are commonly used. The
Collapsed type of Sub-Process is most
Manual A Manual Task performed by a commonly used when the detail needs to be
person without the aid of an Task (Manual)
defined separately.
application, such as technician
installing a telephone. Although less commonly used, the Call
Activity form of Sub-Processes is used when a
Send A Send Task is designed to send a
Sub-Process is going to be used in many
Message to an external Task (Send)

Participant of the process places.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 7

Additional Forms of Activity Inclusive Represent a branching point in the

Gateway process that allows one or more (i.e.
In additional to the sub-types of Activity, there are
multiple) of the possible paths being
additional makers that can be added to an Activity. chosen from the available options Gateway
(Inclusive)
The two Activity markers most commonly used are: based on the evaluation of an
Expression.
Table 9: Additional Activity Markers Parallel Represent a branching point in the
Gateway process where all of the paths in the
Activity Description BPMN Symbol
Marker process must be followed. Gateway
(Parallel)

Loop The Loop marker is

Event Represents a branching point in the
used to indicate that
Based Process where the alternative paths
an Activity is repeated
Gateway that follow the Gateway are based on
sequentially until a
Events (defined after the Event Based Gateway
defined condition is (Event
Gateway) that can occur, rather than Based)
achieved.
the evaluation of an Expression.
Multi- The Multi-Instance
Complex Provide the ability to support
Instance marker is used to
show that (defined) Gateway complex merging and branching
behaviour that are not captured by Gateway
instances of an (Complex)
Activity are created other Gateways.
and executed either in
Parallel or
Sequentially.
TIP:
Although the most commonly used type of
Gateway is the Exclusive Gateway, each type
TIP: 7 can be very useful in their own right.
Loop and Multi-Instance Activities markers For example:
are both used. Loops are typically used
 Inclusive Events allow multiple paths
where the number of iterations is not known
from the Gateway to be executed
in advance, but the looping is undertaken
because the appropriate condition of
until a known condition is met, whereas
each path is true;
Multi-Instance Activities require the number
 Parallel Gateways provide a means of
of instances to be known in advance.
executing multiple paths in a process in
parallel; and
 Event Based Gateways are used when a
specific event is expected, such as
Understanding Gateways
receipt of a message, however another
Gateways are used to control how Sequence Flows event type, such as a Timer, provides
interact as they converge and diverge within a the exit point if no message is received.
Process.
Gateways do not evaluate expressions or events.
Rather, they are simply the routing mechanism.
Evaluation of any expression, for which a Gateway Understanding Data
undertake routing, must be undertaken in the
Data objects in BPMN provide the mechanism to
previous Activity.
show how data or information is created or
Typical types of Gateways used include: consumed by a process.

Table 10: Types of Gateways

There are three types of objects use to define Data:

Type of Description BPMN Symbol

Gateway

Exclusive Represent a branching point in the

Gateway process that requires one and only
one of the possible paths being
chosen from the available options Gateway
(Exclusive)
based on the evaluation of an
Expression.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 8

Table 11: Types of Data Understanding Connecting Objects

Type of Data Description BPMN Symbol There are five different types of Connecting objects
Data An item or collection of available:
Object data that is either used by
or created by an Activity Data Object Table 13: Types of Connecting Objects
(Single)
that only exists for the
Type of Artefacts Description BPMN Symbol
current life of the Process.
Sequence Shows the execution
Data Object
(Input - Single) Flows path (or order) of
(normal Process by connecting
form) Flow Objects and is the
Sequence Flow
Data Object normal and hence
(Output - Single)
typical means of
connecting two Flow
Objects.
Data Object
(Collection)
Default Defines a default path
Sequence following an Exclusive,
Data A collection of data that is Default Sequence Flow
Flow Inclusive or Complex
Store either used or created by
Gateway.
an Activity that exists
beyond the current life of Conditional Provides a pathway
the Process. Sequence from an Activity that is
Flow only followed where a Conditional Sequence Flow
Messages Content of a
defined condition is
communication that flows Message
true.
between two participants.
Message Shows the flow of
Flows information in the form
Message Flow

TIP: of Messages between

Participants.
The commonly used forms of Data Objects are
single and collection forms of Data Object and are Associations Are used to attach Data
used to show the inputs and outputs of an Activity. objects or Artefact
Association
Data Stores are used to show that data is being objects to Flow Objects,
stored beyond the life of the Process. typically Activities.

Messages are used to allow the content of a

message to be defined.

TIP:
Obviously the most common type of Connecting
Understanding Artefacts Object used is the (normal) Sequence Flow.
However, Message Flows and Associations are also
There are two different types of Artefact objects commonly used for their required purposes.
available:
The Default and Conditional types of Sequence
Table 12: Types of Artefacts Flows are also useful in certain circumstances, but
should not be over used. Rather their role should
Type of Description BPMN Symbol be used to highlight specific reasons for use. For
Artefacts
example:
Group Allows flow objects to Group  Use Conditional Sequence Flow to illustrate
Object be grouped for where one path is always followed, but
purposes of another pay may also be followed if a
documentation or certain condition is true; and
analysis.  Use Default Sequence Flow in the situation
Annotation Provides additional where it is possible not to have a path with a
Annotation valid condition, so the default path becomes
information to
elaborate an element the path followed in this situation.
within the process.

TIP:
Although using Group and Annotation Artefacts
are very useful when adding documentation to a
Process, take care not to add too many Artefacts
and making the Process Diagram difficult to read.

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 9

Case Study
The best way to understand how to apply BPMN 2.0 for your own needs is to look at some examples.

The following Models are taken from our Orbus Software Publication, BPMN by Example: An Introduction to
the Business Process Modelling Notation v2.0:

Figure 10: Example Collaboration Diagram

Figure 11: Example Process Diagram

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851
10 Steps
Quick before Initiating a TOGAF® 9 Project or Initiative
to followGuides
Reference Page 10

© Copyright 2013 Orbus Software. All rights reserved.

No part of this publication may be reproduced, resold, stored in a retrieval system, or distributed in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner.

Such requests for permission or any other comments relating to the material contained in this document may be submitted to:

Orbus Software
3rd Floor
111 Buckingham Palace Road
London
SW1W 0SR
United Kingdom

or by electronic mail to: [email protected]

www.orbussoftware.com
[email protected]
+44 (0) 870 991 1851