Parts of a SRS document
The important parts of SRS document are:
Functional requirements:-
ƒ The functional requirements part discusses the functionalities required from the system.
The system is considered to perform a set of high-level functions {fi}. The functional view of the system is shown in fig.
Each function fi of the system can be considered as a transformation of a set of input data (ii) to the corresponding set of output data (oi). The user can get some meaningful piece of work done using a high-level function.
Nonfunctional requirements:-
ƒ Nonfunctional requirements deal with the characteristics of the system which can not be expressed as functions - such as the maintainability of the system, portability of the system, usability of the system, etc.
ƒ Nonfunctional requirements may include:
# reliability issues,
# accuracy of results,
# human - computer interface issues,
# constraints on the system implementation, etc.
Goals of implementation:-
The goals of implementation part documents some general suggestions regarding development. These suggestions guide trade-off among design goals.
The goals of implementation section might document issues such as revisions to the system functionalities that may be required in the future, new devices to be supported in the future, reusability issues, etc. These are the items which the developers might keep in their mind during development so that the developed system may meet some aspects that are not required immediately
The important parts of SRS document are:
- ƒ Functional requirements of the system
- Non-functional requirements of the system
- Goals of implementation
Functional requirements:-
ƒ The functional requirements part discusses the functionalities required from the system.
The system is considered to perform a set of high-level functions {fi}. The functional view of the system is shown in fig.
Each function fi of the system can be considered as a transformation of a set of input data (ii) to the corresponding set of output data (oi). The user can get some meaningful piece of work done using a high-level function.
Nonfunctional requirements:-
ƒ Nonfunctional requirements deal with the characteristics of the system which can not be expressed as functions - such as the maintainability of the system, portability of the system, usability of the system, etc.
ƒ Nonfunctional requirements may include:
# reliability issues,
# accuracy of results,
# human - computer interface issues,
# constraints on the system implementation, etc.
Goals of implementation:-
The goals of implementation part documents some general suggestions regarding development. These suggestions guide trade-off among design goals.
The goals of implementation section might document issues such as revisions to the system functionalities that may be required in the future, new devices to be supported in the future, reusability issues, etc. These are the items which the developers might keep in their mind during development so that the developed system may meet some aspects that are not required immediately
SRS document |Parts of a SRS document |software engineering