In this tutorial, you will learn about, System Requirements Specification (SRS) And Structure of a Typical SRS document.
System Requirements Specification (SRS):
SRS is a set of complete and stated properties along with the of the system that the software must satisfy. A well-designed software requirement specification establishes a boundary and solution of a system to develop.
The SRS should specify only the external behavior of the system and not to the internal details.
We can also think of SRS as an agreement between the client and the developer that what is to be developed and what problems are to be solved.
Characteristics of SRS:
- Unambiguously: All the requirements must be stated unambiguously that is every requirement stated should have only one interpretation.
- Complete: The definition should include all the function and constraints intended by the system user.
- Realistic: The requirements should be realistic and achievable with current technology.
- Verifiable and consistent: The requirements should be verifiable and they are to be verified by the system tester during testing. It makes sure that no requirements conflict with any other requirements.
- Modifiable: The structure and style of the SRS should be such that any necessary change to the requirements can be made easily, completely and consistently.
- Traceable: It should be traceable to the other requirements and related documents. The origin of each requirement must be clear.
- Useable: It must be usable during the operation and maintenance of the system.
Structure of a typical SRS Documents:
- An informative description of the system.
- A functional description of the system.
- Test and validation criteria.
a) System reference and business objective of the documents are implemented
b) Goals and objectives of the system describing in the context of a computer-based system are documented.
c) The scope of the document.
An informative description of the system:
a) Structure representation.
b) Description of sub-systems and system interface.
c) A detailed description of the problem of the problem that the software must be solved.
d) Details of information flow, content and its structure are documented.
A functional description of the system:
a) The functional description of every module is defined.
b) Restriction and limits to every module are defined.
c) A diagram to represent the overall structure and all the basic structure of the software graphically.
Test and validation criteria: here we document the expected software response under various conditions.
Glossary (Dictionary): Definition of all technical or software specific terms used in the documents.
Bibliography: List and reference of all documents that relate to the system (software).
Appendix: supplementary information of the system is documented.
Comment below if you have queries related to the above topic, System Requirements Specification (SRS) And Structure of a Typical SRS document.