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 :

1. Listen to the speaker and concentrate on what is being said.
2. Prepare before you meet, by searching, researching and understanding the problem.
3. Someone should facilitate the meeting and should have an agenda.
4. Face to Face communication is best but also have a document or presentation to focus on discussion.
5. Strive for collaborations and decisions.
6. Document all the decisions.

Planning Practices or Principles :

1. Understand the scope of the project.
2. Involve the customer in the planning activity.
3. Recognize that planning is iterative and things will change.
4. Estimation should be done based on only what you know.
5. Consider the risk and it should be defined in the plan.
6. Be realistic on how much can be done on each day.
7. Define how you ensure quality can be achieved.

Construction Deployment Practices or Principles :

1. Understand the problem you are trying to solve.
2. Understand basic design principles and concepts.
3. Pick a programming language that meets the need of the software to be built.
4. Create a set of unit test cases that will be applied once the component you code is completed.
5. Constraint your algorithm by structured programming practices.
6. Understand the software architecture and create interfaces that are compatible with it.
7. Keep conditional logic as simple as possible.
8. Write a code that is self documenting.