The life-cycle used
here is compatible with that shown in the IEEE
Glossary of Terms.
??? That for planning and management purposes, all activities in a project are broken into work
packages of approximately two person-weeks duration, each with some definable work-product
to be checked and signed off as complete. (This may seem like administrivia. On a well-run project
it is one of the things which makes it a well-run project. In a not-entirely-well-run-project it isn??™t
done, because it would highlight the project??™s deficiencies too clearly.) It??™s worth doing because it
makes you think more clearly about what you??™re trying to do, and if you can??™t plan it, what makes
you think you can do it?
??? That code is developed in units.
??? That the integration of large-scale software is planned as a series of separate steps, each with its
own set of tests. There are development environments which greatly simplify this.
??? That you want a book on test planning and management, not quality assurance, reviews, or
auditing.
??? That you are testing systems of up to 200 KLOC. For such systems the usual method of unit and
system testing applies. Beyond such a size it may be preferable to include a preliminary series of
subsystem integration tests and subsystem tests before the full integration and system tests. This
is because, with very large systems, perhaps some feature may prove extremely problematic when
finally system tested, and it??™s better to find such bugs early.
Pages:
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78