TY - JOUR
T1 - ASFIT
T2 - AUTOSAR-based software fault injection test for vehicles
AU - Park, Jihyun
AU - Choi, Byoungju
N1 - Funding Information:
Funding: This research was supported by the Hyundai-Kia Motor Company. This research was supported by the MSIT(Ministry of Science and ICT), Korea, under the ITRC(Information Technology Research Center) support program( IITP-2020-2017-0-01628 ) supervised by the IITP(Institute for Information & communications Technology Promotion)
Publisher Copyright:
© 2020 by the authors. Licensee MDPI, Basel, Switzerland.
PY - 2020/5
Y1 - 2020/5
N2 - With recent increases in the amount of software installed in vehicles, the probability of automotive software faults that lead to accidents has also increased. Because automotive software faults can lead to serious accidents or even mortalities, vehicle software design and testing must consider safety a top priority. ISO 26262 recommends fault injection testing as a measure to verify the functional safety of vehicles. However, the standard does not clearly specify when and where faults should be injected, and the tools to support fault injection testing for automotive software are also insufficient. In the present study, we define faults that may occur in Automotive Open System Architecture (AUTOSAR)-based automotive software and propose a fault injection method to be applied during the software development process. The proposed method can inject different types of faults that may occur in AUTOSAR-based automotive software, such as access, asymmetric, and timing errors, while minimizing performance degradation due to fault injection, and without using any separate hardware devices. The superior performance of the proposed method is demonstrated through empirical studies applied to fault injection testing of a range of vehicle electronic control unit software.
AB - With recent increases in the amount of software installed in vehicles, the probability of automotive software faults that lead to accidents has also increased. Because automotive software faults can lead to serious accidents or even mortalities, vehicle software design and testing must consider safety a top priority. ISO 26262 recommends fault injection testing as a measure to verify the functional safety of vehicles. However, the standard does not clearly specify when and where faults should be injected, and the tools to support fault injection testing for automotive software are also insufficient. In the present study, we define faults that may occur in Automotive Open System Architecture (AUTOSAR)-based automotive software and propose a fault injection method to be applied during the software development process. The proposed method can inject different types of faults that may occur in AUTOSAR-based automotive software, such as access, asymmetric, and timing errors, while minimizing performance degradation due to fault injection, and without using any separate hardware devices. The superior performance of the proposed method is demonstrated through empirical studies applied to fault injection testing of a range of vehicle electronic control unit software.
KW - AUTOSAR
KW - Fault injection automation
KW - Software fault injection test
UR - http://www.scopus.com/inward/record.url?scp=85085283266&partnerID=8YFLogxK
U2 - 10.3390/electronics9050850
DO - 10.3390/electronics9050850
M3 - Article
AN - SCOPUS:85085283266
SN - 2079-9292
VL - 9
JO - Electronics (Switzerland)
JF - Electronics (Switzerland)
IS - 5
M1 - 0850
ER -