An SRS (software requirements specification) describes the functionality and performance of a software system being developed, including user requirements and system specifications. It precisely defines the product and is used to understand all development requirements. The SRS decomposes problems, provides feedback to customers, and serves as input for design and validation. It aims to establish agreement between customers and suppliers, reduce effort, and provide a cost and schedule baseline. The SRS should be complete, consistent, changeable and traceable.

1. What is SRS?
 A software requirements specification (SRS) is a description of a software
system to be developed, laying out functional and non-functional requirements,
and may include a set of use cases that describe interactions the users will have
with the software.
 How the software will do and how it will be expected to perform.
 Describes the behavior of the system to be developed.
 Should include definition of user requirements and specification of the system
requirements.

2. The SRS precisely defines the software product that will be built.
Used to know all requirements for the software development.
Thus helps in designing of a software.

3.  It provides feedback to the customer.
 It decomposes the problem into component parts.
 It serves as an input to the design specification.
 It serves as a product validation check.

4. a) Establish the basis for agreement between the customers and the
suppliers on what the software product is to do.
b) Reduce the development effort.
c) Provide a basis for estimating costs and schedules.
d) Provide a baseline for validation and verification.

5.  Complete.
 Consistent.
 Changeable.
 Traceable.