Clause 8.3: StRS example outline
The StRS outline follows the stakeholder view.
What clause 8.3 asks
The StRS outline follows the stakeholder view. It covers identification and front matter, the stakeholder purpose and scope, the overview and stakeholders, the business environment, mission and goals, the business model and information environment, the 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 detailed content is in clause 9.4.
Why it matters
The StRS sits between the business view and the technical view. Its outline keeps the user requirements after the operating context, so a reader understands the conditions before the needs. The stakeholder ownership is the point: the content is specified by the stakeholders, not only reviewed by them.
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
Use the outline to run the stakeholder review. Put the user requirements in the centre and keep the operating context around them. Record conflicts rather than averaging them away.
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.
- StRS skeleton The outline with each section present, not applicable, or merged
- Stakeholder ownership The representatives who approved each part of the content
- User requirements Each user requirement with the stakeholder and need it serves
- Conflict record The open conflicts and the agreed position
Where it commonly fails
- The StRS is written by the supplier with no stakeholder review
- The operating context is missing, so the user requirements have no conditions
- Conflicts are removed from the record to make the set look agreed
What to do before the revision
Run the outline as an agenda with the stakeholders. A section no one can speak to is a section that will be challenged later.
Read across
- 8.1 Requirements information item outlines
- 9.4 StRS content
- 6.3.3.7 Manage stakeholder needs and requirements
- 8.4 SyRS example outline
Source for clause 8.3: ISO/IEC/IEEE 29148:2018, Clause 8.3, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.