Skip to content
DiaGO

Introduction to DiaGO

What DiaGO is, how the documentation, Studio, examples, and guided projects fit together, and where to start.

DiaGO is a workspace for learning software design by doing it. Every concept in these docs — from objects and classes to layered architecture — is paired with an editable example you can open in the Studio, modify, validate, and export. The premise: reading about design teaches you notation; changing a design and watching the consequences teaches you judgment.

Reading that composition means "the whole owns the parts and controls their lifetime" takes thirty seconds. Deciding whether an Order should own its OrderLine objects by composition, or merely reference products shared with the rest of the catalog, is where the actual learning happens. DiaGO is built so you spend most of your time on that second kind of question.

The core loop

Every topic on the platform follows the same cycle: Learn -> Inspect -> Edit -> Validate -> Export.

  1. Learn. Read the docs article. Articles explain reasoning, not just notation: why the concept exists, what it buys you, and what it costs. Where formal UML semantics differ from common industry convention, the article says so explicitly.
  2. Inspect. Open the worked example that accompanies the article — a small, realistic model such as a library loan system or a payment flow, not a Foo/Bar toy.
  3. Edit. Modify the example in the Studio. Examples are deliberately imperfect in places; the exercises ask you to find and fix specific weaknesses.
  4. Validate. The Studio checks your diagram against structural rules, and the checks are deterministic: the same diagram produces the same findings, every time. Validation catches mechanical mistakes — a class inheriting from itself, an association end with no multiplicity. It does not judge whether your design is good. That judgment is the skill you are here to build, and no validator can automate it.
  5. Export. Take the result out as an image for an assignment or a design review, or keep iterating.

Starting from a flawed-but-working example instead of a blank canvas is deliberate. A blank canvas hides what you do not know; an existing model forces you to make, and defend, concrete decisions.

The four surfaces

SurfaceWhat it isUse it when
/docsReasoning-first articles on OOD, UML, SOLID, GRASP, patterns, databases, APIs, and architectureYou want to understand a concept before applying it
/examplesA gallery of editable diagrams, organized by topic and domainYou learn best by reading real models and picking them apart
/studioA browser-based diagramming studio with six editors — class, sequence, use-case, ER, component, and deployment — each with deterministic validation and an AI "Explain" review. No account required; work autosaves in your browserYou want to build, validate, or review a model
/learnGuided, syllabus-style projects that chain several concepts into one buildYou want structure and a finished artifact at the end

Press Ctrl+K (Cmd+K on macOS) anywhere to search across all four.

Where to start with the editors

Class diagrams are the recommended starting point. They carry most of the structural vocabulary the rest of design builds on — associations, aggregation, generalization — and they are the diagram type you are most likely to be asked to produce, whether in a course or in industry. Once the vocabulary is familiar, the other five editors follow the same interaction model.

Where to start

Two common entry points:

  • You are new to object-oriented design. Start with Objects and Classes. It builds the vocabulary — state, behavior, identity, responsibility — that every later article assumes. Skip it, and the UML articles will read as arbitrary notation rules instead of answers to design questions.
  • You have a UML assignment due. Go straight to Class Diagrams, then Associations for multiplicities and navigability. Open a matching example from /examples, adapt it in the Studio, validate, and export. A deadline pulling you through the concepts works better than reading front to back.

Either way, the loop is the same: read a little, open the example, break it, fix it, export it.