Goal: software behaviour
Reader: Engineers describing how a system behaves at runtime: states, calls, messaging and placement. Meta cluster: B — process & systems Scenarios: 5 · Examples: 5
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| api interaction sequence | T1 | plantuml | api-interaction-sequence.md |
| deployment topology | T1 | plantuml | runtime-deployment-topology.md |
| eip message flow | T1 | plantuml | eip-message-flow.md |
| event driven flow | T1 | plantuml | serverless-event-driven.md |
| state machine | T1 | plantuml | order-state-machine.md |
Reading order
State machines for lifecycle, sequences for the calls, messaging diagrams for asynchronous flow, deployment for where it runs.
Engines in this goal
plantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- A sequence diagram with no error path
- Deployment topology drawn without units or scaling facts