FAT-AES: Systematic Methodology of Functional Testing for Automotive Embedded Software

Abstract

Road vehicles have incorporated several functionalities over the last decade, with an increasing incorporation of electronic embedded systems. Most of those functionalities are controlled, managed, and supervised by distributed software, within many interconnected Electronic Control Units (ECUs). Within such context, new methodologies for tests of the distributed software functions must be developed to ensure proper performance at the integration level, complying with the requirement specifications. Many strategies have emerged to organize the multiple levels of software testing in automotive embedded systems, to reduce costs and improve its effectiveness and robustness, but there is a need for a methodology to structure, optimize, and plan the tests with real automotive criteria. This work aims to extend the multiple levels of testing concept and propose a method to analyze, design, and evaluate the application system upfront to derive a software testing plan. This method has been developed incorporating the automotive application characteristics, including functional safety requirements specified in the ISO 26262 standard to structure and plan the embedded software test in vehicle development. The proposed method combines an enhancement on plan testing strategy, matching requirement specifications, with adherence to the current methods used in practice by the automotive industry. Such a process will help the automotive industry to follow some concrete steps during validation, to optimize the test volume and facilitate documentation of developed activities, improving the safety and security of automotive systems in the early stages of automotive embedded software, when the details of each function are not yet implemented at the component level.

Integration and Implementation of Scaled Agile Framework and V-Model in the Healthcare Sector Organization

“…Therefore, the authors refer to integrating the V-model and modern quality tools, where the Voice of the Customer is considered [18]. In practice, this should mean that software has become part of functionality and innovation in various areas, from telecommunications and medical devices to automotive systems [22,23].…”

“…The V-model has been widely used in automotive development, in particular from state-of-the-art analysis, mainly in software development such as safety-critical systems [9,11,22,[33][34][35][36], car rental applications [10], and driving range estimation software for electric vehicles [9,37], an automatic framework for the design of Gateway [38], and according to the proposed data-based V-Model, present a solution for the development cycle of AI components [39,40].…”

The evolution of embedded systems in automotive industry: A global review

“…The automotive industry's increasing focus on safety and security has led to the implementation of systematic methodologies for functional testing of automotive embedded software (Hodel et al, 2022). Moreover, there has been a growing emphasis on simulation-based testing and inspection of engine control units during the manufacturing phase, contributing to the overall quality and reliability of automotive embedded systems (Ham et al, 2017).…”

“…The rapid evolution of automotive embedded systems has necessitated flexible system architectures to accommodate future changes (Zhang et al, 2017). This is particularly important as road vehicles have incorporated several functionalities over the last decade, with an increasing incorporation of electronic embedded systems (Hodel et al, 2022). The state-of-the-art design strategies and upcoming hardware/software solutions for the next generation of automotive systems, with a special focus on embedded and networked technologies, have been comprehensively reviewed, highlighting the need for further research in this area to address emerging issues and ensure sustainable growth of the automotive industry (Bello et al, 2019).…”

GUI-Based Data Visualisation Tool for Option C IPMVP using Jupyter Notebook

“…Validation determines if the proposed program tool fits the criteria, whereas verification determines the system's compatibility with the user's needs and expectations as recommended by the IEEE 1012 standard [12]. Klebar et al [13] approved that V-model is one of the comprehensive testing tools in their development. The model validated their automotive OEM embedded system.…”