Validating Requirements in Software Engineering

Requirements validation is an iterative process which takes place throughout the lifecycle of the project. During elicitation, analysis and specification you should constantly be questioning and clarifying the data given to you in order to check its validity. This will ensure that the SRS that you produce is complete, consistent and ready for the formal validation process. Validation ensures that the requirements will met the customers needs. Validation requirement is the process of evaluating a system or component during or at the end of the development process to determine weather it satisfies specified requirements.

The validation process involves two important steps, the first step ensures that each specification is traceable to a requirement in the requirements definition document and the next step ensures that each requirement is traceable to the specification. In the validation phase, the work products produced as a consequence of requirements engineering are examined for consistency, omissions, and ambiguity. The basic objective is to ensure that the SRS (Software Requirements Specification) reflects the actual requirements accurately and clearly. Other objectives of the requirements document are listed below :

1. To certify that the SRS contains an acceptable description of the system to be implemented

2. To ensure that the actual requirements of the system are reflected in the SRS

3. To check the requirements document for completeness, accuracy, consistency, requirement conflict', conformance to standards and technical errors.

Requirements Validation Checks :

Various checks performed for requirements during the validation process are :

Validity check : This check aims to ensure that the system meets all functional, behavioral and performance requirements.

Consistency check : The requirements should be unambiguous and free from any contradiction. The two requirements are inconsistent, if it is impossible to satisfy both of them simultaneously.

Completeness check : The requirements are complete, if all states, state changes, input, products and constraints have been described by some requirements. The set of requirements is extremely complete, if description contains all the properties of environment desired by the users. It is internally complete, if there are no undefined references among the requirements.

Realism check : The requirements must be realistic. It should be possible to implement them within technological and financial constraint.

Verifiability : At the completion of the system, it must be possible to demonstrate that the delivered system meets all the requirements.

Next Topic :

No comments:

Post a Comment