The SRS is a speciÞcation for a particular software product, program, or set of programs that performs
certain functions in a speciÞc environment. The SRS may be written by one or more representatives of the
supplier, one or more representatives of the customer, or by both. Subclause 4.4 recommends both.
The basic issues that the SRS writer(s) shall address are the following:
a)
Functionality.
What is the software supposed to do?
b)
External interfaces.
How does the software interact with people, the systemÕs hardware, other hardware,
and other software?
c)
Performance.
What is the speed, availability, response time, recovery time of various software functions,
etc.?
d)
Attributes.
What are the portability, correctness, maintainability, security, etc. considerations?
e)
Design constraints imposed on an implementation.
Are there any required standards in effect, implementation
language, policies for database integrity, resource limits, operating environment(s) etc.?
The SRS writer(s) should avoid placing either design or project requirements in the SRS.
For recommended contents of an SRS see Clause 5.