State Diagram

Forces the awkward questions about duplicate and out-of-order events.

• Format.puml
• Length22 lines
• Includesnone

The source

22 lines of PlantUML, and needs nothing beyond the bundled engine. Copy it, or open the template inside Gnomon and render it as it is.

@startuml

title State Diagram

[*] --> Idle

state Idle {
  [*] --> Waiting
  Waiting --> Waiting : timeout
}

Idle --> Processing : start
Processing --> Success : complete
Processing --> Error : fail

Success --> Idle : reset
Error --> Idle : reset
Error --> Processing : retry

Success --> [*]

@enduml

Others in UML and standard diagrams

• Sequence DiagramThe highest-value diagram in this list. Time runs down; participants across.
• Activity / Flow DiagramEarns its place when there are real branches and joins.
• Use Case DiagramActor-to-goal. Dated, but still the clearest way to show scope boundaries.
• Class DiagramBest used for a single bounded context, not a codebase.
• ER DiagramCardinality is the part people get wrong. Write it explicitly.
• Mind MapFor structuring thinking, not for documenting a system.
• Gantt ChartPlans, not architecture, but it renders from text, so it diffs in review.
• JSON VisualizationVisualises a JSON payload: handy in an API design review.
• Work Breakdown StructureWork breakdown. Useful for scoping a piece of delivery.