Validating test questions
Then design document will be checked against functional spec (it should design 4 checkboxes..), and the source code against design (is there a code for 4 checkboxes, functions to send the signals etc. Okay, product is built and we need to test it, validate.Here comes our understanding trouble - validation should ensure the product meets requirements for its specific intended use which is basically business requirement (does it work? ) but testers will definitely work with the functional spec, making sure the checkboxes are there, working, labelled, etc.Your access to the NCBI website at gov has been temporarily blocked due to a possible misuse/abuse situation involving your site.This is not an indication of a security issue such as a virus or attack.They are basically checking whether the requirements in functional spec were met in the final product, isn't that verification?
Validation is the customer saying yup, thats everything we wanted in this phase.
Generally, verification helps answering "Are we building the product right? Validation, on the other hand, is trying to answer "Are we building the right product? So, while verification concerns requirements coverage, and if work products (not just code) meet what has been planned and designed (including standards and processes); validation ensures that products meet users expectations (that may not be exactly what is defined in requirement specification).