4.
Your implementation need not provide any user interface, just provide an API
with a method for each action. Describe how you implemented the enabling
conditions, and explain your rationale.
2. Write and execute unit tests for your implementation that execute the runs
simulated in Section 5.5. How does your implementation handle the second run,
where the last action is not enabled?
3. Create a version of your newsreader implementation that contains a defect in
(your implementation of) an enabling condition. Write a unit test that exposes
the defect.
4. Create a version of your newsreader implementation that contains a defect in
(your implementation of) an action method. Write a unit test that exposes the
defect.
5. Revise the reactive system model program of Section 5.7 to correct the design
errors. This version should have no unsafe states and no dead states. In other
words, model the implementation you wrote in Chapter 3, Exercise 3. Hint: use
the design rules given in Section 3.6.
Save the programs you wrote for these exercises to use in exercises in chapters
to come.
6 Exploring and
Analyzing Finite
Model Programs
In this chapter we introduce exploration, our primary technique for analyzing model
programs. Exploration generates a finite state machine (FSM) from a model program.
The FSM can then be used for visualization, analysis, and offline test generation.
Pages:
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142