According to what I understand, Requirement validation involves going over the SRS to ensure the requirements are correct with respect to the user's needs.

  1. Could you help clarify verifiable requirement (checked during validation)?
  2. What is the difference between "requirement verification" and "requirement validation"?

An example to clarify the concepts would be great.

2 Answers 2


Verification and validation are indeed a frequent source of confusion and they are often used interchangeably when they shouldn't.

Let's quote IEEE's (free) SWEBOK, page 10-6:

Verification is an attempt to ensure that the product is built correctly, in the sense that the output products of an activity meet the specifications imposed on them in previous activities.

Validation is an attempt to ensure that the right product is built —that is, the product fulfills its specific intended purpose.

In other words, verification checks that product complies with the requirements, whereas validation checks that the goals are met. Verification is something that you can do. Validation is somewhat where the client or the users have to provide feed-back.

Applied to the requirements, it means (page 1-11):

The requirements may be validated to ensure that the software engineer has understood the requirements; it is also important to verify that a requirements document conforms to company standards and that it is understandable, consistent, and complete.

In other words, in the verification you check that the requirements reflect what the user told you, that they are well written and accurate. While you are verifying this you might find ambiguities and clarify them. For the validation, the client or users approves the requirements, confirming that what they understand seems to reflect what they think is needed.

In practice, verification and validation are embedded in the development process. At every step, verification intends to ensures accuracy and compliance with expectations. Validation intends to get a feedback about success.


Verification :is testing that your product meets the specifications / requirements you have written. "Did I build the system right ?".

Validation :tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. "Did I build the right system ?

V&V together make sure that your software has delivered on its purpose in an error-free way.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.