Clause 9.4: StRS content
The StRS records the stakeholder requirements for the system in its defined environment.
What clause 9.4 asks
The StRS records the stakeholder requirements for the system in its defined environment. Its content covers the stakeholder purpose, scope, overview and stakeholders, the business environment, mission and goals, business model and information environment. It then covers system processes, operational policies and rules, operational constraints, modes and states, operational quality, structure, user requirements, the operational concept, scenarios, detailed concepts and project constraints. The stakeholders should lead the content, and the specification is the basis for their active participation in the requirements process.
Why it matters
The StRS is where the user's view becomes a requirement set. The user requirements section is the heart of it, but the operating context around it is what makes the requirements testable. The standard allows the StRS and BRS to be combined, provided the perspectives are still distinguishable.
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
Write the stakeholder and purpose sections first, then the operating context, then the user requirements. Keep each user requirement linked to a stakeholder and a need. Record conflicts openly rather than resolving them by omission.
Evidence an assessor asks for
The assessor will choose a user requirement and ask which stakeholder agreed it. A set with no stakeholder link is a system specification in disguise.
- Purpose and stakeholders The system purpose, scope, stakeholder classes and their interests
- Operating context The business environment, processes, policies, constraints, modes and quality expectations
- User requirements Each user requirement, its stakeholder and the need it serves
- Operational concept and scenarios The concept, scenarios and detailed concepts that bound the requirements
Where it commonly fails
- User requirements are written by the supplier with no stakeholder review
- Conflicting stakeholder needs are averaged into one vague requirement
- The operational concept is missing, so the context of use is undefined
What to do before the revision
Keep the conflict record with the StRS. It is the evidence that the hard stakeholder work happened, and it protects the project when a need changes later.
Read across
Source for clause 9.4: ISO/IEC/IEEE 29148:2018, Clause 9.4, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.