Product · Verification & validation
Plans, revisions, runs, and coverage, tied to real requirement versions
The V&V module separates Verification (typically against system requirements) from Validation (against stakeholder requirements). Only released plan revisions can be executed; each test item links to one or more requirements with a snapshot of text, version, and relevant fields.
Plan and revision
Create a VVPlan with type Verification or Validation.
Work in the draft revision, update scope summary and revision comment.
Create a new revision from a released one, copies all items and requirement links (including snapshots). Only one draft revision per plan at a time.
Release revision (release), gatekeeper: every item must have title, method, expected result, and at least one requirement link.
V&V items, runs, and approvals
V&V items (manual and AI)
Manual: create items with type, title, method, expected result, description, procedure steps, preconditions, run order, mandatory flag, responsible role. AI: POST .../generate-items (batch) or .../generate-item (combined). AI search: natural language → matching requirement IDs.
Requirement links and impact
VVItemRequirement stores requirementType (stakeholder/system), FK, and snapshots (displayId, version, text, criteria, method fields). The impact service warns when snapshot version < live version; in draft you can update-links to refresh snapshots.
Runs
Create a VVRun against a released revision, status Draft, per-item results initially NotExecuted. Start (start) or let it flip to InProgress on the first non-NotExecuted verdict. Record verdict per item: Passed, Failed, PartiallyPassed, Blocked, NotApplicable. Participants with roles. Complete (complete) computes overallVerdict and sets isFinal; triggers rollup to requirement fields. Abort (abort) with optional reason also triggers rollup.
Approvals
After a run completes, users with VV_RUN_APPROVE can register approvals: TechnicalReview, QualityReview, FormalApproval, CustomerAcceptance, decisions Approved, ApprovedWithRemarks, Rejected. Aggregate approvalStatus controls whether the run is locked for editing.
Coverage and export
The Coverage API summarizes all stakeholder/system requirements and their V&V status (NotPlanned, Planned, InProgress, Verified/Validated, Failed, NotApplicable, NeedsReverification/Revalidation). Excel export of coverage with the same filters as in the UI. Word/PDF for plan revision and run report (plan export supports ?lang=sv|en for display prefix).