FIGURE 4.9 Executable UML (xUML) process model C
B
PIM/PSM mapping
rules
PIM/PSM compiler
updated
PSM source
Target build
Define PIM to PSM
mapping rules
Incorporate PIM/PSM
mapping rules into
PIM compiler
Create a platformspecific
model
Compile the environmentspecific
code
System-test the executable
on the target.
Stop
PSM tests
Tested PIMS
Implementation
domain details
Domain charts,
and dependencies
Middleware details
54 Manage Software Testing
2. The approach excludes all GUI design issues.
3. Algorithm-proving is assumed to occur separately.
See [Atkinson] and [Raistrick] for an overview.
At least 3 toolsets (Virtual Engineering Environments or VEEs) for executable UML were available as
at October 2005:
1. Kabira Technologies (www.kabira.com) ??” ObjectSwitch.
2. Project Technologies (www.projtech.com) ??” BridgePoint.
3. Kennedy-Carter (www.kc.com) ??” UML/xUML.
The dangers for system testing are:
1. The potential for losing sight of the user requirements (as opposed to the design) since these are
neatly embedded in the models.
2. The ease with which the model can be changed such that a system test baseline can change without
system testers realizing it.
3. Few existing automated test tools will interface to the system.
The modeling approach, with its emphasis on early testing, means that many quality problems will
already have been dealt with beforehand.
4.4.9 Formal Methods
Formal Methods (FM) are the use of techniques of formal logic and discrete mathematics in the speci-
fication, design, and construction of computer systems and software.
Pages:
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179