Difference between revisions of "Verification (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created page with '''<blockquote>The proportion of time a system is in a functioning state.</blockquote>'' ====Source==== None cited. ===Discussion=== Category:Glossary of Terms')
 
Line 1: Line 1:
''<blockquote>The proportion of time a system is in a functioning state.</blockquote>''
+
''<blockquote>(1) Confirmation, through the provision of objective evidence, that specified requirements have been fulfilled; (ISO/IEC 25000:2005, 4.64) (ISO/IEC 2008, Section 4.38; ISO/IEEE 2008, 1, Section 4.55) </blockquote>''
 +
 
 +
''<blockquote>(2) Formal proof of program correctness; (ISO/IEC 2009, 1) </blockquote>''
 +
 
 +
''<blockquote>(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) </blockquote>''
 +
 
 +
''<blockquote>(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) </blockquote>''
 +
 
 +
''<blockquote>(5) The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition; (PMBOK® Guide) </blockquote>''
 +
 
 +
''<blockquote>(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) </blockquote>''
 +
 
 +
''<blockquote>(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.</blockquote>''
  
 
====Source====
 
====Source====
None cited.
+
(1)
 +
 
 +
(2)
 +
 
 +
(3)
 +
 
 +
(4)
 +
 
 +
(5)
 +
 
 +
(6)
 +
 
 +
(7)
  
 
===Discussion===
 
===Discussion===

Revision as of 02:04, 20 May 2011

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

(2) Formal proof of program correctness; (ISO/IEC 2009, 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)

(2)

(3)

(4)

(5)

(6)

(7)

Discussion