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