Effective test strategy for testing automotive software

Barhate, Sujit Sopan

doi:10.1109/iic.2015.7150821

Cited by 17 publications

(11 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Hence, a complete and thorough testing of automotive embedded software is essential. A single fault could potentially cause devastating consequences [12]. As a result, about 50% of the total time spent on management and technical activities of automotive development is dedicated to software testing [13].…”

Section: Problem Statementmentioning

confidence: 99%

“…Motivation: One accepted and widespread approach to report the efforts of verifying a software function for various input combinations is using test coverage information based on a suitable coverage metric like requirementsbased test coverage or code-based test coverage [12]. Identifying the current test coverage information for the distributed software functions across different test levels helps establish how much has been tested.…”

Section: Rq2mentioning

confidence: 99%

“…Exhaustive integration testing of the distributed functions at the vehicle integration test level using the numerous variants across the modules would be an excellent means of ensuring defect-free software. However, it is not feasible since projects within the automotive industry neither have infinite resources nor have the time to carry out such exhaustive testing [12]. On the other hand, going by the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience and expertise can lead to test gaps and test redundancies across the different test levels [16].…”

Section: Chapter 1 Introductionmentioning

confidence: 99%

“…Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions at the vehicle integration test level that would help achieve adequate test coverage while reducing test redundancies and test gaps across the test levels. There is limited scientific literature in the context of automotive industry, like [12], found to be focusing on solving this challenge.…”

Section: Chapter 1 Introductionmentioning

confidence: 99%

“…These challenges have a potential to lead to undesirable consequences. Yet, research focusing on addressing this problem domain, like [12], has been found to be limited. Therefore, there is a need from within and outside the automotive industry for a verification strategy that can help focus on improving the effectiveness of integration testing of the distributed software functions.…”

Section: Chapter 1 Introductionmentioning

confidence: 99%

See 4 more Smart Citations

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Context. The share and importance of software within automotive vehicles is growing steadily. Most functionalities in modern vehicles, especially safety related functions like advanced emergency braking, are controlled by software. A complex and common phenomenon in today's automotive vehicles is the distribution of such software functions across several Electronic Control Units (ECUs) and consequently across several ECU system software modules. As a result, integration testing of these distributed software functions has been found to be a challenge. The automotive industry neither has infinite resources, nor has the time to carry out exhaustive testing of these functions. On the other hand, the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience, can lead to test gaps and test redundancies. Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions. Objectives. Firstly, to identify the current approach used to test the distributed automotive embedded software functions in literature and in a case company. Secondly, propose and validate a feasible and effective verification strategy for testing the distributed software functions that would help improve test coverage while reducing test redundancies and test gaps. Methods. To accomplish the objectives, a case study was conducted at Scania CV AB, Södertälje, Sweden. One of the data collection methods was through conducting interviews of different employees involved in the software testing activities. Based on the research objectives, an interview questionnaire with open-ended and close-ended questions has been used. Apart from interviews, data from relevant artifacts in databases and archived documents has been used to achieve data triangulation. Moreover, to further strengthen the validity of the results obtained, adequate literature support has been presented throughout. Towards the end, a verification strategy has been proposed and validated using existing historical data at Scania. Conclusions. The proposed verification strategy to test distributed automotive embedded software functions has given promising results by providing means to identify test gaps and test redundancies. It helps establish an effective and feasible approach to capture function test coverage information that helps enhance the effectiveness of integration testing of the distributed software functions.

show abstract

Section: Problem Statementmentioning

confidence: 99%

Section: Rq2mentioning

confidence: 99%

Section: Chapter 1 Introductionmentioning

confidence: 99%

Section: Chapter 1 Introductionmentioning

confidence: 99%

Section: Chapter 1 Introductionmentioning

confidence: 99%

See 3 more Smart Citations

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

show abstract

Application of rule‐based expert systems in hardware‐in‐the‐loop simulation case study: Software and performance validation of an engine electronic control unit

Ortega‐Cabezas

Colmenar‐Santos

Borge-Díez

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Innovative techniques to validate software are needed to reduce cost and increase software quality.This research aims to check if two rule‐based expert systems (EXs) combined with dynamic‐link libraries (dlls) perform better than other techniques widely employed in the automotive sector when validating the engine electronic control unit (ECU) software by using a hardware‐in‐the‐loop (HIL) simulation.To perform this research, 15 software modules (SMs) of different complexities were chosen to be validated in an HIL simulation by using different techniques such as the manual execution, the tester‐in‐the‐loop, the model‐based testing, a rule‐based EX, and the combination of two EXs to establish the code and functional coverage, the productivity gain, the number of bugs found, potential limitations of each technique, and the success rate of the HIL simulation. The test cases used are described in‐depth in Section 2.The enhancement, which dlls and EXs offer, depends on the number of states in the functional model used in the EXs and the number of subintervals in which the SM inputs can be divided. A range between 6 and 16 more bugs can be detected when using two EXs. The HIL enhancement can reach 6%, 16.8%, and 18% depending on the SM complexity.

show abstract