Name PHAM VAN KHANH Student ID 2020227014

Personal Major Electrical engineering Grade Combine/1st semester

information 연구방법론
Date 2020/11/18 Class
12th week AI기만공격

Machine learning (ML) plays an ever-increasing role in advanced automotive

functionality for driver assistance and autonomous operation; however, its adequacy
from the perspective of safety certification remains controversial. In this paper, we
analyze the impacts that the use of ML as an implementation approach has on the ISO
26262 safety lifecycle and ask what could be done to address them. This method helps
in the systematic identification of implementation failures. The failures occurring due to
incomplete and inconsistent requirements are also identified. In this method, the input
values are derived from the behavioral requirements which are usually developed
previously. If there are no documented requirements, they need to be deduced from the
functional model as it has the executable specifications. It has to be made sure that for
all the requirements that have to be implemented by a software unit, one test case must
be defined. Interface Testing as per ISO 26262 standard: Correct implementation of

Summary interfaces is very strongly recommended by the ISO 26262 unit test recommendation
table. This is because every software unit may have been tested individually but their
communication with other units is also very critical. During the interface testing, the
value range of the incoming signals from the interface is defined and divided into classes.
These classes have a boundary value which is used to define the test cases. After the test
cases are defined interface testing can be performed. Interface testing is performed to
detect early failures that could go unnoticed till the integration testing process. At that
stage, it would be even difficult to localize the issue. Fault Injection Testing: Quite a
self-explanatory term, fault injection implies the insertion of some arbitrary faults. This
may include corrupting the values of CPU registers, code mutation, corrupting the
variable value, and more. Faults can be injected either at compile-time or run-time. This
testing is done to ensure that the software unit behaves in an expected manner at the
occurrence of any error.