COEPD – Center of Excellence for Professional Development Happy Learning
SRS (Software Requirement Specification):
Software requirement specification document is prepared by Business analyst’s which captures the requirements of a software or a product which requires a change or upgrade for increasing the quality of the software/product and ensuring customer demand/satisfaction. Software requirement specification document should adhere to CMMI (Capability Maturity Model Integration) level standards and also meet the ISO (International Organization for Standardization) guidelines.
Below are the key elements of SRS:
- Purpose of the document:
- In this section, the exact need for this document and it’s purpose will be explained. This section derives the purpose/need based on the stakeholder requirements.
- Scope of the document:
- This section captures the main objective of the document. It also captures the cost and time required to develop the software/product.
- Overview:
- This section captures the description of the software/product along with the features expected by the customer/end user.
- Functional Requirements:
- This section captures the functional changes to be made in the system related to the software/product. Functional requirements are captured by Business analysts based on the requirements gathered from the client/stakeholders. Functional requirements will be separately documented depending on the organization/client need as mentioned below.
- FRS(Functional requirement specification)
- FSD (Functional specification document)
- FS (Functional specification)
- Non-Functional Requirements:
- This section captures the non-functional requirement details. Non- Functional requirements will be separately documented in SSD (Solution specification document) which is prepared by technical team.
Below are the possible non-functional requirements.
- Usability
- Scalability
- Performance
- Load
- Security
- Portability
- Compatibility
- Hardware requirements:
- This section captures the need of hardware’s required for making the changes for the software/product like Operating system, Database server, Application server, Cloud Server(if any).
- UI Requirements:
- This section captures the need of UI(User interface) requirements based on the requirements gathered from the stakeholder/end user)
- Design/Development constraints:
- This section captures the details of any specific constraints related to the design phase or the development phase which the team has to be well aware
- System Overview:
- Current System:
- This section captures the current features of the software/product like the details mentioned below:
- What are all the different screens and views available for the software/product in the system
- What are all the critical features which is been used by the customers on a regular basis
- Proposed System:
- This section captures the changes expected from the customer/end user in the current system like the one’s mentioned below.
- What are the changes expected to be made and the screen where the changes are to be made
- What are the changes expected to be made and the view where the changes are to be made
- What are the new enhancements expected by the end user which improves the look and feel of the system and attracts the customers and in turn ensures 100% customer satisfaction
- Benefits of the Proposed system:
- This section captures the benefits of the proposed system compared to the current system.
Use of SRS document:
- Development team require this document for developing product according to the stakeholder need
- Test plans are generated by testing group based on the described external behavior.
- Maintenance and support staff need it to understand what the software product is supposed to do.
- Project manager base their plans and estimates of schedule, effort and resources on it.
- Customers rely on it to know that product they can expect.
- As a contract between developer and customer.
