??“ Creating target system test scripts (which will be collections of those above).
??“ Creating stubs and test methods to exercise those stubs, through the simulator during preliminary
integration attempts, using unfinished domains. This will normally be the responsibility
of programmers.
Code-level bugs and initial conditions for model execution can be injected using the ASL code.
Note that the test method creation facility, while mostly designed for developer use, can also
be used to create domain-level test environments.
FIGURE 4.6
The ???Display Options??? point of the ???Withdraw Cash??? use case
Buttons Screen
Withdraw
cash
Display
balance
Print
balance
Order check
book
Card slot
Receipt slot
Cash slot
8
7
6
5
4
3
2
1
52
Manage Software Testing
Look for ???cannot-happen??? effects in the code. These indicate illegal events which should be
thrown up by a simulation.
8. Compile and debug a PIM using a
Virtual Execution Environment
(VEE). (This may also involve
preliminary timing tests which will be performed by programmers.)
FIGURE 4.7
Executable
UML
(x
UML) process model A
FIGURE 4.8 Executable UML (xUML) process model B
Legacy code
State charts, state
tables, and class
collaboration
diagrams Label
A
ASL code
Class models
Domain charts,
and dependencies
Use cases and
sequence diagrams
Primary use
case set
Stakeholder list
Project vision
document
Define action behavior
Create static models
Create dynamic models
Create use cases
Specify new and reusable
domains
Start
Identify requirements
Test PIMs by executing use
cases on sets of domains
Test PIMs by executing use
cases on each domain
Create PIM/PSI tests
Compile and debug PIMs
Simulator
B
A
Class
collaboration diagrams
ASL code
Domain contracts
(bridges)
Tested PIMS
PSM tests
PIM tests
Untested PIMs
Use cases and
sequence diagrams
Domain contracts
(bridges)
Untested PIMs
Identify domain??“domain
interfaces
Test Planning and Management 53
9.
Pages:
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177