Model-Based Testing of Highly Configurable Embedded Systems

Model-Based Testing of Highly Configurable Embedded Systems

Detlef Streitferdt (Technische Universität Ilmenau, Germany), Florian Kantz (ABB Corporate Research, Germany), Philipp Nenninger (ABB Automation Products, Germany), Thomas Ruschival (Datacom Telematica, Brazil), Holger Kaul (ABB Corporate Research, Germany), Thomas Bauer (Fraunhofer IESE, Germany), Tanvir Hussain (The Mathworks GmbH, Germany) and Robert Eschbach (ITK Engineering AG, Germany)
DOI: 10.4018/978-1-4666-6034-2.ch010
OnDemand PDF Download:
$37.50

Abstract

This chapter reports the results of a cycle computer case study and a previously conducted industrial case study from the automation domain. The key result is a model-based testing process for highly configurable embedded systems. The initial version of the testing process was built upon parameterizeable systems. The cycle computer case study adds the configuration using the product line concept and a feature model to store the parameterizable data. Thus, parameters and their constraints can be managed in a very structured way. Escalating demand for flexibility has made modern embedded software systems highly adjustable. This configurability is often realized through parameters and a highly configurable system possesses a handful of those. Small changes in parameter values can often account for significant changes in the system's behavior, whereas in some other cases, changed parameters may not result in any perceivable reaction. The case studies address the challenge of applying model-based testing to configurable embedded software systems in order to reduce development effort. As a result of the case studies, a model-based testing process was developed. This process integrates existing model-based testing methods and tools such as combinatorial design and constraint processing as well as the product line engineering approach. The testing process was applied as part of the case studies and analyzed in terms of its actual saving potentials, which turned out to reduce the testing effort by more than a third.
Chapter Preview
Top

Example Case Studies

The following two case studies have been elaborated subsequently. In the first industrial case study, the softstarter, a single system testing process was developed.

Based on this testing process the second case study a cycle computer has been developed in a University environment and resulted in an enhanced testing process with product line support. This case study covers multiple domains (computer science, electrical engineering, mechanical engineering) for the best possible learning curve of the future software engineers. These learning demands are a direct result of the initial softstarter case study. Secondly, the cycle computer is a multi-platform project. Many operating systems, different languages and different hardware platforms are in use.

Complete Chapter List

Search this Book:
Reset