IEEE Generic Structure for a Software Requirements Specification (SRS) Document

1. Introduction
2. Overall Description
3. Specific Requirements
4. Appendices
5. Index

1. Introduction

1.1 Purpose of the Requirements Document

1.2 Scope of the Product
1.3 Definitions, acronyms and Abbreviations
1.4 References
1.5 Overview of the remainder of the document

2. Overall Description
2.1 Product Perspective
2.2 Product Functions (summary)
2.3 User Characteristics
2.3 General Constraints
2.4 Assumptions and Dependencies

3. Specific Requirements
3.1 External Interface Requirements
3.2 Functional Requirements
3.3 Non-functional requirements
3.4 Design constraints
4. Appendices
5. Index
 (Detail Description of SRS)

IEEE Generic Structure for a Software Requirements Specification (SRS) Document

1. Introduction
2. Overall Description
3. Specific Requirements
4. Appendices
5. Index
3. Introduction

1.1 Purpose of the Requirements Document

1.2 Scope of the Product
(Identifies the product, & application domain)
1.3 Definitions, acronyms and abbreviation
1.4 References
1.5 Overview of the remainder of the document
(Describes contents and structure of the remainder of the SRS)

4. Overall Description
2.1 Product Perspective
(Describes all external interfaces: system, user, hardware, software; also and site
adaptation, and hardware constraints)
2.2 Product Functions (summary)
(Summary of major functions, e.g. use cases)
2.3 User Characteristics
(Anything that will limit the developer’s options (e.g. regulations, reliability, criticality,
hardware limitations, parallelism, etc))
2.3 General Constraints
2.4 Assumptions and Dependencies

3. Specific Requirements
(All the requirements go in here (i.e. this is the body of the document). IEEE STD provides 8
different templates for this section)
3.1 External Interface Requirements
(All inputs and outputs to system)
3.1.1 User Interfaces
(a user friendly interface)
3.1.2 Hardware Interfaces
(the proposed system will work on any computer)
3.1.3 Software Interfaces
(platform)
3.1.4 Communication Interfaces
3.2 Functional Requirements
(Describe all functions of the system)
3.3 Non-functional requirements
3.4 Design constraints
 3.4.1. Standards Compliance
3.4.2. Hardware Limitations …
3.5. Attributes
3.5.1. Security
3.5.2. Maintainability
3.5.3 Reliability
3.5.4 Availability
3.5.5 Portability
3.6. Other Requirements
3.6.1. Data Base …

NOTE:

Specific Requirements should

 contain all software requirements to a level of detail sufficient to enable designers to satisfy
those requirements, and testers to test that the system satisfies those requirements.
 include a description of every input and every output (response) from the system and all
functions performed by the system in response to inputs and in support of outputs.

4. Appendices
Appendices may include items such as hardware and database descriptions

5. Index
Index the software functions, tables, diagrams, etc.