Requirements, governance and enterprise review
Data-product ownership and contracts
Who owns which data product, under which contract, with which consumers.
ddn@1New DDN source
Why use it?
Every dataset that matters needs a name attached to it — the diagram is the accountability list.
When it helps
Establishing or auditing data-product governance.
How to read it
- Owners are people or teams, never systems.
- A contract without a named consumer is a wish, not a contract.
What you need
- The products
- Owners per product
- Contracts and their consumers
Things to check
- Do not list a team as owner when a person is accountable.
- Do not let a product have zero consumers named — it is probably not a product.
Scope of this diagram
Governance documentation; the contracts are stated, not enforced.
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.