07.01.2013 Views

Lecture Notes in Computer Science 3472

Lecture Notes in Computer Science 3472

Lecture Notes in Computer Science 3472

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Preface<br />

Test<strong>in</strong>g is the primary hardware and software verification technique used by<br />

<strong>in</strong>dustry today. Usually, it is ad hoc, error prone, and very expensive. In recent<br />

years, however, many attempts have been made to develop more sophisticated,<br />

formal test<strong>in</strong>g methods. But a comprehensive account of the area of formal<br />

test<strong>in</strong>g is miss<strong>in</strong>g. The goal of this sem<strong>in</strong>ar volume is to provide an <strong>in</strong>-depth<br />

exposure of this emerg<strong>in</strong>g area, especially to make it easily accessible to new<br />

researchers <strong>in</strong> this field.<br />

S<strong>in</strong>ce test<strong>in</strong>g describes the methodology used to obta<strong>in</strong> better systems, it is<br />

widely used <strong>in</strong> many scientific and <strong>in</strong>dustrial sectors deal<strong>in</strong>g with system development.<br />

As such, a book on test<strong>in</strong>g is hardly ever a comprehensive overview<br />

on the whole doma<strong>in</strong> of test<strong>in</strong>g, but a selection of important approaches and<br />

application doma<strong>in</strong>s. In this volume, we focus on test<strong>in</strong>g methods for reactive<br />

systems. By reactive systems, we understand software and hardware systems<br />

with a (usually) non-term<strong>in</strong>at<strong>in</strong>g behavior that <strong>in</strong>teract through visible events,<br />

such as Web servers, communication protocols, operat<strong>in</strong>g systems, smart cards,<br />

processors, etc.<br />

Furthermore, <strong>in</strong> most chapters of this book, we follow the so-called modelbased<br />

approach. The underly<strong>in</strong>g assumption <strong>in</strong> the model-based approach is the<br />

existence of a precise formal model of the system be<strong>in</strong>g developed. This model<br />

can be used for study<strong>in</strong>g the system to be. Especially <strong>in</strong> the test<strong>in</strong>g phase of<br />

product development, it can be used to generate complete test suites to show<br />

conformance of the model and the actual implementation, or, just to derive<br />

“<strong>in</strong>terest<strong>in</strong>g” test cases to check the developed system.<br />

The 19 chapters of the book are grouped <strong>in</strong>to six parts. In the first part, we<br />

present the approaches for test<strong>in</strong>g for f<strong>in</strong>ite-state mach<strong>in</strong>es, also called Mealy<br />

mach<strong>in</strong>es. The second part, called test<strong>in</strong>g of labeled transition systems, givesan<br />

overview of the test<strong>in</strong>g theory due to Hennessy and De Nicola together with its<br />

extensions to I/O, timed, and probabilistic systems. In Part III, we focus on<br />

methodology, algorithms, and techniques for model-based test case generation.<br />

The methods illustrated <strong>in</strong> the first three parts of the book led to the development<br />

of test tools and have been applied <strong>in</strong> many case studies show<strong>in</strong>g<br />

their advantages and drawbacks. Several tools and case studies are presented <strong>in</strong><br />

Part IV.<br />

While test case generation can be considered the heart of test<strong>in</strong>g, the test<strong>in</strong>g<br />

process as a whole is more complicated. The test cases have to executed on the<br />

system under test. In several application doma<strong>in</strong>s, test suites are used to show<br />

conformance to a standard. For this, test cases have to be <strong>in</strong>terchanged among<br />

developers. Furthermore, test<strong>in</strong>g should be <strong>in</strong>cluded <strong>in</strong> the overall development<br />

process. In Part V, called Standardized Test Notation and Execution Architecture<br />

we cover recent developments.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!