Verification and Validation (software)

In software project management, software testing, and software engineering, Verification and Validation (V&V) is the process of checking that a software system meets specifications and that it fulfils its intended purpose. It is normally part of the software testing process of a project. In pharmaceutical industry, verification involves testing the suitability of well established procedures or (compendial) methods, whereas validation varies from Cross validation, Empirical validation, periodic partial validation, internal/external validation, competence validation by nature, and Cleaning validation, Process validation, Equipment validation, or Documentation validation by tasks.

Definitions

Also known as software quality control

Validation checks that the product design satisfies or fits the intended usage (high-level checking) — i.e., you built the right product. This is done through dynamic testing and other forms of review.

According to the Capability Maturity Model (CMMI-SW v1.1), “Validation - The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements. [IEEE-STD-610] Verification- The process of evaluating software to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. [IEEE-STD-610] ."

In other words, validation ensures that the product actually meets the user's needs, and that the specifications were correct in the first place, while verification is ensuring that the product has been built according to the requirements and design specifications. Validation ensures that ‘you built the right thing’. Verification ensures that ‘you built it right’. Validation confirms that the product, as provided, will fulfill its intended use.

Within the modeling and simulation community, the definitions of validation, verification and accreditation are similar:

*Validation The process of determining the degree to which a model, simulation, or federation of models and simulations, and their associated data are accurate representations of the real world from the perspective of the intended use(s). [Citation
year = 2008
title = Department of Defense Documentation of Verification, Validation & Accreditation (VV&A) for Models and Simulations
publisher = Missile Defense Agency]
* Accreditation is the formal certification that a model or simulation is acceptable to be used for a specific purpose. [Citation
year = 2008
title = Department of Defense Documentation of Verification, Validation & Accreditation (VV&A) for Models and Simulations
publisher = Missile Defense Agency]
* Verification: The process of determining that a computer model, simulation, or federation of models and simulations implementations and their associated data accurately represents the developer's conceptual description and specifications. [Citation
year = 2008
title = Department of Defense Documentation of Verification, Validation & Accreditation (VV&A) for Models and Simulations
publisher = Missile Defense Agency]

Related concepts

Both verification and validation are related to the concepts of quality and of software quality assurance. By themselves, verification and validation do not guarantee software quality; planning, traceability, configuration management and other aspects of software engineering are required.hmnb

Classification of methods

In mission-critical systems where flawless performance is absolutely necessary, formal methods can be used to ensure the correct operation of a system. However, often for non-mission-critical systems, formal methods prove to be very costly and an alternative method of V&V must be sought out. In this case, syntactic methods are often used.

Test cases

A test case is a tool used in the V&V process.

The QA team prepares test cases for verification--to determine if the process that was followed to develop the final product is right.

The QC team uses a test case for validation--if the product is built according to the requirements of the user. Other methods, such as reviews, when used early in the Software Development Life Cycle provide for validation.

Verification can be called a part of validation process.

Independent Verification and Validation

Verification and validation often is carried out by a separate group from the development team; in this case, the process is called "Independent Verification and Validation", or IV&V.

ee also

* Atsec information security
* Cross-validation
* Formal verification
* Functional specification
* Independent Verification and Validation Facility
* International Software Testing Qualifications Board
* Software verification
* Software Requirements Specification
* Validation
* Validation (drug manufacture)
* Verification and Validation - General

References

* cite book
last=Tran
first=E.
editor=Koopman, P.
title=Topics in Dependable Embedded Systems
publisher=Carnegie Mellon University
year=1999
chapter=Verification/Validation/Certification
chapterurl=http://www.ece.cmu.edu/~koopman/des_s99/verification/index.html
accessdate=2007-05-18
* cite journal
last=Menzies
first=T.
coauthors=Y. Hu
title=Data mining for very busy people
journal=IEEE Computer"
issn=0018-9162
volume=36
issue=1
year=2003
pages=22–29
doi=10.1109/MC.2003.1244531