Architecture, distribution and integration
Drill-down linked views
An overview whose elements declare links into a detail view — navigation as part of the model, not the tooling.
ddn@1New DDN source
Why use it?
Reviewers get lost when "see the detail diagram" is a sentence in an email; a declared link is checkable.
When it helps
Any two-level architecture: estate overview plus per-system details.
How to read it
- Elements carrying a link are the doorways; the variant is one of the targets.
- The overview stays stable while details evolve underneath it.
What you need
- The overview elements
- The detail views
- The declared links between them
Things to check
- Do not link to a view that does not exist — diagnostics catch it, reviews should not have to.
- Keep the overview to orientation; detail belongs in the target.
Scope of this diagram
Declared links resolved at render/publication time; no hyperlink protocol beyond the documents is implied.
Work with the converted example
- Open the viewer and select
overview. 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.