Professional Documents
Culture Documents
behavior of the system to be developed. It includes a set of use cases that describe all the
interactions the users will have with the software. Use cases are also known as functional
requirements. In addition to use cases, the SRS also contains non-functional (or
supplementary) requirements. Non-functional requirements are requirements which
impose constraints on the design or implementation (such as performance engineering
requirements, quality standards, or design constraints).
Importance
There must exist some finite cost-effective process with which a person
or machine can check that the software meets the requirement.
Consistent
•
The structure and style of the SRS are such that any necessary changes
to the requirements can be made easily, completely and consistently.
•
Requirements:
1. a coherent and easy-to-use organization (including a table of
contents, index and cross-referencing),
2. not be redundant - this can lead to errors.
Traceable
•
Types:
1. Backward traceability
The SRS must address the needs of the operation and maintenance
phase, including the eventual replacement of the software.
Rules of Order for Specifying SW Requirements
•
a standard format,
o
functional relationships,
o
data flow,
o
performance
to express complete requirements.
•
Rule 5: Limit the verbs and objects in the sentences to a small set with a
single specified definition for each word.
o
Rule 6: Limit the verbs and the objects to terms that are common to the
end user of the product
o
Rule 7: Limit the verbs and objects to actions and items that are visible
external to the product.
o