Where SRS is Used?
Project Management is a skill of monitoring & influencing the development of the project by setting the Goals, standards or the acceptance criteria to achieve those goals on the basis of assumptions, availability of resources. While developing the software we do follow the SDLC where in first stage we decide the goal, and gather the requirements from the business stakeholders. SRS i.e. the System Requirement Specifications is an important part of this phase as the whole success of the project is dependent on this.
What does SRS Means & what are its elements?
SRS is nothing but the Software Requirement Specification which defines how the To-Be developed software will look like or perform after the deployment. To define this SRS document specifies the following things which we also call as the key elements of the SRS Doc.
- System Requirements
- Functional Requirements
- Non-Functional Requirements
- Acceptance criteria
- Priorities and importance of the Stated Functionalities.
- Assumptions Etc.
System Requirements: These are the requirements which define what should be the configuration of the software so that it can be performed on the prespecified platforms this could be related to the software as well as hardware specifications
Functional Requirements: These are the requirements where the business stakeholder specifies which functionalities, he do require in the software which is going to be developed.
Non functional Requirements: These are the requirements where the stakeholder defines what would be the performance requirements, what are the quality control/ security requirements etc.
Acceptance criteria: Acceptance criteria is the one where the team decided the minimum viable requirements of each function so that we can define whether the developed functionality is acceptable as per standards or not.
Priorities & Importance: Here while defining the functionalities we as a team with the business stakeholder also define which functionalities are the most important functionalities without which the software development would be no longer success. In the process we do develop the most important functionalities first.
Assumptions: These assumptions include the constraints that we may face during the development of the software. It also includes the dependencies i.e. without which we cannot go further in the development of the software.
The Advantage of the maintaining the SRS
- Track the project goal: Maintaining the SRS Document will help us the track and validate if the project development is going in right direction or not.
- Decision Making: This helps in taking decisions in later stages that whether the developed software is at par with the requirements and if not, what improvements are required.
- Improved Chances of Project Success
- Improved development process Efficiency and less time consumption
- Efficient, precise, clarity of gathered requirements reduces errors & rework.
Disadvantages Of the SRS
- It’s a time-consuming process
- Stakeholders may create conflict in deciding the priorities/ requirements
- Erroneous requirement gathering may lead project to the failure & more time consumption.