验证和确认的区别_验证与确认之间的区别

桃扇骨 2022-12-07 13:25 252阅读 0赞

![07dd82306736c126f36c92c50256c064.png][]

验证和确认的区别

Today we are going to cover the topic difference between Verification and Validation.

今天，我们将讨论验证和验证之间的主题差异。

These terms can be very prominent and are widely used with respect to the software development. These two words are independent to each other and are the mechanisms to check if the product or service that is meant to be delivered to the end client satisfies the user requirements and whether able to fulfill its intended purpose or not.

这些术语可能非常突出，并在软件开发方面得到广泛使用。 这两个词彼此独立，并且是检查要交付给最终客户的产品或服务是否满足用户要求以及是否能够满足其预期目的的机制。

So without wasting much of our time let’s quickly get started by giving a brief introduction about what does these two terms Verification and Validation mean literally.

因此，在不浪费大量时间的情况下，让我们简要介绍一下“验证”和“验证”这两个术语的含义是什么，让我们快速上手。

**Also Read: [Difference between Testing and Debugging][]**

**另请阅读： [测试和调试之间的区别][Difference between Testing and Debugging]**

### 验证 **(**Verification**)** ###

Tagline: *Have we built the software right?*

口号： *我们是否正确构建了软件？*

Verification is basically the mechanism to verify the software, that the output of any of the development phase must comply with the requirements specified at the time of initiation of that phase.

验证基本上是验证软件的机制，任何开发阶段的输出都必须符合该阶段启动时指定的要求。

Verification, talking in terms of software engineering is regarded as the ***static*** means of verifying the specification, documents, design and code. Not only these but verification is responsible for verifying all the steps involved in the development process of the software like inspection, specification analysis, design analysis etc.

就软件工程而言，验证被视为验证规范，文档，设计和代码的***静态***方法。 不仅这些，而且验证还负责验证软件开发过程中涉及的所有步骤，例如检查，规范分析，设计分析等。

Moreover, verification is aimed at finding out whether the software is of high quality or not, on the other hand it can’t evaluate the usefulness of the software.

此外，验证的目的在于确定软件是否具有高质量，而另一方面却无法评估软件的实用性。

Following methods are followed to carry out verification process:

按照以下方法进行验证过程：

*  Walkthrough
    
    演练
 *  Inspection
    
    检查
 *  Code Review
    
    代码审查

### 验证方式 **(**Validation**)** ###

Tagline: *Have we built the right software?*

口号： *我们是否构建了正确的软件？*

This mechanism is the process of inspecting the software in between or at the end of the development phase and making sure that the software must comply with the specified requirements.

此机制是在开发阶段之间或结束时检查软件并确保软件必须符合指定要求的过程。

Validation process deals with the evaluation of end product (software) to ensure whether the produced software meets the end users expectation or not. This process is termed as the ***dynamic***mechanism of evaluating the software product.

验证过程涉及对最终产品(软件)的评估，以确保所生产的软件是否符合最终用户的期望。 此过程称为评估软件产品的***动态***机制。

Following methods are adopted to accomplish the objective of validation process:

采用以下方法来完成验证过程的目标：

*  Testing and
    
    测试和
 *  End Users
    
    终端用户

## 验证与确认之间的区别 **(**Difference between Verification and Validation**)** ##

We’ve seen what two terms Verification and Validation mean in the world of software testing. Now let’s quickly do a comparative study of these two to figure out the differences and find out what common features do they share.

我们已经了解了软件测试领域中的“验证”和“验证”这两个术语的含义。 现在，让我们快速对这两者进行比较研究，以找出差异并找出它们共有的共同特征。

<table> 
 <tbody> 
  <tr> 
   <td><strong>Verification</strong></td> 
   <td><strong>Validation</strong></td> 
  </tr> 
  <tr> 
   <td>It is regarded as the static method of verifying the code, design and documents.</td> 
   <td>It is termed as the dynamic practice to validate the end product.</td> 
  </tr> 
  <tr> 
   <td>This process is usually carried out by humans.</td> 
   <td>This is primarily accomplished by computers.</td> 
  </tr> 
  <tr> 
   <td>It is to ensure that software complies with the specifications.</td> 
   <td>It is to ensure that the end client’s expectation is met or not.</td> 
  </tr> 
  <tr> 
   <td>Execution of the program code is not required in this step.</td> 
   <td>Execution of code is the basic need.</td> 
  </tr> 
  <tr> 
   <td>Errors that cannot be tracked during validation are caught here.</td> 
   <td>Errors that cannot be tracked during verification are caught here.</td> 
  </tr> 
  <tr> 
   <td>It is done by the QA team to conform the software’s compliance with the SRS.</td> 
   <td>It is carried out with collaboration of developers and testing team.</td> 
  </tr> 
  <tr> 
   <td>It is executed before validation process.</td> 
   <td>It is done usually after the verification process.</td> 
  </tr> 
  <tr> 
   <td>It explains if the outputs are according to the inputs or not.</td> 
   <td>It explains whether a customer is going to accept the product or not.</td> 
  </tr> 
  <tr> 
   <td>Errors caught at this stage are usually less costly to remove.</td> 
   <td>Errors cost more to be removed at this stage.</td> 
  </tr> 
  <tr> 
   <td>Accomplished via Walkthrough, Inspection and Code Review.</td> 
   <td>Accomplished through Testing and surveys with the End Users.</td> 
  </tr> 
 </tbody> 
</table>

<table> 
 <tbody> 
  <tr> 
   <td> <strong>验证</strong> </td> 
   <td> <strong>验证方式</strong> </td> 
  </tr> 
  <tr> 
   <td> 它被视为验证代码，设计和文档的静态方法。 </td> 
   <td> 这被称为验证最终产品的动态实践。 </td> 
  </tr> 
  <tr> 
   <td> 此过程通常由人类执行。 </td> 
   <td> 这主要是由计算机完成的。 </td> 
  </tr> 
  <tr> 
   <td> 这是为了确保软件符合规范。 </td> 
   <td> 这是为了确保满足或不满足最终客户的期望。 </td> 
  </tr> 
  <tr> 
   <td> 在此步骤中不需要执行程序代码。 </td> 
   <td> 执行代码是基本需求。 </td> 
  </tr> 
  <tr> 
   <td> 验证期间无法跟踪的错误在此处捕获。 </td> 
   <td> 验证期间无法跟踪的错误在此处捕获。 </td> 
  </tr> 
  <tr> 
   <td> 由质量检查团队完成，以使软件符合SRS。 </td> 
   <td> 它是在开发人员和测试团队的协作下进行的。 </td> 
  </tr> 
  <tr> 
   <td> 它在验证过程之前执行。 </td> 
   <td> 通常在验证过程之后完成。 </td> 
  </tr> 
  <tr> 
   <td> 它说明了输出是否与输入一致。 </td> 
   <td> 它说明了客户是否要接受该产品。 </td> 
  </tr> 
  <tr> 
   <td> 在此阶段捕获的错误通常以较低的代价消除。 </td> 
   <td> 在此阶段，消除错误的成本更高。 </td> 
  </tr> 
  <tr> 
   <td> 通过演练，检查和代码审查完成。 </td> 
   <td> 通过与最终用户的测试和调查来完成。 </td> 
  </tr> 
 </tbody> 
</table>

At last we come to conclude that both these processes are necessary to the software development process in one way or the other. Both the mechanisms have got different potentials and advantages to encounter the defect and vulnerabilities at different stages of the software development cycle.

最后，我们得出的结论是，这两个过程对于软件开发过程而言都是必不可少的。 两种机制在软件开发周期的不同阶段遇到缺陷和漏洞时，都有不同的潜力和优势。

That is all for today. If you’ve got any doubts or queries related to verification vs validation then, please feel free to ask in the comment section. We will be happy to help. Suggestions are equally welcomed from the readers end.

今天就这些。 如果您对验证与验证有任何疑问或疑问，请随时在评论部分提问。 我们将很乐意提供帮助。 读者的建议也同样受欢迎。

> 翻译自: [https://www.thecrazyprogrammer.com/2018/04/difference-between-verification-and-validation.html][https_www.thecrazyprogrammer.com_2018_04_difference-between-verification-and-validation.html]

验证和确认的区别

[07dd82306736c126f36c92c50256c064.png]: /images/20221123/5c31069b7de1405eb922782a6c5ea15f.png
[Difference between Testing and Debugging]: https://www.thecrazyprogrammer.com/2018/01/difference-testing-debugging.html
[https_www.thecrazyprogrammer.com_2018_04_difference-between-verification-and-validation.html]: https://www.thecrazyprogrammer.com/2018/04/difference-between-verification-and-validation.html