In Step 5 “Verify & Validate Requirements” each requirement must be verified and validated to ensure that they are the correct requirements. This ensures that the requirements meet the overall objective of the system and all stakeholder needs.

Visit: Verification and Validation for more information.

Validating Requirements
To validate means to confirm that the requirements meet the operational and system level needs of a program. Validating Requirements ensures that:

  1. The set of requirements is correct, complete, and consistent,
  2. A model can be created that satisfies the requirements, and
  3. A real-world solution can be built and tested to prove that it satisfies the requirements.

Requirements designers should go back to stakeholders again with the requirements document and have them review it. The requirements should also all be traced in a rational database at this point. Take Stakeholder comments and make changes; hopefully there’re not any. You may need to revisit Step 2 “Write & Document Requirements” if there are. Repeat the process until there is complete agreement among all stakeholders. When all requirements are agreed upon, a requirements baseline can be established and managed to in Step 6 “Manage Requirements”.

Verifying Requirements
Requirement must be verified to prove that each one satisfies their stated requirement. Verification can be done by:

AcqLinks and References:

Updated: 7/28/2017

Print Friendly, PDF & Email