3. What is an SRS?
SRS is the official document of what the system developers should
implement.
SRS is the complete description of the behavior of the system to be
developed.
SRS give the detailed description of both functional and non-functional
requirements.
The SRS fully describe what the system will do and how it will be expected
to perform.
4. Purpose of SRS:
The SRS will precisely define the software product that will be built.
SRS used to know all the requirements for the software development and
thus that will help in designing the software.
5. Users of the document:
System customers
Managers
System Engineers
System Test Engineers
System Maintenance Engineers
6. Structure:
Large Organizations such as
US Department of defense and IEEE
Define the standards.
IEEE/ANSI 830-1998 (IEEE, 1998).
IEEE suggest the following structure.
System Customer: Owner of the product and specify the requirements.
Managers: Use the SRS to plan the system development process
System Engineers: Use the req. to understand what system is to developed.
System Test Engineers: Use the req. to develop validation test for the product.
System Maintenance Use the req. to understand the system and the relationship b\w its parts.
Engineers: