Darker cells mean a higher score for this topic on that metric.
LessMore
Last reviewed Sources & creditsMedia creditsMethodology
Quick answers
When should I pick Sequence diagram patterns?
When the story is: API flows, support escalations, lab protocols, checkout steps.
When should I avoid Sequence diagram patterns?
Skip it in cases like: a simple unordered checklist would tell the same story.
Who invented or popularised it?
UML sequence diagrams; text tools like PlantUML and Mermaid
What does it encode?
lifelines and ordered messages across actors
Is it OK in ads?
Yes if one claim is visible at a glance in Meta, Google and retail print; otherwise link to a full figure.
Will a teacher accept it?
Yes for lab reports and poster boards if axes, units and a source line are present.
Sequence diagram patterns encodes values as lifelines and ordered messages across actors. UML sequence diagrams; text tools like PlantUML and Mermaid.
In reports, ads and assignments it fits API flows, support escalations, lab protocols, checkout steps. Skip it when a simple unordered checklist would tell the same story.
Mistakes
- Failure modes 1 — a simple unordered checklist would tell the same story
- Failure modes 2 — 3-D pies and perspective bars
- Failure modes 3 — Dual axes that fake a correlation
- Failure modes 4 — Truncated axes that shout a small delta
- Failure modes 5 — Legend only, no direct labels
- Failure modes 6 — Missing source, unit or period
Fixes
- Fixes 1 — Return to API flows, support escalations, lab protocols, checkout steps.
- Fixes 2 — Flat, one axis, direct labels.
- Fixes 3 — Color-blind-safe palette plus pattern.
- Fixes 4 — Rewrite the title as a claim and add a source line.
Sequence diagram patterns: honour lifelines and ordered messages across actors, and switch when a simple unordered checklist would tell the same story.