JSON Visualization

Visualises a JSON payload: handy in an API design review.

• Format.puml
• Length18 lines
• Diagramjson
• Includesnone

The source

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

@startjson

title JSON Data Structure

{
  "user": {
    "id": 1,
    "name": "John Doe",
    "email": "[email protected]",
    "roles": ["admin", "user"],
    "settings": {
      "theme": "dark",
      "notifications": true
    }
  }
}

@endjson

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.
• Mind MapFor structuring thinking, not for documenting a system.
• Gantt ChartPlans, not architecture, but it renders from text, so it diffs in review.
• Work Breakdown StructureWork breakdown. Useful for scoping a piece of delivery.