A Component-Based Process for Developing Automotive ECU Software

Her, Jin Sun; Choi, Si Won; Cheun, Du Wan; Bae, Jeong Seop; Kim, Soo Dong

doi:10.1007/978-3-540-73460-4_31

Cited by 6 publications

(6 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This section discusses studies P8 [40], P220 [54], P279 [57], P332 [63], P365 [65], P468 [68], P493 [69], P580 [71], P588 [72], P589 [73], E127 [79], and E230 [90], which were assigned to the (general) variability management category. Managing the variability within a software product line constitutes a challenging task and is addressed by nearly one third of the studies from the result set.…”

Section: Variability Managementmentioning

confidence: 99%

“…Jin Sun et al [40] propose a component-based development process based on variability types. They identify several variability types that may occur in ECU-related development: variability of software components, variability of logic components, variability of sensor components, variability of actuator components, variability of setpoint generator components, variability of output device components, and variability of component interfaces.…”

Section: Variability Managementmentioning

confidence: 99%

See 1 more Smart Citation

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

et al. 2022

View full text Add to dashboard Cite

The rapidly growing number of software-based features in the automotive domain as well as the special requirements in this domain ask for dedicated engineering approaches, models, and processes. Nowadays, software development in the automotive sector is generally developed as product line development, in which major parts of the software are kept adaptable in order to enable reusability of the software in different vehicle variants. In addition, reuse also plays an important role in the development of new vehicle generations in order to reduce development costs. Today, a high number of methods and techniques exist to support the product line driven development of software in the automotive sector. However, these approaches generally consider only partial aspects of development. In this paper, we present an in-depth literature study based on a conceptual model of artifacts and activities for the managed evolution of automotive software product line architectures. We are interested in the coverage of the particular aspects of the conceptual model and, thus, the fields covered in current research and research gaps, respectively. Furthermore, we aim to identify the methods and techniques used to implement automotive software product lines in general, and their usage scope in particular. As a result, this in-depth review reveals that none of the studies represent a holistic approach for the managed evolution of automotive software product lines. In addition, approaches from agile software development are of growing interest in this field.

show abstract

Section: Variability Managementmentioning

confidence: 99%

Section: Variability Managementmentioning

confidence: 99%

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

et al. 2022

View full text Add to dashboard Cite

show abstract

“…The application of the ABSRM selection method is carried out on an automotive Automatic Parking System (APS). According to the models described in [14], [19], the main function of the software components in an APS is to find the optimal path for parking by measuring the distance between the car and its surrounding objects, and to drive the car automatically without the driver's intervention.…”

Section: An Applicationmentioning

confidence: 99%

A Method for Selecting a Model to Estimate Software Reliability at the Design Phase of Component-Based Real-Time System Development

Garg¹

2018

JSW

View full text Add to dashboard Cite

The rapid growth of software-based functionalities has not only increased the complexity of Component-Based Real-Time Systems (CBRTS) but also made it difficult for designers to quantify its reliability. Architecture-Based Software Reliability Models (ABSRMs) are useful for estimating the architectural reliability of component-based systems so that the behavior of its software components can be examined at different development phases. However, due to the availability of a number of models spread over different ABSRM categories, it is difficult to know which one is suitable for a particular system. Traditional model selection methods have two limitations: (i) they can only be applied to identify a model from a specific ABSRM category; and (ii) they omit a well-defined and verified mechanism to identify the ABSRMs which are capable of addressing the reliability requirements at an early development phase. Reliability estimation at the design phase enables developers to analyze the impact of the software component's reliability and its interactions on a CBRTS, study the sensitivity of CBRTS reliability to the reliabilities of its software components and interfaces and guide the process of identifying potential troublesome software components which require more attention during the integration exercises. In this paper, we describe a method for selecting an ABSRM to estimate software reliability at the design phase of a CBRTS development. To demonstrate the usefulness of our proposed method, we apply it to an automotive Automatic Parking System.

show abstract

“…The ECU systems interact in order to execute the desired functionality in the vehicle like controlling the engine, displaying fuel level and operating air bags [9]. In the past, each single ECU system in the vehicle had a single dedicated function.…”

Section: Problem Statementmentioning

confidence: 99%

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

A Component-Based Process for Developing Automotive ECU Software

Cited by 6 publications

References 7 publications

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

Managed Evolution of Automotive Software Product Line Architectures: A Systematic Literature Study

A Method for Selecting a Model to Estimate Software Reliability at the Design Phase of Component-Based Real-Time System Development

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

Contact Info

Product

Resources

About