Description: Discusses the background information for writing a good software requirements specification (SRS). The characteristics of a good SRS are that it is unambiguous (hence use of formal requirements specifications languages because of pitfalls in natural language), complete, verifiable, consistent, modifiable, traceable, and useable during the operation and maintenance phase. The preparation evolution and tools for developing an SRS are described. The methods used to express software requirements i.e. input/output specifications and mathematical, functional timing, and other models are discussed, also annotation of requirement and common pitfalls in their expression. Finally there is an SRS prototype outline which includes general description and specification requirements.
Oversight Committee: C/S2ESC - Software & Systems Engineering Standards Committee
Get This Standard
Buy Purchase a copy of this standard Buy
Access with Subscription Standards Online subscribers can access this standard in IEEE Xplore Digital Library. Access Learn More