Requirements, governance and enterprise review
Independent verification checklist
The software-change review gates with their checklists — independent review drawn as a first-class part of delivery.
ddn@1New DDN source
Why use it?
A checklist that lives in the model gets versioned with it; the one in a wiki page drifts.
When it helps
Change control: releases, schema migrations, anything requiring sign-off.
How to read it
- Gates sequence the change; checklist items attach to the gate that enforces them.
- Independence is declared — who reviews is part of the model, not a meeting invite.
What you need
- The gates
- The checklist items per gate
- The independent reviewers
Things to check
- Do not let the author and reviewer be the same declared role.
- A gate that always passes on the nod is theatre — say what evidence it reads.
Scope of this diagram
Declared gates and checklists; enforcement is an organisational act, not a render guarantee.
Work with the converted example
- Open the viewer and select
software. 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.