A Software Requirement Specifications (SRS) document is a detailed and structured requirements document that contains the functional requirements (illustrates behaviour), non-functional requirements (depicts characteristics) along with any use cases that the software must fulfil.

SRS states ‘What’ requirements must be fulfilled to satisfy the business’s needs and in accordance to it elaborates BRD’s high-level statements into a module, sub-module, and features. Every Listed requirement in SRS should fulfil the business objectives listed in the BRD.

SRS describe the features of a system or software application and it is derived from BRD

SRS is created by BA or System Analyst/Architect.

SRS commonly used for estimating the cost and effort required for developing that software.

SRS is used by the project managers, SMEs (subject matter experts), technical and implementation lead responsible for overseeing the development of the listed functionalities.

The key elements of an SRS are:

• Scope of Work
• Functional Requirements
• Non-Functional Requirements
• Dependencies
• Data Model
• Assumptions
• Constraints
• Acceptance Criteria

Non-functional requirements represent the performance level characteristics like how fast it can respond, how smooth is a user interface, security, etc. of the application under development (AUD).

No functional requirements are captured in the SRS document in its designated section.