12).
??? The test manager:
??“ Identifies the known weaknesses and feeds details back to all testers.
??“ Monitors the degree of coverage, robustness, and execution history of all automated tests (if
testers ever get much ???behind the curve??? it will severely delay release since system testing will
uncover even more bugs).
??“ Ensures that testers (mostly) have the tools and training they need.
??“ Ensures that automated feature-interaction tests are prepared.
??“ Reviews automated tests.
??“ Monitors the degree of coverage of test suppliers.
If the management attempt to emulate the Microsoft approach to develop products of comparable
size to Microsoft??™s (c. 170 KLOC)
without
the right staffing ratios, approach, or time, chaos will
ensue. Note that:
??“ The best view of the system??™s functions lies in the system tests.
??“ Netscape attempted a similar approach but used three developers per tester, and had no buffer
time or daily tests. It lost the browser war by being too slow delivering and too slow in
performance.
See [Cusumano 1] and [Cusumano 2] for more on this. Note that the Microsoft Solutions Framework
(a near clone of SSADM) does not appear to be used by Microsoft Product Groups. Mention of it
provoked wry grins when mentioned to some senior staff working on Word.
4.4.7 (Rational) Unified Process
This consists of four phases:
1. Inception in which the business case is established
2. Elaboration in which the scope of the system is defined, risks are identified and resolved, and the
architecture designed
3.
Pages:
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172