Methods of validating requirements
System Validation is a set of actions used to check the compliance of any element (a system element, a system, a document, a service, a task, a system requirement, etc.) with its purpose and functions.
An example is presented to illustrate the SCR tabular notation, and an overview of each of the ten tools in the SCR toolset is presented.A validation action is defined and then performed (see Figure 1, below).Note: If there is uncertainty about compliance, the cause could come from ambiguity in the requirements.It may be performed on an iterative basis on every produced engineering element during development and may begin with the validation of the expressed stakeholder requirements.When the validation process is applied to the system when completely integrated, it is often called final validation.This matrix lays the foundation for checking bidirectional traceability between the requirements, test cases, source code and design.
Testing – All requirements must be testable /verifiable so putting together the test scripts for the project as early as possible will highlight missing information or information that is ambiguous.
To validate a system requirement is to make sure its content translates correctly and/or accurately a stakeholder requirement in the language of the supplier.
The Verification versus Validation section of the System Verification article gives fundamental differences between the two concepts and associated processes.
If you are using use cases this is not an onerous task.
This is an ideal method for testing functional requirements but can be tricky to adopt for non-functional requirements.
Any engineering element can be validated using a specific reference for comparison, such as stakeholder requirements, system requirements, functions, system elements, documents, etc.