Edition 3 at DIS ballot, stage 40.20/ Planning date 12 September 2027, an estimate/ ISO/IEC/IEEE 29148:2018 applies today
ISO 29148 Revision CheckerThe requirements record, clause by clause, and the edition that follows it
9.6
ISO/IEC/IEEE 29148:2018
Information items

Clause 9.6: SRS content

Current editionISO/IEC/IEEE 29148:2018, Clause 9.6Edition 3 at DIS ballotNo public change recorded

The SRS records the requirements for a software product, a program or a group of programs in a specific environment.

What clause 9.6 asks

The SRS records the requirements for a software product, a program or a group of programs in a specific environment. Its content covers the purpose and scope, product perspective and interfaces (system, user, hardware and software), product functions, user characteristics, limitations, assumptions and dependencies, apportioning of requirements, the specified requirements, external interfaces, functions, usability, performance, logical database requirements, design constraints and standards compliance, software system attributes, verification and supporting information. It indicates the precedence and criticality of the requirements.

Why it matters

The SRS is the software counterpart of the SyRS and should agree with it. The clause expects the SRS to expand the system requirements that apply to the software, not to invent a separate product. The database, design constraint and standards sections are the ones most often missing from a template driven SRS.

In the public record

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

Trace the SRS to the SyRS before writing. Use the content list as the outline. Record precedence and criticality for each requirement, and keep the verification section consistent with the system verification plan.

Evidence an assessor asks for

The assessor will compare the SRS with the SyRS. A software requirement with no parent in the system set is either derived or unsupported.

  • SRS The baselined specification, organized to the clause 9.6 content list
  • Interface set System, user, hardware and software interfaces, with the source of each
  • Specified requirements Functions, usability, performance, database, constraints, standards and attributes
  • Verification and supporting information The verification approach and the supporting material a reader needs

Where it commonly fails

  • The SRS is a generic template with the project name changed
  • Performance requirements have no measure or condition
  • The database and design constraint sections are omitted because the design is not fixed

What to do before the revision

Write the interface and specified requirement sections first. They carry the testable content and expose the gaps in the system set early.

Read across

← 9.5 SyRS content A.2.1 OpsCon: general, title and preface →

Full register / Revision record

Source for clause 9.6: ISO/IEC/IEEE 29148:2018, Clause 9.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.