Clause 6.5.2: Requirements activities in verification
The requirements work in verification selects the verification method or technique and the criteria for every verification action.
What clause 6.5.2 asks
The requirements work in verification selects the verification method or technique and the criteria for every verification action. The method is best associated with the requirement when the requirement is written. It defines how, who, when and where compliance will be shown. The four standard methods are test, demonstration, analysis (including simulation) and inspection. Certification can be an alternative. The method and its result are recorded in a requirements traceability matrix or a verification cross reference matrix, and traceability of the verified elements is maintained.
Why it matters
The clause turns verifiability from an adjective into a record. A requirement with no method is not yet verifiable, even if it looks measurable. The four methods have different evidence strengths, and the choice should follow the property being verified, not the convenience of the test team.
No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.
What good looks like
Add a verification method and a success criterion to every requirement at authoring time. Record who will witness the evidence and when, as an event rather than a calendar date. Keep the matrix under configuration control with the requirement set.
Evidence an assessor asks for
The assessor will pick a requirement marked verified and ask for the objective evidence. A method with no result is a plan, not verification.
- Verification matrix Each requirement, the method, the criterion, the owner, the event and the result
- Method rationale Why inspection, analysis, demonstration or test was chosen for this property
- Witness record Who will witness the evidence and what counts as a pass
- Traceability The link from the verified element back to the requirement
Where it commonly fails
- Every requirement is assigned test, including properties that cannot be tested economically
- The verification method is chosen by the test team after the design freeze
- A certificate is treated as verification without a link to the requirement
What to do before the revision
Choose the method when the requirement is written. It changes how the requirement is worded, and it exposes requirements that cannot be verified at all.
Read across
- 6.4.3.3 Define system or software requirements
- 6.4.3.5 Manage system or software requirements
- 6.5.3 Requirements activities in validation
- 6.5.2 Requirements activities in verification
← 6.5.1 Requirements activities in architecture definition 6.5.3 Requirements activities in validation →
Source for clause 6.5.2: ISO/IEC/IEEE 29148:2018, Clause 6.5.2, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.