BPMN: Business Process Model and Notation
Introduction to BPMN
BPMN stands for Business Process Model and Notation and is a standard for modelling business processes. BPMN is divided into the following diagram types:
- Process Diagram
- Collaboration diagram (Collaboration Diagram)
- Choreography Diagram (Choreography Diagram)
- Conversation Diagram
BPMN with Enterprise Architect
In this course you will learn how to use Business Process Model and Notation (BPMN) in the Enterprise Architect tool and how the implementation of BPMN differs from other process description languages.
Process diagramm
This is the most commonly used type of BPMN diagram and is used to visualise the processes within an organisation. A process diagram shows the sequence of activities (steps) and decisions that are made in a specific business process, as well as events that are reacted to during the course of the process. The most important language elements in the process diagram are activities, gateways (decision points), events (start, intermediate events, end events) and sequence flows, which are the connections between the elements.
In contrast to other process description languages such as the UML activity diagram, BPMN offers a more explicit way of describing decisions and defining events.
In BPMN we have the choice of 5 different types of gateways (decision nodes):
Exclusive Gateway:
For either/or decision, exactly one condition occurs and only one branch in the process flow is executed. Two alternative graphical representations are available here.
Inclusive Gateway:
For or-decision (with the possibility that several cases may apply)
Parallel Gateway:
All outgoing process flow branches are executed. When merging with parallel gateways, all process flows must have arrived at the parallel gateway before the process is continued.
Complex Gateway:
Typically used when the decision logic involves multiple variables or when a combination of different incoming and outgoing sequence flows are controlled based on complex rules.
Event Based Gateway:
It enables the branching or merging of process flows based on the occurrence or non-occurrence of certain events. In contrast to the complex gateway, which is based on conditions, the event-based gateway takes into account the occurrence of events, such as the arrival of a message or the reaching of a certain point in time.
The 5 gateways at a glance
Events
With events, we distinguish between start events, intermediate events and end events. Each event can in turn be specially configured and react to a message, a signal, an error, a cancellation, etc., for example. A distinction is also made between interrupting and non-interrupting events.
A special event is the compensation event, which can be used to simply describe the unwinding of a business process. BPMN thus provides us with a powerful yet easy-to-understand language for describing simple to very complicated business processes using the same language and in an understandable way.
Collaboration Diagram
Collaboration diagrams extend the process diagrams with the representation of interactions between different business units or organisations. They show how processes work together across organisational boundaries (business unit, organisations, roles) and how information flows (so-called messages) take place between different roles or organisations. These diagrams contain pools and lanes.
Pools are used to describe different participants, e.g. a business partner or organizational unit. A pool can be displayed as a white or black box, with a displayed process (white box) or without (black box). No sequence flows (relationships between BPMN activities) may be used between pools, only messages. With a black-box pool, the messages are created directly from pool to pool or from pool to BPMN activity from which the message originates or is received.
Lanes look graphically like pools and are used to organize BPMN activities. A lane describes, for example, a role that is responsible for the process steps (BPMN activities) contained in the lane. Lanes are often nested in pools, but can also stand alone. In contrast to pools, lanes allow sequence flows (relationships between BPMN activities) to be created across lane boundaries, unless the lane is located in another pool.
Process Diagram
A process diagram can easily be extended to a collaboration diagram by nesting the individual process diagrams in pools and lanes.
With Enterprise Architect, you only need a new diagram (electronic drawing sheet) to show the existing processes and their pools. In another diagram, the pools and lanes can be omitted in order to have a pure process diagram view.
The single point of information principle applies here: there is a model (given model structure with relationships between the elements) and one or more diagrams, each of which shows the sections and levels of detail of the model that are relevant for a stakeholder.
Choreography Diagram
A choreography diagram focuses on the exchange of information between two or more participants in a process without showing the internal processes of the participants. It shows how the participants interact with each other and the order in which the interactions take place. This is particularly useful to illustrate the exchange of messages and responsibilities between the parties involved.
Conversation Diagram
These diagrams provide a simplified view of a choreography or collaboration by showing the participants involved and the message flows between them, without going into specific details of the process flows. Conversation diagrams are useful for providing an overview of all business communications within a process.
Each of these diagram types has its specific areas of application and advantages, depending on which aspect of a business process you want to highlight or analyse.
Buy Enterprise Architect
Are you working with an older version of Enterprise Architect and would like to upgrade to the latest version? Here you will find an overview of the licence prices in direct comparison.
FAQs on process modelling
What is process modelling?
Business process modelling refers to the simplified and comprehensible description and graphical presentation of company processes. The data is visualised using symbols and flowcharts, which makes the processes in the company transparent. In addition, key figures and risk assessments are created. Ultimately, the choice of modelling language (e.g. BPMN) determines which concepts are used for the process description.
Process modelling methods include, for example
- Process maps provide a holistic overview of company structures
- Flowcharts are used to visualise individual sub-processes
- Event-driven process chains (EPC) are focussed entirely on functions and the resulting events (e.g. an order triggers further events)
What is BPMN and how does it support the further development of business processes?
The Business Process Model and Notation (BPMN) is a graphical specification language in process management and is being further developed by the OMG. It describes business processes and workflows in order to achieve the goals agreed with the corporate strategy.
The focus of BPMN is on notation and therefore on the graphical representation of business processes. The diagrams in BPMN are called Business Process Diagrams (BPD) and are intended to support the development of processes by human experts.
Version 2.0, released in 2011, standardises an XML-based format in which BPMN diagrams are saved. It is used for the exchange between different tools, for example for modelling, simulation or the execution of process models.
Thanks to the abstract symbol definition of BPMN, a comprehensive view of both human and machine processes is possible. In this way, it creates overall transparency.
What is the goal of process modelling?
Process modelling records business processes in order to be able to analyse and document them and thus gain a better understanding of organisational processes.
The following objectives are pursued in detail:
- Transparency: Everyone involved in the process should be aware of the exact procedure
- Improvements: Process modelling reveals weaknesses and inefficient processes that can then be optimised
- Communication: The clear and unambiguous representation in the model facilitates communication between all stakeholders
- Standardisation: Modelling standardises processes and workflows and thus helps to improve quality
- Faster familiarisation: Thanks to clearly modelled processes, the familiarisation time is reduced
- Compliance and quality: By documenting the processes in the model, it becomes clear that legal requirements are being met and internal quality standards are being observed
- Automation: Process models are an excellent basis for automation and digitalisation
- Risk management: process risks are very clearly identified in the models and countermeasures can be developed
Process modelling therefore serves to make business processes more transparent and flexible, thereby increasing an organisation’s competitiveness.
