Standards families
UML class diagram — associations and classifiers
Classes with typed attributes and operations, association ends with multiplicities, navigability and aggregation.
uml.structure@2New DDN source
Why use it?
The class diagram is the shared vocabulary between domain talk and code — multiplicities make the rules checkable.
When it helps
Object-oriented design, domain modelling, or any review of "what has what, how many, owned by whom".
How to read it
- Boxes are classifiers; compartments hold attributes and operations.
- Read each association end: multiplicity, role name, navigability — each is a separate claim.
What you need
- The classifiers
- Their features
- The associations with end properties
Things to check
- Do not leave multiplicity off an end "for now" — it is the claim.
- Do not model a relationship attribute without an association class or a home.
Scope of this diagram
Declared structure with UML semantics validated; no code generation or behavioural check is implied.
Work with the converted example
- Open the viewer and select
associations. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.