Clause 8.1: Requirements information item outlines
The standard recommends an outline for each information item, but it does not impose one structure on every project.
What clause 8.1 asks
The standard recommends an outline for each information item, but it does not impose one structure on every project. The specific requirements clause should be organized so that the stakeholders agree the organization aids understanding. A project can organize by system mode, user class, object, feature, stimulus, response or functional hierarchy. The outline is a starting point, and tailoring it is allowed where the content is still complete and the readers can follow it.
Why it matters
The clause is about readability and agreement, not a fixed table of contents. A structure that the stakeholders did not agree is a review defect even when every section exists. The mode, user class and feature options are useful when the system behaves differently for different users or states.
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
Choose the structure before writing the requirements, and record why it fits this system. Keep the required content from clause 9 in every structure. Test the outline with a reader who was not on the authoring team.
Evidence an assessor asks for
The assessor will ask why the specification is organized this way. A structure copied from a template with no reason is not a decision.
- Outline decision The chosen structure, the reason and the stakeholders who agreed it
- Content map Where each clause 9 content element sits in the chosen outline
- Reader test A note from a reader outside the authoring team that the structure was followable
- Tailoring record Any section removed or merged, with the reason and the approval
Where it commonly fails
- The outline is copied from a template and the project cannot say why
- A mode-based system is organized by function, so the degraded and emergency requirements are scattered
- Sections exist but the readers cannot find the requirement they need
What to do before the revision
Write the outline on one page and test it with a reader before the first draft. Changing it later costs more than choosing it well.
Read across
- 8.2 BRS example outline
- 8.3 StRS example outline
- 8.4 SyRS example outline
- 8.5 SRS example outline
- 9.2 General content
← 6.6.3.3 Perform requirements measurement 8.2 BRS example outline →
Source for clause 8.1: ISO/IEC/IEEE 29148:2018, Clause 8.1, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.