𝐖𝐡𝐚𝐭 𝐝𝐨 𝐲𝐨𝐮 𝐦𝐞𝐚𝐧 𝐛𝐲 𝐕𝐞𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐚𝐧𝐝 𝐕𝐚𝐥𝐢𝐝𝐚𝐭𝐢𝐨𝐧?

The most commonly discussed, confused, interchanged and asked question.

A generic definition for them would be
𝐕𝐚𝐥𝐢𝐝𝐚𝐭𝐢𝐨𝐧: ” Are we building the right product?”
𝐕𝐞𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧: ” Are we building the product right?” -Boehm, 1979.

Interesting, but still confusing.

Before we head into the definition of what Verification and Validation is, we need to understand the root activity that shines light on those words. “𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬” . What are requirements?

“Requirements are defined as a prerequisite to accomplishing design work because of the nature of complex systems and the need for many people to work together to develop complex systems.” – Grady’s book.

Once you’ve understood this statement, we can now dive into understanding V and V.

On a higher level, we can consider the understanding of those activities as
Validation: The right system is going to be built.
Verification: The requirements that are designed are compliant with the design.

On a deeper level,
– Validation is applied during concept development and early design work to ensure that specific requirements are necessary, and optimally valued and that it is possible to satisfy them i.e 𝐕𝐚𝐥𝐢𝐝𝐚𝐭𝐢𝐨𝐧 𝐢𝐬 𝐝𝐨𝐧𝐞 𝐝𝐮𝐫𝐢𝐧𝐠 𝐭𝐡𝐞 𝐞𝐚𝐫𝐥𝐲 𝐬𝐭𝐚𝐠𝐞𝐬 𝐨𝐟 𝐝𝐞𝐬𝐢𝐠𝐧 𝐭𝐨 𝐦𝐚𝐤𝐞 𝐬𝐮𝐫𝐞 𝐭𝐡𝐚𝐭 𝐭𝐡𝐞 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 𝐚𝐫𝐞 𝐧𝐞𝐜𝐞𝐬𝐬𝐚𝐫𝐲, 𝐯𝐚𝐥𝐮𝐚𝐛𝐥𝐞 𝐚𝐧𝐝 𝐜𝐚𝐧 𝐛𝐞 𝐦𝐞𝐭.

– Verification work is applied after the design work on test articles and early production items to produce evidence that the design solutions satisfy the requirements. i.e 𝐕𝐞𝐫𝐢𝐟𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐰𝐨𝐫𝐤 𝐢𝐬 𝐝𝐨𝐧𝐞 𝐚𝐟𝐭𝐞𝐫 𝐭𝐡𝐞 𝐝𝐞𝐬𝐢𝐠𝐧 𝐰𝐨𝐫𝐤 𝐭𝐨 𝐦𝐚𝐤𝐞 𝐬𝐮𝐫𝐞 𝐭𝐡𝐚𝐭 𝐭𝐡𝐞 𝐝𝐞𝐬𝐢𝐠𝐧 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 𝐦𝐞𝐞𝐭 𝐭𝐡𝐞 𝐫𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬.

Once these basics are clear, we can dive in and understand the various techniques involved.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An Article by: Yashwanth Naidu Tikkisetty
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~