Practices to follow while writing the SRS for a project
A software requirements specification (SRS) is a description of a software system to be developed. In order to write a good SRS, some common practices have to be followed which are as follows :
Communication Practices or Principles :
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Listen to the speaker and concentrate on what is being said.
- Prepare before you meet, by searching, researching and understanding the problem.
- Someone should facilitate the meeting and should have an agenda.
- Face to Face communication is best but also have a document or presentation to focus on discussion.
- Strive for collaborations and decisions.
- Document all the decisions.
Planning Practices or Principles :
- Understand the scope of the project.
- Involve the customer in the planning activity.
- Recognize that planning is iterative and things will change.
- Estimation should be done based on only what you know.
- Consider the risk and it should be defined in the plan.
- Be realistic on how much can be done on each day.
- Define how you ensure quality can be achieved.
Construction Deployment Practices or Principles :
- Understand the problem you are trying to solve.
- Understand basic design principles and concepts.
- Pick a programming language that meets the need of the software to be built.
- Create a set of unit test cases that will be applied once the component you code is completed.
- Constraint your algorithm by structured programming practices.
- Understand the software architecture and create interfaces that are compatible with it.
- Keep conditional logic as simple as possible.
- Write a code that is self documenting.