Verification and Validation
Statement 1:
(2) meaning of Verification
Determined that the provision requirements have been met by providing objective evidence.
(2) meaning of "Validation"
Identified that specific intended uses or application requirements have been met by providing objective evidence.
(3) differences between "verification" and "validation"
Both "verification" and "confirmation" are identified. However, "verification" indicates that the requirements are met, while "validation" indicates that the requirements are met for intended purposes or applications. To put it simply, "confirm" is to check whether the product meets the customer's requirements.
(4) the difference between "design verification" and "design validation" in "design and development" is:
The purpose of design verification is to check whether the design output meets the design input requirements.
The purpose of design validation is to check whether the final product formed by the design meets the customer's usage requirements.
Statement 2:
1. "validation" is to prove that the provided (or to be provided) product is suitable for its intended use, "Verification" is to find out whether the work products properly reflect the specified requirements. In other words, verification should ensure that "done correctly", while confirmation should ensure that "done correctly ".
2. Verification focuses on "process" and validation focuses on "results"
3. (Verification) --- Are we producing the product right?
(Validation) --- Are we producing the right product?
Statement 3:
1. What is verification?
Verification is to use data to prove whether we are creating the product correctly. Note that the process is correct.
2. What is confirmation?
Verify that we have created the right product with data. Note that the result is correct.
3. Verification and validation are a broad concept that interested readers can refer to IEEE Std 1012-1998.
Verification: check whether a certain item meets the previously set standards, for example, document review. The items to be checked are documents, and the inspection standards are the document review standards, for example: software is the thing to check for the testing software, and the inspection standard is the software specification description, including the function description and performance requirements.
Confirm: Check whether the software has reached the expected goal in the final execution environment. In general, debugging, acceptance testing, and so on are all performed in the real environment where the software needs to be executed. Finally, the software is executed in the environment to ensure that the software meets the requirements for use.
Note:
Valiadation many others verify that the product is consistent with what they want from the user's perspective or the user's perspective. From the perspective of SP, it may be easier to understand this;
Verification many others are reviewing and testing from the developer's perspective to verify whether the product requirements and architecture design are consistent with the user requirements;
Statement 4:
(1) meaning of Verification
The test method is used to check whether a conclusion is correct.
Practice is the only criterion for testing truth. Verification = verification + proof.
That is to say, we use practice to test whether the theory is true. Before verification, the answer may be correct or wrong.
(2) meaning of "Validation"
I already know a conclusion to check whether the theory is executed effectively. It is not necessary to verify the correctness of the theory,
Is a test of the running force. Japanese enterprises like to use the word "OK", which can be understood as: combined
Take a look at the real thing at the site.
Verification and Validation