Quiz Entry - updated: 2026.10.22
Which ways are there to represent a life-cycle process, and what is each one good at?
Text, tables (state tables), sequence diagrams, activity diagrams or flowcharts, system views, and further notations such as BPMN or state diagrams; each makes a different aspect visible, so they are complementary rather than alternatives.
| Representation | Shows best | Weak at |
|---|---|---|
| Text | Context, assumptions, notes; readable by anyone | Hides gaps; nothing forces you to cover every case |
| Table / state table | Every combination of states and the action for each: completeness | The flow and the reasons behind it |
| Sequence diagram | Which object talks to which, in what order; alternatives | Decisions and data details |
| Activity diagram / flowchart | Steps and yes/no decisions of one operation | Timing between systems, state combinations |
| System view | Which systems and components take part and call each other | The order and the conditions |
| Others (BPMN, state diagram, use cases) | Standardised process notation; the states of one object | Need trained readers |
The deeper point: a process model is a communication tool. The same LCP is explained to a manager, a developer and a lawyer, and each needs a different view. In practice you combine them, for example a short text for context, a flowchart per operation, and a state table that proves every case is covered.
Go deeper:
Business Process Model and Notation (Wikipedia) — the standard process notation, with events, activities, gateways and pools.- OMG: BPMN 2.0.2 specification — the formal specification behind BPMN diagrams.
- OMG: UML 2.5.1 specification — the source for activity, sequence, state machine and use-case diagrams.