Difference between revisions of "Verification (glossary)"
Wikiexpert (talk | contribs) |
|||
| Line 35: | Line 35: | ||
===Discussion=== | ===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?) | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 22:09, 23 August 2012
(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
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?)
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