Difference between revisions of "Validation (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Updated (1a))
(34 intermediate revisions by 9 users not shown)
Line 1: Line 1:
<blockquote>(1) ''Confirmation, through the provision of objective evidence, that the (Stakeholder) [[Systems Requirement (glossary)|requirements]] for a specific intended use or application have been fulfilled.'' (ISO/IEC 2008, Section 4.37) </blockqute>
+
<blockquote>(1a) ''Confirmation, through the provision of objective evidence, that the (stakeholder) requirements for a specific intended use or application have been fulfilled.'' (ISO 9000:2015) </blockquote>
  
<blockquote>(2)'' The [[Process (glossary)|process]] of providing evidence that the [[Software (glossary)|software]] and its associated [[Product (glossary)|products]] satisfy [[System Requirement (glossary)|system requirements]] allocated to software at the end of each [[Life Cycle (glossary)|life cycle]] activity, solve the right problem, and satisfy intended use and [[User (glossary)|user]] needs. ''(IEEE 1012-2004, 3.1.35) </blockquote>
+
<blockquote>(1b)'' The set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment. The right system was built.'' (ISO/IEEE 2015, 1, Section 6.4.8) </blockquote>
  
<blockquote>(3)'' The set of activities ensuring and gaining confidence that a [[System (glossary)|system]] is able to accomplish its intended use, goals and objectives;'' (ISO/IEEE 2008, 1, Section 4.54) </blockquote>
+
<blockquote>(2) ''The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with verification.'' (PMI 2013) </blockquote>
  
<blockquote>(4) ''The process of evaluating a system or [[Component (glossary)|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) </blockquote>
+
<blockquote>(3)'' 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) </blockquote>
 
 
<blockquote>(5) ''The assurance that a product, service, or system meets the needs of the [[Customer (glossary)|customer]] and other identified [[Stakeholder (glossary)|stakeholders]]; ''(PMI 2008) </blockquote>
 
 
 
<blockquote>(6) ''Confirmation by examination and provision of objective evidence that the particular requirements for a specified intended use are fulfilled;'' (ISO 8402) </blockquote>
 
 
 
<blockquote>(7) ''The process of determining that the [[Systems Engineering (glossary)|systems engineering]] process had produced the right system based upon the needs expressed by the stakeholder.'' (Buede 2009)</blockquote>
 
  
 
===Source===
 
===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).
+
(1) ISO/IEC/IEEE. 2015. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (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
+
(2) PMI. 2013. ''[[A Guide to the Project Management Body of Knowledge|A Guide to the Project Management Body of Knowledge (PMBOK® Guide)]]''. 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI).  
  
(7) Buede, D. M. 2009. ''The Engineering Design of Systems: Models and Methods''. 2nd ed. Hoboken, NJ, USA: John Wiley & Sons Inc.
+
(3) IEEE. 2004. ''IEEE Standard for Software Verification and Validation.'' Institute of Electrical and Electronics Engineers (IEEE) Standards Association: 3.1.35. IEEE 1012-2004.
  
 
===Discussion===
 
===Discussion===
''Verification'' is a process to answer the question ''Have we built the system right?'' (i.e., does it satisfy the system requirements?)
+
Definition (1a) refers to the outcome of providing evidence that a particular system realization is validated (i.e., Does it satisfy the customer and user needs as stated and agreed?).  The word (stakeholder) has been added to clarify the definition.
  
''Validation'' answers the question ''Have we built the right system?'' (i.e., does it satisfy the customer and user needs?)
+
Definition (1b) is based on the introduction to the validation process and refers to the process of achieving validation through a set of activities conducted across a system’s [[Life Cycle (glossary)]] to ensure that the system that has been built will serve its intended purpose. The term (engineered) system has been added to conform to SEBoK terminology.
  
For a full discussion of the role and importance of validation in Systems Engineering see the [[System Validation]] article.
+
Definition (3) refers to the validation of software components in terms of satisfying both allocated system requirements as well as user needs.
  
 +
Validation builds on the activities and outcome of verification, a process that confirms that the system has been built correctly (i.e., Does it satisfy the system requirements?).
  
 +
For a full discussion of the role and importance of validation in systems engineering see the [[System Validation]] article.
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
  
{{DISQUS}}
+
<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>

Revision as of 15:04, 14 October 2021

(1a) Confirmation, through the provision of objective evidence, that the (stakeholder) requirements for a specific intended use or application have been fulfilled. (ISO 9000:2015)

(1b) The set of activities ensuring and gaining confidence that a system is able to accomplish its intended use, goals and objectives (i.e., meet stakeholder requirements) in the intended operational environment. The right system was built. (ISO/IEEE 2015, 1, Section 6.4.8)

(2) The assurance that a product, service, or system meets the needs of the customer and other identified stakeholders. It often involves acceptance and suitability with external customers. Contrast with verification. (PMI 2013)

(3) 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)

Source

(1) ISO/IEC/IEEE. 2015. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (E).

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

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

Discussion

Definition (1a) refers to the outcome of providing evidence that a particular system realization is validated (i.e., Does it satisfy the customer and user needs as stated and agreed?). The word (stakeholder) has been added to clarify the definition.

Definition (1b) is based on the introduction to the validation process and refers to the process of achieving validation through a set of activities conducted across a system’s life cycle to ensure that the system that has been built will serve its intended purpose. The term (engineered) system has been added to conform to SEBoK terminology.

Definition (3) refers to the validation of software components in terms of satisfying both allocated system requirements as well as user needs.

Validation builds on the activities and outcome of verification, a process that confirms that the system has been built correctly (i.e., Does it satisfy the system requirements?).

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

SEBoK v. 2.5, released 15 October 2021