BPMN 2.0 Intro Analysts
- 1 Copyright ⌘
- 2 Business Process⌘
- 3 BPMN⌘
- 3.1 BPMN benefits⌘
- 3.2 Demonstration⌘
- 3.3 Levels of BPMN Process Modelling⌘
- 3.4 BPMN Activity⌘
- 3.5 Types of Activities⌘
- 3.6 Types of Sub-Processes⌘
- 3.7 Sequence Flow⌘
- 3.8 Token ⌘
- 3.9 Sequence Flow Splitting⌘
- 3.10 Basic BPMN Flow Objects⌘
- 3.11 Gateways ⌘
- 3.11.1 Exclusive Gateway ⌘
- 3.11.2 Exclusive Gateway Example⌘
- 3.11.3 Merging (exclusive)⌘
- 3.11.4 Parallel Gateway ⌘
- 3.11.5 Parallel Gateway Example 1⌘
- 3.11.6 Parallel Gateway Example 2⌘
- 3.11.7 Gateway Exercises⌘
- 3.11.8 Inclusive Gateway ⌘
- 3.11.9 Inclusive Gateway Example 1⌘
- 3.11.10 Inclusive Gateway Example 2⌘
- 3.11.11 Gateway Exercises 2⌘
- 3.12 Events ⌘
- 3.13 Events ⌘
- 3.14 Pool and Participant⌘
- 3.15 Messages and Message Flows ⌘
- 3.16 4 Basic Message Events ⌘
- 3.17 Timer Events ⌘
- 3.18 Interrupting vs. Non-Interrupting⌘
- 3.19 Event-Based Exclusive Gateway⌘
- 3.20 Artifacts ⌘
- 3.21 Types of Tasks ⌘
Most of our training material is based on the BPMN 2.0 Specification http://www.omg.org/spec/BPMN/2.0/
BPMN 2.0 Spec:
A Process describes a sequence or flow of Activities in an organization with the objective of carrying out work.
Howard Smith, Peter Fingar, Business Process Management – The Third Wave, Meghan Kiffer, 2006:
Business Process is the complete and dynamically coordinated set of collaborative and transactional activities that deliver value to customers.
by Bruce Silver
- Process Logic (Process Model) is a complete map of all the paths from the triggering event to any defined end state.
- Process Model is more than documentation of one instance of the process.
- Process logic is usually hidden.
- Business Process Model and Notation (BPMN)
- OMG standard
- similar to flowchart diagram, but
- formal (specification - http://www.omg.org/spec/BPMN/2.0/)
- event based
- with message flows
- standard notation maintained by OMG
- not vendor specific
- Simple process
Levels of BPMN Process Modelling⌘
by Bruce Silver - Three Levels of Process Modeling with BPMN, BPMS Watch, April 2008
- Descriptive modeling
- Abstract, high-level, simple to communicate across the organization
- Requires understanding of fundamental concepts such as pools and lanes, tasks and subprocesses and sequence flow, not the complexities of BPMN's various flow control and event patterns
- Analytical modeling
- More details, showing all the steps, including the exception paths required to analyze process performance using simulation or to create details requirements for an IT implementation. Requires understanding of BPMN's various decisions and merge patterns, event and exception handling patterns. Hierarchical representation of the end to end business process
- Executable modeling
- BPMN is a part of the executable process implementation. Imposes many validation constraints.
- Modeling at this level is somewhat vendor tool-dependent.
- is work that is performed within a Business Process
- can be atomic or non-atomic (compound)
- represent points in a Process flow where work is performed
- is executable element of a BPMN process
Types of Activities⌘
- an atomic Activity within a Process flow
- is used when the work in the Process cannot be broken down to a finer level of detail
- compound activity
- Event Sub-Process
- compound activity
- Call Activity
- allows the inclusion of re-usable Tasks and Processes in the diagram
Types of Sub-Processes⌘
A Sequence Flow is used to show the order that Activities will be performed in a Process.
- Token traverses the Sequence Flows and passes through the elements in the Process
- A token is a theoretical concept that is used as an aid to define the behavior of a Process that is being performed
- The behavior of Process elements can be defined by describing how they interact with a token as it “traverses” the structure of the Process.
- A token does NOT traverse a Message Flow
Sequence Flow Splitting⌘
- Conditional flow - sequence flow with a condition that is evaluated to determine whether or not the sequence flow will be used
- Default flow - used only if all the other outgoing conditional flows are not true
Basic BPMN Flow Objects⌘
Gateways are used to control splitting and merging of sequence flows.
Exclusive Gateway ⌘
- A diverging Exclusive Gateway (Decision) is used to create alternative paths within a Process flow
- Only one of the paths can be taken, this means the gateway is exclusive
- A Decision can be thought of as a question that is asked at a particular point in the Process
- The question has a defined set of alternative answers
- Each answer is associated with a condition Expression that is associated with a Gateway’s outgoing Sequence Flows
Exclusive Gateway Example⌘
Parallel Gateway ⌘
- A Parallel Gateway is used to create or synchronize (combine) parallel flows
- A Parallel Gateway creates parallel paths without checking any conditions; each outgoing Sequence Flow receives a token upon execution of this Gateway
- For incoming flows, the Parallel Gateway will wait for all incoming flows before triggering the flow through its outgoing Sequence Flows
Parallel Gateway Example 1⌘
Parallel Gateway Example 2⌘
- Exercise 1.
- Exercise 2.
- Demonstration - splitting and merging
Inclusive Gateway ⌘
- A diverging Inclusive Gateway (Inclusive Decision) can be used to create alternative but also parallel paths within a Process flow
- Unlike the Exclusive Gateway, all condition Expressions are evaluated
- The true evaluation of one condition Expression does not exclude the evaluation of other condition Expressions
- All Sequence Flows with a true evaluation will be traversed by a token
- Since each path is considered to be independent, all combinations of the paths MAY be taken, from zero to all
- However, it should be designed so that at least one path is taken.
Inclusive Gateway Example 1⌘
Inclusive Gateway Example 2⌘
Gateway Exercises 2⌘
- Exercise 3.
- Exercise 4.
An Event is something that “happens” during the course of a Process.
- Events affect the flow of the Process and usually have a cause or an impact. The term “event” is general enough to cover many things in a Process.
- The start of an Activity, the end of an Activity, the change of state of a document, a Message that arrives, etc., all could be considered Events
- Types of events:
- Start Events - indicate where a particular Process will start
- Intermediate Events - indicate where something happens (an Event) somewhere between the start and end of a Process
- Boundary Intermediate Events - attached to the boundary of an Activity
- End Events - indicate where a Process will end
- None Event does not have a defined trigger or result.
- The Event MUST be displayed without a marker
- None Start Event starts the process and generates new token
- None End Event ends a particular flow and consumes the token
- Exercise 1.
Pool and Participant⌘
- The pool shape represents a participant.
- A Lane is a sub-partition within within a Pool.
- Lanes are used to organize and categorize Activities.
- The meaning of the Lanes is up to the modeler.
- Lanes are often used for such things as internal roles (e.g., Manager, Associate), systems (e.g., an enterprise application), an internal department (e.g., shipping, finance),
Messages and Message Flows ⌘
- A Message represents the content of a communication between two Participants.
- A Message Flow is used to show the flow of Messages between two Participants that are prepared to send and receive them.
- A Message Flow MUST connect two separate Pools. They connect either to the Pool boundary or to Flow Objects within the Pool boundary. They MUST NOT connect two objects within the same Pool.
- Pool, Lane, Blackbox
4 Basic Message Events ⌘
Message Events Example⌘
- Exercise 1.
- Exercise 2.
- Exercise 3.
Timer Events ⌘
- Expresses a time gap in processing or a wait for a period of time.
- Start Timer – start on specific date (Monday at 9am, etc..)
- Intermediate Timer - a specific time-date or a specific cycle (e.g., every Monday at 9am)
- If used in the main flow it acts as a delay mechanism
Timer Example 1⌘
Timer Example 2⌘
Interrupting vs. Non-Interrupting⌘
Boundary Events Exercises⌘
- Exercise 1:
Event-Based Exclusive Gateway⌘
- The Event-Based Gateway represents a branching point in the Process where the alternative paths that follow the Gateway are based on Events that occur
- This is opposed to the evaluation of Expressions using Process data (as with an Exclusive or Inclusive Gateway which are Data Based)
- A specific Event, usually the receipt of a Message, determines the path that will be taken
- Basically, the decision is made by another Participant, based on data that is not visible to Process, thus, requiring the use of the Event-Based Gateway.
- A company is waiting for a response from a customer they will perform one set of Activities if the customer responds “Yes” and another set of Activities if the customer responds “No.”
- The customer’s response determines which path is taken
- The identity of the Message determines which path is taken
- That is, the “Yes” Message and the “No” Message are different Messages
- The receipt of the Message can be modeled with an Intermediate Event with a Message trigger or a Receive Task
- In addition to Messages, other triggers for Intermediate Events can be used, such as Timers
Event-Based Gateway Starts a Process⌘
Event-Based Gateway Exercises⌘
- Exercise 1:
- Exercise 2:
Artifacts are used to provide additional information about the Process
- Provides a visual mechanism to group elements of a diagram informally.
- Group can be used for documentation or analysis purposes.
- Groups do not affect the flow of the Process.
Text Annotation ⌘
- Is a mechanism for a modeler to provide additional information for the reader of a BPMN Diagram
- The Text Annotation object can be connected to a specific object on the Diagram with an Association
- Does not affect the flow of the Process
Types of Tasks ⌘
Receive Task ⌘
- Waits for a Message to arrive from an external Participant
- Once the Message has been received, the Task is completed
- Starts the process
- MUST NOT have any incoming Sequence Flow
- Instantiate attribute MUST be set to true
Send Task ⌘
- Sends a Message to an external Participant.
- Once the Message has been sent, the Task is completed.
Asynchronous Communication - tasks⌘
Asynchronous Communication - events⌘
Service Task ⌘
- uses some sort of service, which could be a Web service or an automated application.
Synchronous Communication ⌘
User Task ⌘
- A typical “workflow” Task where a human performer performs the Task with the assistance of a software application
- Phone operator updates customer record
- User changes his password
Manual Task ⌘
- Is expected to be performed without the aid of any business process execution engine or any application
- A telephone technician installing a telephone at a customer location
Business Rule Task ⌘
- Provides a mechanism for the Process to provide input to a Business Rules Engine and to get the output of calculations that the Business Rules Engine might provide
Script Task ⌘
- Is executed by a business process engine
- The modeler or implementer defines a script in a language that the engine can interpret
- When the Task is ready to start, the engine will execute the script
- When the script is completed, the Task will also be completed.