BPMN 2.0 - an introduction to the Level 1 Palette

BPMN 2.0Introduction to the Level 1 Palette

by Declan Chellar

Scope of this slide deck

• In: an introduction to the shapes of the Level 1 Palette of BPMN 2.0

• In: textual explanations of the purpose of each shape

• In: stand-alone visual examples of the use of each shape

• Out: an example start-to-finish process model

What is BPMN?

• “Business Process Model and Notation”

• A graphical technique for modelling business processes

• Based on flowcharting

• An expressive language with vocabulary, grammar and syntax

• Managed by the Object Management Group

Why use BPMN?

• It is an international standard, the lingua franca of process modelling

• Easily understood by non-technical business people

• Caters well for event-based process modelling

• Caters well for exception scenarios

• Caters well for hierarchical modelling

Why use the Level 1 Palette?

Any of the following is a good reason to stick to Level 1:

• You are not familiar with the shapes of the Level 2 Palette

• You are modelling an initial overview of a process

• You want a simple (non-executable) model of a process

• You don’t need to model event-triggered behaviour

First some symbols

• Instructions appear with this symbol:

• Handy tips appear with this symbol:

• Warnings appear with this symbol:

• Quotes from the BPMN 2.0 Specification appear with this symbol:

(along with a reference to the relevant section in the specification)

Pools and Lanes

This is a Pool. It represents an

entire Process from start to finish.

The process name

goes here.

Process names are always verb phrases and should reveal the

intent of the process.

These are all good process names

because the verbs directly address the core activity and

intent of the process.

Replace

Customer Card

Request Vacation

Add New Account

Switch

Customer Account

Noun phrases do not make good

process names because processes are about activity and a phrase that lacks a verb obscures the core activity of the process.

Customer CardReplacement

Vacation Request

New Account

Switch

Customer Account

Within a Pool, we must

have at least one Lane. A Lane represents the

Performer of any tasks that sit within that Lane.

The Performer name

goes here.

The Performer name

goes here.

Performer names are always

noun phrases and can represent individual roles, teams, departments or can

represent a desire for Activities to be automated.

Personnel Manager

Claims

Adjuster

System

(for Activities to be automated)

Accounts

Department

These are all good Performer names.

Those who perform activities within the same process must be modelled as Lanes within

the same process Pool.

You can also have Pools outside

the process, to indicate entities or other processes that interact with

the process you are modelling.

If we do not model what happens

inside them, they are known as Black Box Pools.

We do not model what happens inside a Black Box Pool because:

• we do not know• or we do not care

• or we cannot control it

However, if we do know what goes

on inside the other Pool and we can control it and we do care, then we

model it as another White Box Pool.

Message X Received

Request Information Y

Send Message Z

Receive Information Y

Message X

Request for Information Y

Information YMessage Z

We show the interactions

between Pools with Message Flows.

Message X Received

Send Message Z

Message X

More on Sub

Processes shortly.

Tasks must sit within the Lane that performs the

You don’t have to indicate the Task type but it does add clarity.

User (person symbol):

In the Level 1 palette, the User Task type represents any atomic activity carried out by a human.

Service (gears symbol):

In the Level 1 palette, the Service Task type represents any

automated, atomic activity.

Sequence Flows

A Sequence Flow is used to show the order of Flow Elements in a Process.

(section 8.3.13)

To show the order of flow

between shapes, we use the Sequence Flow shape.

To show sequence flow, we

use the Sequence Flow shape.

There are different types of arrow-

headed shapes in BPMN, so get used to calling this one by its correct name: Sequence Flow

A Sequence Flow can have only one source

and one target.

Sequence Flows must always

stay within a Pool.

Sequence flows may never

cross a pool boundary.

Message Flows

A Message Flow is used to show the flow of Messages between

two Participants that are prepared to send and receive them.

(section 9.3)

Message XReceived

Message X

Catching Message Events

(white envelope) musthave an incoming Message

Flow from the boundary of another Pool.

Message XReceived

Send Message Y

Message X Message Y

Throwing Message Events

(black envelope) musthave an outgoing Message

Flow to the boundary of another Pool.

Message XReceived

Send Message Y

Message X Message Y

Message Flows may only

pass between Pools.

Message X

Message Flows may never

pass within a Pool.

Message X Received

Send Message Z

Message X

What shapes can send Messages?

Message

Throwing Event

Black Box Pool

boundary

Black Box Pool

boundary

Message X Received

Send Message Z

Message X

What shapes can

receive Messages?

Message

Catching Event

Black Box Pool

boundary

Black Box Pool

boundary

Sub Processes

A Sub-Process is an Activity whose internal details

have been modeled using Activities, Gateways, Events, and Sequence Flows. A Sub-Process is a

graphical object within a Process, but it also can be “opened up” to show a lower-level Process.

(section 8.3.13)

Sub Processes allow you to

model the details of a Process hierarchically.

Sub Processes also allow you to group activities logically for the

sake of tidiness.

The details of a collapsedSub Process are shown on

another (child) canvas.

BOutcome

Outcome B

Outcome A

Collapsed Sub Processes must sit within the Lane where the first task of that Sub Process

is performed, even though subsequent Tasks may be performed in other Lanes.

The details of an expanded Sub Process are shown at the same level as the Sub Process shape

itself.

A Sub Process inherits its Pool from

the parent, so you are only required to show the Pool at the

top level of your model.

However, you should

show any relevant Lanes at the Sub Process level.

Sub Processes must have oneun-labelled Start Event of the

type “None”.

This is because the trigger for

the Sub Process is already known: it is the previous

Activity at the parent level.[P

Sub Processes must have oneun-labelled Start Event of the

type “None”.

Sub Processes must at least

one End Event.

Sub Processes must at least

one End Event.

There is no need to label a Sub Process End Event

if there is only one.

Determine Outcome

Outcome BOutcome

Outcome A

You must label Sub Process

End Events if there are more than one.

Gateways

Gateways are used to control how Sequence Flows interact as they

converge and diverge within a Process.(section 8.3.13)

We use a Gateway shape to navigate the diagram

when optional or multiple paths are possible.

No processing takes place within a Gateway, i.e., it

contains no logic. It is nothing more than a visual navigation

device for your diagram.

Because no processing takes place within a Gateway, be careful not

to call them ‘Decision Points’.

Determine Credit Limit

Credit Limit

Any Decision logic should be contained

within a previous Activity and the Gateway should be labelled accordingly.

Credit Limit

Any logic should be contained within a previous Activity and the Gateway

should be labelled accordingly.

Remember we said that the

performance of work is represented only by Activity shapes.

A plain, Exclusive Gateway like this means that the process follows only one of the subsequent Gates, (i.e.,

the one where the outcome labelled on the Gate is true).

An Exclusive Gateway can also be indicated like this.

The Sequence Flows that

follow a Gateway are called Gates.

Credit Limit

Sufficient

Insufficient

Label the Gates coming out of the Gateway to cover all

allowed outcomes.

BOutcome

Outcome B

Outcome A

When a Sub Process has more than

one End Event, you must use an Exclusive Gateway at the parent level to interrogate the outcome.

Use Parallel Gateways to

model paths that the process follows in parallel.

With a Splitting Parallel Gateway, all paths following the Gateway

are activated as soon as the process reaches the Gateway.

With a Joining Parallel Gateway, the process does not continue until all

incoming paths are complete.

Data Shapes

Use a Data Object to represent transient data that is passed within a process but which does not need to

exist outside the process.

Use a Data Store to represent data that persists beyond the

scope of the process.

Use a Data Store to represent data that persists beyond the

scope of the process.

A Data Store is not necessarily

a database! It is simply a logical representation of

persisted data.

A sheet of paper could be used as a Data Object but it is discarded at some point before the process ends.

A sheet of paper could be

used as a Data Store but it is kept to be used after the

process ends.

We label both Data Objects and Data Stores to indicate the business concept of the data but not to indicate the

name of a database.

Customer Phone Number

Customer Account Details

Data Objects and Data Stores must

be connected to Activity shapes with Data Associations to show the flow of data from and to Activities.

Annotation

Annotations are a useful

way to add clarity to a process model.

Annotation

But do not use an Annotation

where clarity can be provided by an Event, Activity Gateway, Message Flow, Data Object or Data Store.

Off-page Connectors

Generally used for printing, this object will show where a Sequence Flow leaves one page and then restarts on the next page.

(table 7.2)

You can use an Intermediate Link

Event as an off-page connector when you need to split your

diagram across two canvasses.

As the name implies, the Intermediate Event

indicates where something happens (an Event) somewhere between the start and end of a

Process. It will affect the flow of the Process, but will not start or (directly) terminate the Process.

(section 10.4.4)

An Intermediate Event is

represented by a circle with a double, thin border.

An Intermediate Event is

represented by a circle with a double, thin border.

White for

“catching”.

Black for

“throwing”.

The Intermediate Link Event is the only type of Intermediate Event in

the Level 1 Palette.

Use the Intermediate Link Event sparingly. Instead, try to use Sub

Processes to keep each diagram of your model tidily on a single canvas.

This has been a basic introduction to the Level 1 Palette of BPMN 2.0

ESSENTIAL REFERENCE WORKS:

“BPMN Method and Style” by Bruce Silver“Process and Decision Modelling in BPMN/DMN” by Tom DeBevoise and James Taylor

(both books available in paperback and for Kindle)

The BPMN Specification:http://www.omg.org/spec/BPMN/2.0/

www.chellar.com/AnalysisFu/

LinkedIn: es.linkedin.com/in/declanchellar/

Twitter: @AnalysisFu

Care to discuss further?

BPMN 2.0 - an introduction to the Level 1 Palette

process pool

process steps

entire process

good process names

sub process shape

good start event labels

basic types

good performer names

Business

BPMN 2.0 & PAVONE Notation

Bpmn 2.0 by Example Version Alpha 8

BPMN 2.0 und die X4 BPM Suite

BPMN 2.0 Tutorial - CRaG Systems - UML · PDF fileusing the....

BPMN 2.0 (ejemplos) - ilapep.mx · BPMN 2.0 (ejemplos)...

BPMN 2.0 patterns & real life examples

BPMN 2.0 RFP - Object Management Group

BPMN 2.0 Analytical Constructs - Jarrar › courses › BPMN...

Nomenclatura manual bpmn 2.0

BPMN 2.0 Example Document

BPMN 2.0 für fachliche Prozessmodellierung

BPMN 2.0 Handbook Digital Edition

BPMN 2.0 Introduction

2.0 MATERIAL PALETTE

BPMN Models - sparxsystems.fr · Table of Contents BPMN...

Bpmn 2.0 Eclipse OMG/Symposium