ISO26262 Part1 之 Verification 的方法汇总

1.目的

Verification的目的是确保工作产物满足相应的需求；

2.适用情况

2.1在概念阶段

验证确保了概念是正确的、完整的,并符合相关项的边界条件,同时确保了定义的边界条件本身是正确的、完整的和一致的,以使概念可以得到实现。

2.2 在产品开发阶段

以不同的方式执行验证,描述如下:

—在设计阶段,验证是对工作成果的评估,例如,需求规范、架构设计、模型或软件编码,从而确保它们与之前建立的要求在正确性、完整性和一致性方面相符合;
评估可通过评审、模拟或分析技术开展，并以系统化方式计划、定义、执行和记录;
（此处是相应的VR评审活动，时间计划可以涵盖在Safety Plan里面）

—在测试阶段,验证是在测试环境下对工作成果、相关项和要素的评估,以确保其满足要求。
测试以系统化的方式进行计划、定义、执行、评估和记录。
（此处可以对于V模型的右侧，有详细的测试计划，测试规范，测试报告）

2.3 在生产和运行阶段

验证确保了:
—生产过程中恰当地满足安全相关的特殊特性;
—在用户手册、维修和维护指导中恰当地提供了安全相关的信息;
—通过在生产流程中应用控制措施,相关项的安全相关特性得到了满足。

3. 方法种类

The typical verification activities can be classified as follows:
— verification review (3.181), walk-through (3.182), inspection (3.82);
— verification testing (3.169);
— simulation;
— prototyping; and
— analysis (safety (3.132) analysis, control flow analysis, data flow analysis, etc.).

4. 回答问题

实际上，对应核心的问题，Verification实际上可以分为两部分，

• 一部分是设计阶段的Verification，这里更多的是采用Review评审的方式，也可以与CR相合并；
• 一部分是测试阶段的Verification，这里其实是对应的V模型的右侧，实际的SIL，HIL，台架测试等；对应的是Safety plan中的 测试计划，测试规范，测试报告；

5. 参考定义

5.1 Verification Methods in Software Verification

Reviewing any software to find faults is known as Software Verification. Verification is the process of checking that software achieves its goal without any bugs. It is the process to ensure whether the product that is developed is right or not. The reviewing of a document can be done from the first phase of software development i.e. software requirement and analysis phase where the end product is the SRS document. There are many methods for practicing the verification of the software like peer-reviews, walkthroughs, inspections, etc. that can help us in the prevention of potential faults otherwise, it may lead to the failure of the software.

5.2 Methods of Verification

Here are some of the common methods that are required for Verification are listed below.

• Peer Reviews
• Walk Through
• Inspections

Peer Reviews

The easiest method and most informal way of reviewing the documents or the programs/software to find out the faults during the verification process is the Peer-Review method. In this method, we give the document or software programs to others and ask them to review those documents or software programs where we expect their views about the quality of our product and also expect them to find the faults in the program/document. The activities that are involved in this method may include SRS document verification, SDD verification, and program verification. In this method, the reviewers may also prepare a short report on their observations or findings, etc.

Advantages of Peer Reviews:

• You can expect some good results without spending any significant resources.
• It is very efficient and significant in its nature.

Disadvantages of Peer Reviews:

• Lead to bad results if the reviewer doesn’t have sufficient knowledge.

Walk-Through

Walk-throughs are a formal and very systematic type of verification method as compared to peer review. In a walkthrough, the author of the software document presents the document to other persons which can range from 2 to 7. Participants are not expected to prepare anything. The presenter is responsible for preparing the meeting. The document(s) is/are distributed to all participants. At the time of the meeting of the walk-through, the author introduces the content in order to make them familiar with it and all the participants are free to ask their doubts.

Advantages of Walk-Through

• It may help us to find potential faults.
• It may also be used for sharing documents with others.

Disadvantages of Walk-Through
The author may hide some critical areas and unnecessarily emphasize some specific areas of his / her interest.

Inspections

Inspections are the most structured and formal type of verification method and are commonly known as inspections. A team of three to six participants is constituted which is led by an impartial moderator. Every person in the group participates openly, and actively, and follows the rules about how such a review is to be conducted. Everyone may get time to express their views, potential faults, and critical areas. After the meeting, a final report is prepared after incorporating necessary suggestions from the moderator.

Advantages of Inspections:

• It can be very effective for finding potential faults or problems in documents like SRS, SDD, etc.
• The critical inspections may also help in finding faults and improve these documents which can in preventing the propagation of a fault in the software development life cycle process.

Disadvantages of Inspections:

• They take time and require discipline.
• It requires more cost and also needs skilled testers.

Applications of Verification Methods

The above three verification methods are very popular and have their strengths and weaknesses. We can compare these methods on various specific issues as given below:

6. 参考引用

https://www.geeksforgeeks.org/verification-methods-in-software-verification/?ref=header_search