Validation (glossary)

(1) Confirmation, through the provision of objective evidence, that the (Stakeholder) requirements for a specific intended use or application have been fulfilled. (ISO/IEC 2008, Section 4.37) </blockqute>

(2) The process of providing evidence that the software and its associated products satisfy system requirements allocated to software at the end of each life cycle activity, solve the right problem, and satisfy intended use and user needs. (IEEE 1012-2004, 3.1.35)

(3) The set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals and objectives; (ISO/IEEE 2008, 1, Section 4.54)

(4) The process of evaluating a system or component during or at the end of the development process to determine whether a system or component satisfies specified requirements; (IEEE 1998a, Section 3.2)

(5) The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders; (PMI 2008)

(6) Confirmation by examination and provision of objective evidence that the particular requirements for a specified intended use are fulfilled; (ISO 8402)

(7) The process of determining that the systems engineering process had produced the right system based upon the needs expressed by the stakeholder. (Buede 2009)

Source

(1) ISO/IEC. 2008. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). ISO/IEC 15288:2008 (E).

(2) IEEE. 2004. IEEE Standard for Software Verification and Validation. Institute of Electrical and Electronics Engineers (IEEE) Standards Association: 3.1.35. IEEE 1012-2004.

(3) ISO/IEC. 2008. Systems and Software Engineering — System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 15288:2008 (E).

(4) IEEE. 1998. IEEE Guide for Developing System Requirements Specifications. Washington, DC: Institute of Electrical and Electronics Engineers(IEEE) Standards Association, IEEE 1233-1998.

(5) PMI. 2008. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).

(6) ISO 8402. 1994. Quality Management and Quality Assurance — Vocabulary Geneva, Switzerland: International Organization for Standardization (ISO). ISO 8402:1994

(7) Buede, D. M. 2009. The Engineering Design of Systems: Models and Methods. 2nd ed. Hoboken, NJ, USA: John Wiley & Sons Inc.

Discussion

Verification is a process to answer the question Have we built the system right? (i.e., does it satisfy the system requirements?)

Validation answers the question Have we built the right system? (i.e., does it satisfy the customer and user needs?)

For a full discussion of the role and importance of validation in Systems Engineering see the System Validation article.

SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus