HTML Diagram

Build the smallest visual model that makes the relationship easier to understand than prose alone. Match the notation and visual language to the user's project and subject. Do not force every topic into the same SVG boxes and arrows.

Choose the right model

Identify the question the reader should answer, then select the form:

• topology for components and connections;
• sequence for ordered messages over time;
• process for steps, branches, and handoffs;
• state for transitions and conditions;
• hierarchy for containment or ownership;
• timeline for change over time;
• matrix for repeated relationships;
• quantitative view when magnitude matters.

Decide what must remain visible together and what can be revealed on demand. Use a simpler form when it carries the same meaning.