Presentation is sequential through Part III,
each chapter and part is a prerequisite for all following chapters and parts. Chapters
in Part IV are independent; readers can read one, some, or all in any order. Each
part concludes with a guide to futher reading, an annotated bibliography of pertinent
literature including research papers.
Part I shows what model-based testing and analysis can do; the rest of the book
shows how to do it.
Chapter 1 (this chapter) is a preview of the topics in the rest of the book.
Chapter 2 demonstrates why we need model-based testing.We exhibit a software
defect that is not detected by typical unit tests, but is only exposed by executing
more realistic scenarios that resemble actual application program runs. We preview
our testing techniques and show how they can detect the defect that the unit tests
missed.
Chapter 3 demonstrates why we need model-based analysis.We exhibit a program
with design errors that cause safety violations (where the program reaches forbidden
states), deadlocks (where the program seems to stop running and stops responding to
events), and livelocks (where the program keeps running but can??™t make progress).
We preview our analysis and visualization techniques and show how they can reveal
the design errors, before beginning any testing.
Part II explains modeling, analysis, and testing with finite models that can be
analyzed exhaustively.
Pages:
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41