# Process Analysis

**In short:** Process analysis turns a business process into a BPMN model by working through ordered questions: where it starts and ends, what steps occur, which paths exist, who takes part, and what is exchanged.

## Explanation

Process analysis builds a BPMN model step by step. BPMN is a widely used standard notation for processes, and it does not depend on any implementation environment. Work through the questions in order.

**Boundaries: where does the process start and end?**
A none start event marks where a process instance begins. It is the plain trigger. A none end event ends one execution path. The process completes when no active paths remain, so end events define the outcomes. Name events after a business state that is reached or awaited. Use an object plus a verb that expresses a state, such as "invoice received."

**Activities: what happens?**
Name each task with an object plus a verb in the infinitive, such as "check invoice." This is verb-object style.

**Paths: what can differ or go wrong?**
Model the happy path first. Then collect exceptions, prioritize them, and add them step by step. An exclusive gateway picks exactly one outgoing path based on data. A default flow covers the case where no condition holds. Label the gateway as a question. Label each outgoing flow as an answer.

**Participants and exchanges**
Message events refer to a message that passes between participants. Each message has one sender and one recipient. For the notation of participants, see the article BPMN Swimlane (Pool and Lane).

**Keeping the diagram readable**
Place the happy path on a straight line in the center. Model it left to right. Avoid crossing flows. Consider avoiding lanes in most models. Order pools so that few message flows cross between pools.

## Example

A company models how it handles a customer order.

1. Boundaries: the process starts with "order received." It ends with "order shipped" or "order rejected."
2. Activities: "check order" and "ship goods."
3. Paths: the happy path runs from receipt to shipment. A gateway asks "Order valid?" The answers "yes" and "no" lead to different paths. The team adds further exceptions later.
4. Participants: the customer sends the order as a message to the company.

## Trade-offs

Modeling the happy path first keeps the first diagram simple. It also means exceptions are added later, so early versions are incomplete. Avoiding lanes and crossing flows makes diagrams easier to read. It can also limit how much organizational detail a model shows.

BPMN diagram: [Order process: start event, tasks, a question gateway and two outcomes.](https://arc.fuet.ch/diagrams/concepts/modeling-bpmn/process-analysis/diagram-1.bpmn)

## Checks

- Each process has a start event and end events that show its trigger and outcomes.
- Tasks are named with an object and an infinitive verb.
- Exclusive gateways are labeled as questions and their outgoing flows as answers.
- The happy path is drawn on a straight line in the center, left to right, with few crossing flows.

## Related

- [BPMN Swimlane (Pool and Lane)](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-swimlane-pool-and-lane.md)
- [BPMN Event](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-event.md)
- [BPMN Gateway](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-gateway-semantics.md)
- [BPMN Layout Guideline](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-layout-guideline.md)
- [BPMN Modeling Guidelines](https://arc.fuet.ch/concepts/modeling-bpmn/bpmn-modeling-tips.md)
- [Process Analysis and Modeling](https://arc.fuet.ch/concepts/modeling-bpmn/purpose-of-process-analysis-and-modeling.md)
- [Levels of Process Modeling](https://arc.fuet.ch/concepts/modeling-bpmn/levels-of-process-modeling.md)
- [Runtime View](https://arc.fuet.ch/concepts/documentation/runtime-view.md)

## Sources

- [None events | Camunda 8 Docs](https://docs.camunda.io/docs/components/modeler/bpmn/none-events/) — docs.camunda.io, accessed 2026-11-09
- [Naming BPMN elements | Camunda 8 Docs](https://docs.camunda.io/docs/components/best-practices/modeling/naming-bpmn-elements/) — docs.camunda.io, accessed 2026-11-09
- [Modeling beyond the happy path | Camunda 8 Docs](https://docs.camunda.io/docs/components/best-practices/modeling/modeling-beyond-the-happy-path/) — docs.camunda.io, accessed 2026-11-09
- [Exclusive gateway | Camunda 8 Docs](https://docs.camunda.io/docs/components/modeler/bpmn/exclusive-gateways/) — docs.camunda.io, accessed 2026-11-08
- [Creating readable process models | Camunda 8 Docs](https://docs.camunda.io/docs/components/best-practices/modeling/creating-readable-process-models/) — docs.camunda.io, accessed 2026-11-09
- [Message events | Camunda 8 Docs](https://docs.camunda.io/docs/components/modeler/bpmn/message-events/) — docs.camunda.io, accessed 2026-11-09
- [About the Business Process Model And Notation Specification Version 2.0](https://www.omg.org/spec/BPMN/2.0/About-BPMN) — omg.org, accessed 2026-11-09