簡單【結論】：
Verification：確認達成規格 (requirements)；
Validation：確認達成目的 (intended use)。
在品質管理上，Verification和Validation這兩個術語各有其特殊的意義，因此必須加以定義。CMMI-SVC V1.2以及ISO 9000:2000對Verification和Validation分別定義如下：
CMMI-SVC, V1.2
Verification: Confirmation that work products properly reflect the requirements specified for them. In other words, verification ensures that “you built it right.”
Validation: Confirmation that the product or service, as provided (or as it will be provided), will fulfill its intended use. In other words, validation ensures that “you built the right thing.”
ISO 9000:2000
Verification: Confirmation, through the provision of objective evidence (3.8.1), that specified requirements (3.1.2) have been fulfilled. (達成規格)
Validation: Confirmation, through the provision of objective evidence (3.8.1), that the requirements (3.1.2) for a specific intended use or application have been fulfilled. (達成目的)
深入探討，Verification和Validation 這兩個品質管理標準的定義，其規範的對象(概念)是相通的。
【例】
Verification：引擎、傳動軸、輪胎、方向盤、油門、剎車。
Validation：交通工具。
在產品或服務的開發流程中，Verification與Validation的關係和位置如下圖所示：
這個流程的簡單描述如下：
1.首先要找出顧客/使用者對某個產品或服務之預設目的(Intended Use)；
2.然後以開發活動的用語(術語)轉譯這個預設目的。加以詳述，發展成為指定的需求(Specified Requirements)，形成該產品或服務的規格。
3.根據指定需求(規格)，進行產品或服務的開發；
4.接下來就根據規定、指定的需求(規格)，對開發活動的結果進行Verification(驗證)；
5. 最後再對通過驗證的開發活動的產出(也就是產品或服務)進行Validation(驗收)，決定所開發出來的產品或服務是否能夠滿足顧客/使用者預設目的。
Difference between Verification and Validation?
The terms ‘Verification‘ and ‘Validation‘ are frequently used in the software testing world but the meaning of those terms are mostly vague and debatable.
- Verification takes place before validation, and not vice versa.
Verification evaluates documents, plans, code, requirements, and specifications. Validation, on the other hand, evaluates the product itself. - The inputs of verification are checklists, issues lists, walkthroughs and inspection meetings, reviews and meetings. The input of validation, on the other hand, is the actual testing of an actual product.
- The output of verification is a nearly perfect set of documents, plans, specifications, and requirements document. The output of validation, on the other hand, is a nearly perfect, actual product.
|
Criteria
|
Verification
|
Validation
|
|
Definition
|
The process of evaluating work-products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase.
|
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.
|
|
Objective
|
To ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements.
|
To ensure that the product actually meets the user’s needs, and that the specifications were correct in the first place. In other words, to demonstrate that the product fulfills its intended use when placed in its intended environment.
|
|
Question
|
Are we building the product right?
|
Are we building the right product?
|
|
Evaluation Items
|
Plans, Requirement Specs, Design Specs, Code, Test Cases
|
The actual product/software.
|
|
Activities
|
|
|
Reference:
http://cracksoftwaretestinginterviews.blogspot.com/2014/01/16-difference-between-verification-and.html
