Difference between revisions of "Verification (glossary)"

From SEBoK
Jump to navigation Jump to search
Line 22: Line 22:
 
(2) ISO/IEC/IEEE. 2010. ''Systems and Software Engineering -- Vocabulary (SEVocab)'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronic Engineers (IEEE) 2009 ISO/IEC/IEEE 24765:2010 [database online]. Available from http://pascal.computer.org/sev_display/index.action.  
 
(2) ISO/IEC/IEEE. 2010. ''Systems and Software Engineering -- Vocabulary (SEVocab)'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronic Engineers (IEEE) 2009 ISO/IEC/IEEE 24765:2010 [database online]. Available from http://pascal.computer.org/sev_display/index.action.  
  
(3) IEEE 1012-2004.  ''IEEE Standard for Software Verification and Validation.'' Institute of Electrical and Electronics Engineers (IEEE) Standards Association: IEEE 1012-2004.
+
(3) IEEE. 2004.  ''IEEE Standard for Software Verification and Validation.'' Institute of Electrical and Electronics Engineers (IEEE) Standards Association: IEEE 1012-2004.
  
 
(4) ISO/IEC. 2001. ''Software engineering — Product quality — Part 1'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC).: ISO/IEC 9126-1:2001.
 
(4) ISO/IEC. 2001. ''Software engineering — Product quality — Part 1'' Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC).: ISO/IEC 9126-1:2001.
Line 28: Line 28:
 
(5) PMI. 2008. ''A Guide to the Project Management Body of Knowledge (PMBOK guide)''. 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).  
 
(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) (IEEE 829-2008, 3.1.54)
+
(6) IEEE. 2008. ''IEEE Standard for Software and System Test Documentation'' Institute of Electrical and Electronics Engineers (IEEE) Standards Association: IEEE 829-2008.
  
 
(7) ISO 8402. 1994. ''Quality Management and Quality Assurance — Vocabulary'' Geneva, Switzerland: International Organization for Standardization (ISO). ISO 8402:1994
 
(7) ISO 8402. 1994. ''Quality Management and Quality Assurance — Vocabulary'' Geneva, Switzerland: International Organization for Standardization (ISO). ISO 8402:1994

Revision as of 15:43, 15 September 2011

(1) Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled; (ISO/IEC 25000:2005, 4.64) (ISO/IEC 2008, 4.38; ISO/IEEE 2008, 1, 4.55)

(2) Formal proof of program correctness; (ISO/IEC/IEEE. 2010, 1)

(3) The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (IEEE 1012-2004, 3.1.36)

(4) Confirmation by examination and provision of objective evidence that the particular requirements for a specific intended use are fulfilled. (ISO/IEC 9126-1:2001)

(5) The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition. (PMBOK® Guide)

(6) Process of providing objective evidence that the software and its associated products comply with requirements (e.g., for correctness, completeness, consistency, and accuracy) for all life cycle activities during each life cycle process (acquisition, supply, development, operation, and maintenance), satisfy standards, practices, and conventions during life cycle processes, and successfully complete each life cycle activity and satisfy all the criteria for initiating succeeding life cycle activities. (IEEE 829-2008, 3.1.54)

(7) Confirmation by examination and provision of objective evidence that specified requirements have been fulfilled. (ISO 8402)

(8) The process of ensuring that a system is built according to stakeholder requirements and design specifications.

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).

ISO/IEC. 2005. Software Engineering — Software Product Quality Requirements and Evaluation (SQuaRE) -- Guide to SQuaRE. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC). ISO/IEC 25000:2005.

(2) ISO/IEC/IEEE. 2010. Systems and Software Engineering -- Vocabulary (SEVocab) Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronic Engineers (IEEE) 2009 ISO/IEC/IEEE 24765:2010 [database online]. Available from http://pascal.computer.org/sev_display/index.action.

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

(4) ISO/IEC. 2001. Software engineering — Product quality — Part 1 Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC).: ISO/IEC 9126-1:2001.

(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) IEEE. 2008. IEEE Standard for Software and System Test Documentation Institute of Electrical and Electronics Engineers (IEEE) Standards Association: IEEE 829-2008.

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

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

Discussion