Systematic Model-Based Testing of Embedded Automotive Software

Conrad, Mirko; Fey, Ines; Sadeghipour, Sadegh

doi:10.1016/j.entcs.2004.12.005

Cited by 31 publications

(15 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Given that this alignment mechanism, together with transformation, was observed most frequently, we can assert that establishing traceability is, in general, a main concern of the studied alignment methods. As shown in the analysis, the between-phase links with a connection type mechanism dominate, mapping for example technical requirements to test scenarios (Case I [Damian et al 2005]), requirements classification trees to logical test scenarios (Case G [Conrad et al 2005]), or test reports to requirements models (Case H [Abbors et al 2009]). This observation concurs with Gotel and Finkelsteins' [1994] definition of requirements traceability referring to "the ability to describe and follow the life of a requirement, in both forwards and backwards direction".…”

Section: Summary Analysismentioning

confidence: 99%

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Requirements Engineering and Software Testing are mature areas and have seen a lot of research. Nevertheless, their interactions have been sparsely explored beyond the concept of traceability. To fill this gap we propose a definition of requirements engineering and software test (REST) alignment, a taxonomy that characterizes the methods linking the respective areas, and a process to assess alignment. The taxonomy can support researchers to identify new opportunities for investigation, as well as practitioners to compare alignment methods and evaluate alignment, or lack thereof. We constructed the REST taxonomy by analyzing alignment methods published in literature, iteratively validating the emerging dimensions. The resulting concept of an information dyad characterizes the exchange of information required for any alignment to take place. We demonstrate use of the taxonomy by applying it on five in-depth cases and illustrate angles of analysis on a set of thirteen alignment methods. In addition we developed an assessment framework (REST-bench), applied it in an industrial assessment, and showed that it, with a low effort, can identify opportunities to improve REST alignment. Although we expect that the taxonomy can be further refined, we believe that the information dyad is a valid and useful construct to understand alignment.

show abstract

Section: Summary Analysismentioning

confidence: 99%

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…Classification Tree method, which is used effectively in traditional software development, was proposed by Conrad to systematically test embedded model-based software [10]. This method requires dividing each input variable range into a set of scenarios (equivalent classes) and carefully selecting one of the test scenarios of inputs to frame a test case for testing a particular requirement.…”

Section: Astmentioning

confidence: 99%

“…Automation has changed the way software is being developed leading to merging of design and coding phases into one phase termed "modeling". Correspondingly, the phases in the model-based software development include specifications, modeling, and testing phases [10]. In modeling, design gradually develops into an executable artifact with different layers of graphical abstractions called models from which highly optimized code is generated automatically using code generators.…”

Section: Introductionmentioning

confidence: 99%

Effective unit-testing in model-based software development

Kamma

Maruthi

2014

Proceedings of the 9th International Workshop on Automation of Software Test

View full text Add to dashboard Cite

Model-based software development is extensively used in avionics and automotive safety critical control software applications. In model-based software development, highly optimized code is generated automatically from models. Such code is often hard to understand and this can make it difficult to write test cases. Therefore, in model based software development, test cases have to be derived based on the models to achieve coverage of code auto-generated from the models. Further, safety standards in those domains often demand effective unit-testing method to check functional requirements as well as achieve 100% code coverage.In this paper, we first discuss three methods for unit testing in model based software development, namely Modified Condition & Decision Coverage (MCDC), Classification tree and Exploratory methods. We then discuss results of our field study conducted on 3 live projects at Robert Bosch Engineering & Business Solutions Limited to check on the effectiveness of three approaches. Based on the results from our field study, we conclude that MCDC method along with boundary value analysis is most productive to check functional requirements as well as achieve 100% coverage of autogenerated code.

show abstract

“…While some studies focus on the concept of test scenarios as a means of managing the requirements of the increasingly complex automotive embedded software, they take a formalized approach to the generation and use of test scenarios like in [5], [112] and [113].…”

Section: Summary Of Previous Workmentioning

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

Systematic Model-Based Testing of Embedded Automotive Software

Cited by 31 publications

References 1 publication

A taxonomy for requirements engineering and software test alignment

A taxonomy for requirements engineering and software test alignment

Effective unit-testing in model-based software development

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

Contact Info

Product

Resources

About