A number of other requirements validation techniques are used either individually or in conjunction with other techniques to check the entire system or parts of the system.
Requirements validation studies the 'final draft' of the requirements document while requirements analysis studies the 'raw requirements' from the system stakeholders (users).Requirements validation and requirements analysis can be summarized as follows: Various inputs such as requirements document, organizational knowledge, and organizational standards are shown.The organizational standards are specified standards followed by the organization according to which the system is to be developed.The output of requirements validation is a list of problems and agreed actions of the problems.Completing a traceability matrix will ensure that the SRS is complete, that nothing has fallen through the gaps.
It will also ensure that all the requirements elicited can be traced back and justified to business requirements as well as functional requirements.
Prototyping is generally used to test validity and completeness of the requirements.
A prototype brings the SRS to life by providing the users with a visual model.
The lists of problems indicate the problems encountered in the" requirements document of the requirements validation process.
The agreed actions is a list that displays the actions to be performed to resolve the problems depicted in the problem list.
In the validation phase, the work products produced as a consequence of requirements engineering are examined for consistency, omissions, and ambiguity.