Salt and pepper, Batman and Robin, and verification and validation (V&V) have more in common than one might think. For instance, all three of these random pairs operate better together. With IEEE 1012-2016: IEEE Standard for System, Software, and Hardware Verification and Validation, an organization can see how one of those dynamic duos (it’s V&V, for the record) is appropriately made to work in tandem. The scope of IEEE 1012-2016 is large, and the standard addresses systems in hardware and software. Generally, verification and validation exists so that a system can work to the best of its ability. IEEE 1012-2016 is a standard to assure that anyone who uses V&V may work to the best of their ability.
V&V is there to help you catch issues with process before someone else does. It’s a rigorous procedure started at a product’s beginnings and carried constantly throughout its creation. It stresses risks of products and gives an early look at what might be working and what’s not working in a product. A rigorous V&V procedure provides information to assure the processes are heading in the correct direction. At the end it’s there to assure the goals one has set out at the beginning have been met.
Again, IEEE 1012-2016 is a standard with a large scope. However, whether it’s system, software, or hardware, or commonly a combination of these processes, the IEEE 1012-2016 V&V standard helps provide achievable goals for specific products. Remember “V&V reporting occurs throughout the system, software, or hardware life cycle.” It is there to help make V&V work better.
After scouring the Internet or the pages of IEEE 1012-2016 and getting lost in the breadth of the material, one might think there is no difference between verification and validation. Maybe it doesn’t matter; it’s unimportant. Look closer.
Verification shows that the product is working from one step to the next. Validation is basically the end evaluation of everything. Does it work as intended? Does it meet a customer’s needs? One can have verification without validation and vice versa, but like salt without pepper, Batman without Robin, it just wouldn’t feel right.
IEEE 1012-2016 revises IEEE 1012-2012. It has been changed from the previous edition in the following ways:
- IEEE 1012-2016 addresses the amended processes of ISO/IEC/IEEE 15288:2015 System and software engineering – System life cycle processes.
- V&V in IEEE 1012-2016 was built to correspond with ISO/IEC/IEEE 15288:2015 and ISO/IEC Std 12207:2008.
IEEE 1012-2016: IEEE Standard for System, Software, and Hardware Verification and Validation is available on the ANSI Webstore.
this page should be updated to correct the typoé:
IEEE 1012-1016 revises IEEE 1012-2012; sgall read IEEE 1012-2016 , “2”
the 1016 typo is present a few places on this page.
Thanks for catching that! Should be fixed now.