Mind Map

For structuring thinking, not for documenting a system.

• Format.puml
• Length24 lines
• Diagrammindmap
• Includesnone

The source

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

@startmindmap

title Mind Map

* Project
** Planning
*** Requirements
*** Timeline
*** Resources
** Development
*** Frontend
**** Components
**** Styling
*** Backend
**** API
**** Database
** Testing
*** Unit Tests
*** Integration Tests
** Deployment
*** Staging
*** Production

@endmindmap

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.
• State DiagramForces the awkward questions about duplicate and out-of-order events.
• ER DiagramCardinality is the part people get wrong. Write it explicitly.
• 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.