The
set of steps is called an integration tree. An example is shown below.
In the first place let us imagine that some software to handle a raster display controller is being developed
to work as shown in Figure 8.10.
An HOOD (top-level design) diagram is later produced as shown in Figure 8.11.
The software items which constitute the raster display controller can be read off the high-level design
and onto an Integration tree as shown in Figure 8.12.
The key to Figure 8.12 is shown in Figure 8.13.
FIGURE 8.9 Boilerplate test plan specification of handover meeting and release note contents
FIGURE 8.10 The raster display controller block diagram
Handover meeting
Handover from Developers to system testing, or from system test to some other group will take the following form:
??? Review the (UAT/system test/Desktop/Server) environment requirements (if unusual)
??? Review the release note
??? Install the software
??? Demonstrate that 90% of all new features are present.
Release note contents
The Release note will show:
??? Release name, pre-requisites, and release environment.
??? bugs ?¬?xed and outstanding
??? Features allegedly present (as de?¬?ned by a functional speci?¬?cation, or sub-set thereof).
??? Pathnames of ancillary documentation.
Raster display
controller
Cockpit
?µprocessor
board
1553 databus
140 Manage Software Testing
Figure 8.12 shows an extremely cautious integration strategy, split into 5 steps.
Pages:
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321