SRS Standards (IEEE)

An SRS (Software Requirements Specification) is the document that states what the software must do and acts as an agreement between client and developer. Standards give a common structure so every SRS is complete and consistent.

Main standards

• IEEE 830-1998: Recommended Practice for Software Requirements Specifications (the classic SRS format used in syllabi).
• ISO/IEC/IEEE 29148:2018: the current standard that replaced IEEE 830 and covers requirements engineering processes and documents.

IEEE 830 structure

1. Introduction
   • 1.1 Purpose, 1.2 Scope, 1.3 Definitions, acronyms, abbreviations, 1.4 References, 1.5 Overview
2. Overall description
   • 2.1 Product perspective, 2.2 Product functions, 2.3 User characteristics, 2.4 Constraints, 2.5 Assumptions and dependencies
3. Specific requirements
   • External interfaces (user, hardware, software, communication)
   • Functional requirements
   • Performance requirements
   • Design constraints
   • Software system attributes (reliability, availability, security, maintainability, portability)
   • Other requirements
4. Appendices and index

Characteristics of a good SRS (IEEE 830)

Correct, unambiguous, complete, consistent, ranked for importance/stability, verifiable, modifiable, traceable.

Benefits of following a standard

• Common understanding between client, analysts and developers
• Fewer missing or conflicting requirements
• Easier review, testing and maintenance
• Basis for estimating cost and schedule