Characteristic of good SRS. Correct: SRS is correct when all user requirements are stated in the requirements document. Unambiguous: SRS is unambiguous when every stated requirement has only one interpretation Complete: SRS is complete when the requirements clearly define what the software is required to do Ranked for Importance/Stability: All requirements are not equally important, hence each requirement is identified to make differences among other requirements. Modifiable: The requirements of the user can change, hence requirements document should be created in such a manner that those changes can be modified easily Traceable: SRS is traceable when the source of each requirement is clear and facilitates the reference of each requirement in future. Verifiable: SRS is verifiable when the specified requirements can be verified with a cost-effective process to check whether the final software meets those requirements. Consistent: SRS is consistent when the subsets of individual requirements defined do not conflict with each other.
