Knowledge and skills requirements for the software design and testing of automotive applications Jernej Zabavnik, Andreas Riel, M. Marguč, Miran Rodič To cite this version: Jernej Zabavnik, Andreas Riel, M. Marguč, Miran Rodič. Knowledge and skills requirements for the software design and testing of automotive applications. SAAEI 2019, Jul 2019, Cordoba, Spain. hal-02335566 HAL Id: hal-02335566 https://hal.archives-ouvertes.fr/hal-02335566 Submitted on 28 Oct 2019 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. > REPLACE THIS LINE WITH YOUR PAPERLIBRO IDENTIFICATION DE ACTAS - NUMBERSAAEI 2019 (DOUBLE-CLICK HERE TO EDIT) < 1 Knowledge and skills requirements for the software design and testing of automotive applications J. Zabavnik, A. Riel, M. Marguč, M. Rodič software development process is upgraded with the processes Abstract— The required knowledge and skills that should be and methods prescribed in IEC/ISO 26262 [2], the functional provided to the novice developer, designing and testing the safety safety standard for the electrical, electronic and programmable critical device in automotive industry using Hardware-in-the- electronic devices in road vehicles. Automotive SPICE and Loop (HiL), are presented in the paper. They should be available to the student finishing the MSc level of Electrical Engineering or IEC/ISO 26262 thus represent the most important documents in Mechatronics that aims to seek the employment in the automotive automotive industry to comply with the Quality Management industry. The development process is presented in short, together and Functional Safety assessment. The risk classification with the brief explanations of phases, which include some typical scheme defined in the IEC/ISO 26262 is called Automotive examples of written text in the documentation (requirements, test Safety Integrity Level (ASIL) and is used to rate hazards of the cases, etc.). The process follows the Automotive SPICE and focuses system based on the consideration of malfunctions in particular on the tip of the V-model. The presented text can serve as a useful driving situations. information in the process of adapting the existing curriculum to the new occurring needs introduced by the new development and To verify the applied system, architecture, software and testing processes in industry. hardware, testing is an essential tool. It is used in order to determine whether the objectives set are met. Testing is Index Terms— software engineering, requirements, Hardware- performed based on the requirements, where the most important in-the-Loop, testing, automotive upgrade introduced by the IEC/ISO 26262 is the introduction of the testing of functional safety objectives. For this purpose, the ISO/IEC does not only specify the requirements regarding the I. INTRODUCTION processes, but also prescribes the methods which shall be N the modern vehicles there is a growing number of electric, applied. I electronic and programmed electronic devices. This is not Among the methods required by IEC/ISO 26262, the only the case for the main drive (drivetrain), but also for a big Hardware-in-the-Loop (HiL) testing has become indispensable number of auxiliary devices. In many cases previously in the automotive domain [8]. It represents the method where mechanic or hydraulic devices are being replaced with the the device under test is placed in an emulated environment. The electric ones. For many such devices (so-called safety critical basic principle of the method is presented in the Figure 1. devices), failures could result in serious, even fatal, injuries of the passenger in the vehicle. These failures must be avoided as far as possible at reasonable cost and in a way sustainable for the producer of the vehicle. Tested Using extremely reliable devices would in many cases result in a very high cost of the final product, making it unaffordable component for the customer. The solution is therefore to develop in such a way, that the devices remain safe even in the case of their failure, i.e., to achieve functional safety of the device and as a result also vehicle. Failures shall be avoided, however if this is not possible, their effects have to be mitigated. This goal can be HIL simulator achieved with the use of fault-tolerant devices developed according to the proper development cycle. Figure 1:HIL testing basic principle The development cycle in the automotive industry is based on the classical V-model, where the development from the user requirements to the validation of the product is described. In With the use of HiL, systems testing can be performed under automotive industry processes are specified in compliance with close-to-real conditions. It is also important to note, that the the Automotive SPICE standard [1]. Both the system and repeatability of tests is assured, and the same testing hardware 373 > REPLACE THIS LINE WITH YOUR PAPERLIBRO IDENTIFICATION DE ACTAS - NUMBERSAAEI 2019 (DOUBLE-CLICK HERE TO EDIT) < 2 can be re-used for tests of various devices with only limited backbone of both Automotive SPICE and the ISO 26262. An modifications. Since the device under test is available in real essential property is the bidirectional traceability between during testing, and no understanding of its internal design is process steps on the left-hand side of the V, as well as between therefore required, HiL testing is a form of black-box testing. related process steps on the left and right-hand side of the V. Black-box testing can be performed for testing of units, While the left-hand side covers requirements engineering and integration testing, system testing and up to the certain level, design from system level to software (SW) unit level, the right- even system validation. The testing processes as described hand side is dedicated to verification and validation in the form above have been widely accepted in the automotive industry. of tests from SW unit level up to system level. In the following They represent a must for any company wishing to be a part of we will briefly describe every process step on the left-hand side the automotive development process or supply chain. It has of the V. been observed, however, that there is a serious lack of engineers familiar with these processes and methods, and consequently many companies, especially smaller ones, experience serious difficulties in adopting them. Definitely the knowledge in this field will be required from the future employees and therefore it is important that teaching it becomes a part of the education process, especially at higher education levels. This is especially important for the students of Electrical Engineering and Mechatronics. The requirements for new topics and the extension of the existing ones to the education process will be presented in the following text. There have already been extensive activities in the field of adapting university curricula accordingly, in particular the Automotive Universities project [7], however those have to be extended by the testing methods, especially HiL-related ones. Figure 2:V-model design (ASPICE) This paper is organized as follows. After the introduction first the design process in the automotive industry is presented Stakeholder Requirements are (internal or external) customer in more details. The V-model is described together with its requirements describing what the system shall do and how the activities. The testing in the automotive industry is described system shall perform. The stakeholder requirements documents next. The main approaches, methods and processes are are analyzed with respect to the feasibility, risk and priority of presented. Based on this explanation some knowledge and skills requirements. required for the HiL testing are proposed. To visualize the System Requirements – In the system design phase, engineers problem and propose a methodology of teaching, an example of technically analyze the stakeholder requirements documents testing is proposed. In the final section, the conclusion is given and derive company-internal system requirements from them. to summarize the most important topics required in the future Each stakeholder requirement shall lead to at least one atomic education. (i.e., indivisible) system requirement. The System Architectural Design maps the system II. DESIGN PROCESSES IN AUTOMOTIVE INDUSTRY requirements to system components (mechanics, electronic hardware or software) and their interfaces. At this stage, the Automotive SPICE and the IEC/ISO 26262 provide the architectural design is still a high-level black-box design frameworks for development processes of embedded specifying the main system components and their automotive systems. In the following we will briefly describe interconnections via clearly defined interfaces. the essentials of both these standards. Software Requirements Analysis leads to requirements to A. Automotive SPICE software related parts derived from system requirements. The Automotive SPICE is based on the SPICE – ISO/IEC15504 System Architectural design shall be used to better