Skip to content
DiaGO

Software design,
explained visually.

Learn UML, object-oriented design, design patterns, databases, APIs, and software architecture—then build and validate your diagrams in the same workspace.

Free while in early access · no sign-up needed for Studio

library-system.diagoo — class diagram
Member- name: String- memberId: String+ borrow(book: Book)+ activeLoans(): ListBook- title: String- isbn: String+ isAvailable(): boolLoan- dueDate: Date- returnedAt: Date+ isOverdue(): bool10..*0..*1borrows0 errors · 0 warnings

DiaGO Desktop for Windows

The eight studios as a Windows app — your files stay on your computer, and it works offline.

Download v1.0.0

One loop, one workspace

Stop learning on one platform and redrawing diagrams in another. In DiaGO the article, the example, and the editor are the same surface.

  1. 1Learn

    Read a concept with its notation and reasoning

  2. 2Inspect

    Study a real example diagram

  3. 3Edit

    Open it in Studio and make it yours

  4. 4Validate

    Get deterministic feedback on the model

  5. 5Export

    Save it as .diagoo, PNG, SVG, or PDF

Built to teach, not just to draw

  • Documentation that explains why

    Every concept covers notation, when to use it, when not to, and the design reasoning behind it — not just what the arrows look like.

    Browse the docs
  • Eight real diagram editors in the browser

    Class, sequence, use-case, activity, state machine, ER, component, and deployment diagrams — each with a palette, inspector, undo/redo, autosave, and export. No account required.

    Choose a studio
  • Validation that teaches

    Deterministic rules catch inheritance cycles, dangling relationships, and broken multiplicities — and explain why each one matters.

    See how it works
  • Learning built into the canvas

    Select a composition edge and DiaGO tells you what the notation means, when to reach for it, and the mistakes to avoid.

    Read about composition
OrderOrderLine*

Error

The whole's end of a composition says * ("Order"); it can be at most 1.

Why it matters
In a composition a part belongs to at most one whole at a time, so the multiplicity at the whole's (diamond) end must be 1 or 0..1. More than one owner is aggregation, or a plain association.
How to fix it
Set the multiplicity at the diamond end to 1 (or 0..1 if the part can exist on its own for a while), or use aggregation if the part is really shared.

Design your first system today

Pick a studio, drop two elements on the canvas, and connect them. DiaGO explains the rest as you go.