Before staring any project, or to understand the problems of the clients, solutions and scope for the project. The Business Analyst do the Requirement gathering.
SRS which stands for Software Requirement Specification, it’s a document prepared by Business Analyst with the help of Technical Team. It describes what will be the software features.
SRS the Software Requirement Specifications as name suggests is a complete descriptions of the requirement of the software that need to be fulfilled for successful development of software application or product. These requirements can be functional and non-functional. It is depending upon the type of requirements needed for the software development.
After successfully gathered the requirements, SRS is prepared and which describes the features of the software that includes changes or modifications that is needed to be done to improve the quality of the software and satisfy the clients.
SRS document is required for the development of the product as per the requirements.
Key elements of SRS are
- Introduction:
- Purpose of the Document:- While preparing SRS document, it is necessary to understand why this document is necessary and also the main purpose of the SRS document is described.
- Scope of the Document:- While preparing SRS document, it explains the main objective of the document that what kind of value will provide to its customer.
- Overview: Here, it’s a description of features or summary of the software features.
- General Description: In general description, its functions which includes the objectives of the user, features of the software, benefits of the software, also the importance of the software.
- Functional Requirements: Functional Requirements of the software is basically the behavioural aspects of the software which explains the behaviours and communication between the users and the system. Functional requirements can be represented using tools like UML Diagram, Mockups, wireframes and so on.
- Non-Functional Requirements: Non functional requirements of the software is basically for the operational part of the system which help the system to work smoothly and for better performance. Examples are, security, reusability, reliability, portability, maintainability and so on.
- Interface Requirements: In this interface requirements, software interface which mean that how the software programs communicates with each other, code or message are described.
- Performance Requirements: In this performance requirements, it is being described and explained how the products performs under desired circumstances or conditions. It also explains the required time to download page and so on.
- Design Constraints: In design constraints, basically explains about the limitations or restriction are explained for the designing software team. Examples Algorithm, hardware, software limitations and so on.