Characteristics of good SRS document include the following:
Concise: The SRS document should be succinct and at the same time unambiguous, consistent, and comprehensive. Verbose and irrelevant explanations diminish readability and also raise mistake chances.
Structured: It should be well-structured. A well-structured document is simple to understand and change. In reality, the SRS document undergoes multiple revisions to cope up with the client expectations. Often, the client needs evolve over a period of time. Therefore, in order to make the revisions to the SRS document easier, it is vital to create the document well-structured.
Black-box view: It should just explain what the system should perform and avoid from stating how to achieve them. This implies that the SRS document should define the external behavior of the system and not address the implementation difficulties. The SRS document should see the system to be designed as black box, and should specify the externally observable behavior of the system. For this reason, the SRS document is also called the black-box specification of a system.
Conceptual integrity: It should display conceptual integrity so that the reader may readily grasp it.
Response to unfavorable occurrences: It should define appropriate reactions to unpleasant events. These are called system reaction to extraordinary
Verifiable: All system requirements included in the SRS document must be able to be independently verified. It should be feasible to assess whether or not requirements have been satisfied in an implementation, according to this.
