Construction in which the low-level elements of the system are coded or designed, and minor
releases each containing an increment of the system??™s features
4. Transition in which a beta release is made and system-tested.
The phases correspond to a number of models, several of which can be baselines for system and unit
testing (Figure 4.4). These models are supported by a number of diagramming techniques. The solid
lines in Figure 4.5 indicate required diagrams and the dotted lines indicate optional ones. The test phase
exploits primarily the Class diagrams but may also use Component and Deployment diagrams. Sequence
diagrams have had timing constructs attached as shown in [
UML
TP].
Test Planning and Management
49
It is quite possible to get the data required from
UML
diagrams for the purpose of system testing (see
section 8.2.1). However unit
test cases
cannot be so simply designed from an
UML
model, and are
probably best derived using a tool such as xUnit or its equivalent.
The UP approach has the following dangers:
??? Baseline maintenance: because you are not allowed to
decompose
in
UML
the possibility of
inconsistency is considerable.
??? Baseline definition: you need to look at several models to check what is your baseline.
??? Sloppiness: the approach is as rigorous as users make it. If used well you will have a lot of support,
and test development will be greatly simplified. Otherwise??¦
4.
Pages:
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173