Verification vs Validation #QuickRead
Break down traditional QA silos and empower developers to own quality checks.
Nailing that distinction between Verification and Validation is not a difficult one, but it does trigger a brief moment of confusion. Lets revisit their definitions, and a method I’ve used that may help you to remember the difference between Verification and Validation.
I’ve listed two definitions from IEEE-STD-610 and ISTQB, in order to provide variety with the hope that one of them is easier for you to remember.
Verification:
“A test of a system to proce that it meets all its specified requirements at a particular stage of its development.” — IEEE-STD-610
“Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.” — ISTQB
Validation:
“An activity that ensures that an end product stakeholder’s true needs and expectations are met.” — IEEE-STD-610
“Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.” — ISTQB
Remembering Verification
Ask yourself the following: “Are we building the right product?”.
Variations include: “Am I building the product right?” or “Have we built the software right?”.
Remembering Validation
Ask yourself the following: “Are we building the right product?”.
Variations include: “Am I building the right product?” or “Have we built the right software?”
Subscribe if you like what you’ve read? Leave a clap 👏 and stay tuned for more!
