Architecture, distribution and integration
Cross-file traceability (UAF governance/operations)
A strategic-capabilities view whose model is split across files — traces resolve across file boundaries into one render.
uaf.strategic@1New DDN source
Why use it?
Real architectures outgrow one file; the trace view proves references stay intact when the model is partitioned.
When it helps
Multi-file models: governance in one file, operations in another, one view over both.
How to read it
- The boxes and traces read exactly as a single-file view; the file boundary is invisible in the render.
- Imports in the source declare which file supplies which elements.
What you need
- The main source file and its included files
- Qualified cross-file references
- The intended trace relationships
Things to check
- External references require the target file and its name, separated by ::.
- An included file retains its name scope; loading order never selects a target.
Scope of this diagram
Cross-file references resolved at render time; no external repository or versioning semantics are implied.
Work with the converted example
- Open the viewer and select
sv. 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.