Time, composition and linked documentation
Linked diagrams and documentation views
Several views over one model: an overview with links into detail views at different audiences.
ddn@1New DDN source
Why use it?
One model, many readers — the links keep every audience on the same facts.
When it helps
Any documentation set where executives and implementers read the same system.
How to read it
- The overview is a map, not a simplification to maintain separately.
- Detail views are selections of the same model — they cannot drift apart.
What you need
- The audiences
- The overview contents
- The detail views per audience
Things to check
- Do not maintain a separate "simplified" copy of the model.
- Do not link to a view that no longer selects what the link promises.
Scope of this diagram
Composition documentation; navigation is a reading aid, not an application.
Work with the converted example
- Open the viewer and select
diagram. 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.