Clause 6.3.3.6: Analyze stakeholder requirements
The complete stakeholder set is analyzed against the individual and set characteristics.
What clause 6.3.3.6 asks
The complete stakeholder set is analyzed against the individual and set characteristics. It is prioritized and classified, and reused requirements are checked for fit, feasibility, availability, quality, cost, value and whether they are current. Critical performance measures are defined so technical achievement can be assessed. The analyzed set is fed back to the stakeholders to confirm it captures their needs, and the issues are resolved through negotiation.
Why it matters
The clause puts validation before the system requirements are written. The feedback step is the stakeholder's chance to say the set is not what they meant. The critical performance measures are the link to verification: without them, the later test has nothing to measure against.
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
Run the characteristic review and the stakeholder review as two separate events. Record the measures, the issues and the negotiation outcome. Do not close an issue by deleting the requirement unless the stakeholder agrees.
Evidence an assessor asks for
The assessor will ask for a measure that shows a stakeholder requirement was achieved. If the measure is defined only at test, the analysis stopped early.
- Analysis record The set review against the individual and set characteristics, with the issues found
- Critical performance measures The measures and the requirement each one assesses
- Stakeholder feedback The review record and the changes made as a result
- Issue log Each conflict or deficiency, the negotiation and the resolution
Where it commonly fails
- The set is reviewed for spelling and format, not for the characteristics
- Critical performance measures are left to the test team
- Conflicts are closed by removing the requirement, with no stakeholder agreement
What to do before the revision
Hold the stakeholder feedback session before the system requirements baseline. After that point, a change is a change to the baseline, not a review comment.
Read across
- 5.2.5 Characteristics of individual requirements
- 5.2.6 Characteristics of a set of requirements
- 6.3.3.5 Transform needs into stakeholder requirements
- 6.3.3.7 Manage stakeholder needs and requirements
← 6.3.3.5 Transform needs into stakeholder requirements 6.3.3.7 Manage stakeholder needs and requirements →
Source for clause 6.3.3.6: ISO/IEC/IEEE 29148:2018, Clause 6.3.3.6, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.