Clause 7: The required information items
A project claiming conformance has to produce four information items: the business requirements specification, the stakeholder requirements specification, the system requirements specification and, where 12207 applies, the software requirements specification.
What clause 7 asks
A project claiming conformance has to produce four information items: the business requirements specification, the stakeholder requirements specification, the system requirements specification and, where 12207 applies, the software requirements specification. Each item has to contain the content defined in clause 9. The standard allows several specifications of each type, for example a SyRS for the system and another for a system element. The items need not be separate paper documents: they can be unpublished, held in a repository, split into volumes or combined, as long as the required content is easy to find and logically organized.
Why it matters
The clause settles a common argument about documents. The obligation is the content, not the binding. A modelling repository can satisfy it. The four names are still required, because they map to four different views: why the business is acting, what the stakeholders need, what the system must do, and what the software must do.
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
Build an information item index with the four names, the repository location, the version and the owner. Where an item is combined with another, record the section mapping. Where a model holds the content, record how a reviewer can extract it.
Evidence an assessor asks for
The assessor will ask for one required content element and expect to find it in the named item. An index that points at a folder is not a content map.
- Information item index The four items, their location, version, owner and the clause 9 content map
- Combination map Where items are combined or split, the section that carries each required content element
- Repository access A reviewer's route to the current and previous versions
- 12207 decision Whether the SRS applies, with the framework decision behind the answer
Where it commonly fails
- A project with a single requirements document and no mapping to the four items
- The content exists in a model but cannot be extracted for review
- The SRS is omitted on a 12207 project because the team writes only a SyRS
What to do before the revision
Make the index the table of contents of the requirements pack. If a required content element has no home, the gap is visible immediately.
Read across
Source for clause 7: ISO/IEC/IEEE 29148:2018, Clause 7, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.