Verification is one aspect of testing a product's fitness for purpose. Validation is the complementary aspect. Often one refers to the overall checking process as V & V.
Validation: "Are we building the right product?", i.e., does the product do what the user really requires.
Verification: "Are we building the product right?", i.e., does the product conform to the specifications.
The verification process consists of static and dynamic parts. E.g., for a software product one can inspect the source code (static) and run against specific test cases (dynamic).
Validation usually can only be done dynamically, i.e., the product is tested by putting it through typical usages and atypical usages ("Can we break it?").
Validation: "Are we building the right product?", i.e., does the product do what the user really requires.
Verification: "Are we building the product right?", i.e., does the product conform to the specifications.
The verification process consists of static and dynamic parts. E.g., for a software product one can inspect the source code (static) and run against specific test cases (dynamic).
Validation usually can only be done dynamically, i.e., the product is tested by putting it through typical usages and atypical usages ("Can we break it?").
Hi, nice post. Well what can I say is that these is an interesting and very informative topic. Thanks for sharing your ideas, its not just entertaining but also gives your reader knowledge. Good blogs style too, Cheers!
ReplyDeletevalidation engineering jobs