Difference between revisions of "Verification (glossary)"
| Line 22: | Line 22: | ||
Definition 3 refers to verification at the end of each lifecycle stage that both software and systems have been developed in compliance with all standard practices and rules. | Definition 3 refers to verification at the end of each lifecycle stage that both software and systems have been developed in compliance with all standard practices and rules. | ||
| − | Verification supports the activities and outcome of | + | |
| + | Verification supports the activities and outcome of [[Validation (glossary)]] a process to 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 verification in Systems Engineering see the [[System Verification]] article. | For a full discussion of the role and importance of verification in Systems Engineering see the [[System Verification]] article. | ||
Revision as of 22:01, 17 March 2013
(1a) The set of activities ensuring and gaining confidence that all system elements satisfy the performance, functional and non-function requirements placed on them (ISO/IEEE 2008, 1, Section 4.54)
(1b) Confirmation, through the provision of objective evidence, that specified (system) requirements have been fulfilled; (ISO/IEC 25000:2005, 4.64) (ISO/IEC 2008, 4.38; ISO/IEEE 2008, 1, 4.55)
(2) The evaluation of whether or not a product, service, or system complies with a regulation, requirement, specification, or imposed condition. (PMBOK® Guide)
(3a) 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)
(3b) Process of providing objective evidence that the software and its associated products comply with requirements for all life cycle activities during each life cycle process, 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)
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) PMI. 2008. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 4th 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: IEEE 1012-2004.
Discussion
Definition 1a refers to the Process of achieving Verification through a set of activities conducted across a system’s life cycle to answer the question Have we built the system right?
Definition 1b refers to the outcome of providing evidence that a particular system realization is Verified (i.e. does it satisfy the specified and agreed system requirements?). The word (System) has been added to clarify the definition
Definition 3 refers to verification at the end of each lifecycle stage that both software and systems have been developed in compliance with all standard practices and rules.
Verification supports the activities and outcome of validation a process to 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 verification in Systems Engineering see the System Verification article.
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