# Business Process Model & Notation (BPMN)

> A plain-English guide to the standard shapes that map how work moves from a start to a finish.

**In short:** BPMN is a standard set of shapes for mapping how work moves from a start to a finish, using events, activities, gateways, arrows and lanes.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/business-process-model-notation-bpmn

## What you will learn

This lesson explains a drawing system called BPMN. You will learn what it is, which shapes it uses, and how a designer can read or draw a simple process with it. You do not need any prior knowledge.

A process is a set of steps that turns a starting point into a result, such as placing an online order. A diagram is a picture that shows those steps and how they connect.

- **BPMN:** Business Process Model and Notation. A shared set of shapes and rules for drawing business processes.
- **Notation:** A fixed set of symbols, where each symbol has one agreed meaning.
- **Process:** A series of steps that leads to a result.
- **Diagram:** A drawing that shows the parts of something and how they link.
- **Stakeholder:** Anyone who cares about or works on a process, such as a designer, a developer or a manager.

## Where did BPMN come from?

BPMN began with the Business Process Management Initiative (BPMI), a group that wanted one common way to draw business processes. The Object Management Group (OMG), a standards group, has looked after BPMN since its merger with BPMI in 2005. In 2011, version 2.0 arrived and the name became Business Process Model and Notation.

The OMG calls version 2.0.2 the final formal version. BPMN is also an international standard, known as ISO/IEC 19510. It is a graphical notation, so its main job is to show a process as a picture that business users and technical staff can both read.

> **Tip:** You may still see the older name, Business Process Modeling Notation. Both names describe the same BPMN acronym.

## What are the four groups of shapes?

BPMN sorts its shapes into groups. Each group has one job. Here are the four main groups.

- **Flow objects:** The main parts of a process: events, activities and gateways.
- **Connecting objects:** The lines and arrows that link those parts together.
- **Swimlanes:** Containers that show who does which work. A pool holds one participant, and a lane is a row inside a pool for one role.
- **Artifacts:** Extra information such as data objects, groups and notes.

### What are events and activities?

An event is drawn as a circle. An event is something that happens, such as a request arriving or a timer running out. An activity is drawn as a rounded rectangle. An activity is work that someone does, such as checking a form.

The border of the circle shows the event type. A start event has a thin border. An intermediate event, which happens in the middle of a process, has a double border. An end event has a thick border and marks the finish.

### What are gateways?

A gateway is drawn as a diamond. A gateway is a point where the path splits or joins. The symbol inside the diamond tells you which kind of gateway it is.

- **Exclusive gateway:** Shows an X inside. Only one path can be taken.
- **Parallel gateway:** Shows a plus sign inside. All paths run at the same time, with no choice to make.
- **Inclusive gateway:** Shows a circle inside. One or more paths can be taken.

### What are arrows and lanes?

A sequence flow is a solid line with an arrow. It shows which step comes next inside one pool. A message flow is a dashed line. It carries a message from one pool to another, for example from a customer to a company. A message flow never links two steps that sit in the same pool.

## How do you draw a simple process?

1. **Mark the start:** Place one start event at the left edge to show where the process begins.
2. **List the work:** Add an activity for each job, in the order the work happens.
3. **Add a decision:** Where the path must choose, add a gateway and label each path it creates.
4. **Link the parts:** Join the shapes with sequence flows, always pointing in the direction the work moves.
5. **Mark the finish:** Close each path with an end event.

## Shapes as data

The sample below is not a real BPMN file. It is a small lookup table that matches each shape name to its look, so you can see the idea of one name and one meaning.

```python
shapes = {
    "start event": "circle, thin border",
    "activity": "rounded rectangle",
    "gateway": "diamond",
    "end event": "circle, thick border",
}
for name, look in shapes.items():
    print(f"{name}: {look}")

```

Output:

```text
start event: circle, thin border
activity: rounded rectangle
gateway: diamond
end event: circle, thick border

```

## Check yourself

**Quick check:** In BPMN, which gateway lets only one path be taken?

A. Parallel gateway, shown with a plus sign
B. Exclusive gateway, shown with an X
C. Inclusive gateway, shown with a circle
D. Start event, shown with a thin border

**Answer:** B. An exclusive gateway shows an X and sends the flow down one path only.

## Why do designers use BPMN?

BPMN is built for business processes. It leaves out things such as organizational structures, functional breakdowns and data models, and it is not a data flow diagram.

BPMN diagrams are meant to be read by both business users and technical staff.

> **Tip:** Sketch the process in plain boxes first. Switch to BPMN symbols when your team needs one precise, shared standard.

## Sources

- [Object Management Group (OMG): Business Process Model & Notation (BPMN)](https://www.omg.org/bpmn/)
- [OMG: About the BPMN 2.0.2 specification](https://www.omg.org/spec/BPMN/2.0.2/About-BPMN)
- [IBM: What is business process modeling and notation (BPMN)?](https://www.ibm.com/think/topics/bpmn)
- [Wikipedia: Business Process Model and Notation](https://en.wikipedia.org/wiki/Business_Process_Model_and_Notation)
