03 · Product
Verification
Every requirement knows how it gets proven.
Verification in synapse™ is a set of actions, tests, analyses, inspections and reviews, linked to the requirements they prove and carrying their own evidence. Their status flows up to the requirements, their dates place them against the project milestones, and the V&V team works on them in parallel with the people writing the requirements.
The campaign timeline, generated from the actions' planned dates and the milestones' due dates. An action with no dates does not appear, which is the fastest way to find work nobody has scheduled.
- V&V works in parallelVerification actions are their own objects, not a column on the requirement. The verification team plans and runs them across the project while the requirements are still being written.
- Linked to what they proveOne action can verify many requirements and one requirement can need many actions. The link is the compliance matrix, kept by the tool rather than in a spreadsheet.
- Evidence on the actionTest reports, analysis results and external links attach to the action that used them. Evidence never sets the status; an engineer judges it and does.
- Status flows upSet an action to Verified and every requirement it proves reflects it. A failed test reads as work still open, never as done.
- Methods enforced by the processEach requirement kind defines which verification methods it accepts. An action that does not fit the rule is rejected, not quietly recorded.
- A plan that draws itselfMilestones, the Gantt chart and the test plan per review come from the dates already on the actions. There is nothing to draw and nothing to re-link.
The whole campaign in one list
Every test, analysis, inspection and review, with its owner, its facility, its planned window and the requirements it proves. Verified, in progress and blocked are counted across the top, and the list filters, clusters and saves as views, so the state of the campaign is a glance rather than an afternoon of chasing people for status.
