Matrices, tables and analysis panels
General model-derived relationship matrix
Any two model lists crossed: elements on both axes, cells marking which pairs relate and how.
matrix.relations@1New DDN source
Why use it?
Cross-checks ("every X is covered by a Y") become visual gaps instead of list-diffing by hand.
When it helps
Coverage checks: capabilities↔systems, requirements↔tests, teams↔systems.
How to read it
- Rows are one model list, columns another; a marked cell means the pair relates.
- An empty row or column is the finding: something relates to nothing.
What you need
- The row list
- The column list
- The mark each true cell carries
Things to check
- Do not fill cells to look complete — an honest empty cell is the finding.
- Do not mix relationship types in one mark without a legend.
Scope of this diagram
Model-derived marks; the matrix reports the model, it does not prove coverage in reality.
Work with the converted example
- Open the viewer and select
matrix_general. 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.