Following are the Characteristics of Good SRS Document:
1) Complete
i. SRS should be absolute.
ii. SRS defines accurately the entire live situation that will be encountered and the system’s competence to successfully address them.
2) Consistent
i. SRS should be dependable.
ii. SRS capability functions and performance levels are friendly, and the required quality features.
3) Accurate
i. SRS accurately defines the system’s capability in a real-world environment, as well as how it interfaces.
ii. This aspect of requirement is a significant problem area for man y SRS.
4) Modifiable
The logical, hierarchical construction of the SRS should make possible any necessary modifications and that too with a greater ease.
5) Testable
SRS must be confirmed in such a manner that explicit evaluation criteria can be derived from the SRS itself.
6) Ranked
Individual requirement of an SRS are hierarchically arranged according to stability, security, perceived ease/difficult of implementation, or other parameter that helps in the design of that and subsequent document.
7) Traceable
Each requirement in SRS must be uniquely identified to a source.
8) Unambiguous
9) Valid
10) Verifiable
1) Complete
i. SRS should be absolute.
ii. SRS defines accurately the entire live situation that will be encountered and the system’s competence to successfully address them.
2) Consistent
i. SRS should be dependable.
ii. SRS capability functions and performance levels are friendly, and the required quality features.
3) Accurate
i. SRS accurately defines the system’s capability in a real-world environment, as well as how it interfaces.
ii. This aspect of requirement is a significant problem area for man y SRS.
4) Modifiable
The logical, hierarchical construction of the SRS should make possible any necessary modifications and that too with a greater ease.
5) Testable
SRS must be confirmed in such a manner that explicit evaluation criteria can be derived from the SRS itself.
6) Ranked
Individual requirement of an SRS are hierarchically arranged according to stability, security, perceived ease/difficult of implementation, or other parameter that helps in the design of that and subsequent document.
7) Traceable
Each requirement in SRS must be uniquely identified to a source.
8) Unambiguous
9) Valid
10) Verifiable