Lecture Notes in Computer Science 3472

15 Case Studies
Wolfgang Prenninger 1 , Mohammad El-Ramly 2 , and Marc Horstmann 3
1 Institut für Informatik
Technische Universität München
prenning@in.tum.de
2 Department of Computer Science
University of Leicester, UK
mer14@le.ac.uk
3 Institut für Verkehrssicherheit und Automatisierungstechnik
Technische Universität Braunschweig
m.horstmann@tu-bs.de
15.1 Introduction
In this chapter, we review and analyze some of the significant case studies published
on the application of model-based testing. We focus on case studies done
in industrial contexts in order to evaluate how model-based testing is applied in
practice and how far it is applied. But we also review a few proof of concept and
benchmarking case studies. We review case studies on model-based testing of
processors [DBG01, SA99, FKL99], smart cards [PPS + 03,CJRZ01],protocols
[KVZ98, BFdV + 99], Java and POSIX [FHP02]. This list is not exhaustive; but it
is a good representation of the range of applications, methods and tools used in
the available model-based testing case studies. There could be other case studies
which we did not detect or have been published recently.
We shall observe that all case studies follow a similar process for model-based
testing. Thus, we structure the chapter as follows: Sec. 15.2 gives the big picture
and provides a fast overview of the abstract model-based testing process which
all case studies have in common. Sec. 15.3 describes the different application
domains and their characteristics where model-based testing has been applied.
Sec. 15.4 through Sec. 15.8 document in detail which techniques and methodologies
are used by the different approaches to instantiate the different phases
of the abstract process. Sec. 15.9 summarizes and concludes this chapter.
For technical foundation about test case generation we refer to Chap. 11 and
12. For a thorough overview about test generation tools we refer to Chap. 14.
15.2 The Abstract Process
By studying the reviewed case studies listed in Sec. 15.1 and described in Sec. 15.3
we observe that the underlying process is very similar. All case studies start with
an abstract formal test model which is derived either (semi-)automatically out of
system development models or manually out of the systems requirements specification.
In the later case, manual validation of the test model against system
requirements specification should be done first in order to find possible errors
M. Broy et al. (Eds.): Model-Based Testing of Reactive Systems, LNCS 3472, pp. 439-461, 2005.
© Springer-Verlag Berlin Heidelberg 2005