The content and qualities of a good software requirements specification (SRS) are described, and several sample SRS outlines are presented. This recommended practice is aimed at specifying the requirements of software to be developed, but can also be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/EIA Std 12207.1-1997 are also provided.
Standard Identifier: IEEE Std 830-1998
- NIST Special Publication 800-171, Revision 1, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations Reference Document
- Introduction to Tools & Testing Techniques for Assured Software – DoD Software Assurance Community of Practice: Volume 2 Journal Article
- Introduction to Design and Development Process for Assured Software – DoD Software Assurance Community of Practice: Volume 1 Journal Article
- Overview of the Software Assurance Marketplace (SWAMP) and SWAMP-in-a-Box (SiB) CSIAC Webinar
- Development and Transition of the SEI Software Assurance Curriculum Journal Article