It helps to ensure
that the most-used features of the system are tested and is of great value when testing high-traffic systems.
It is also valuable for determining:
TABLE 7.2 Where the bugs were caught
Phase/quality gate Requirements Design Coding Documentation
Phase
total
Detection
effectiveness
(%)
Requirements review 39 39 60
Architecture design review 10 33 43 32
Code review 5 55 70 130 50
System test 8 12 66 10 96 59
Deployment 2 6 33 25 66
Quality gate total 64 106 169 35 374
TABLE 7.3 Where the bugs were created and caught
Phase
Bug detection
(%)
Bug injection
(%)
Requirements 10 17
Design 11 28
Coding 34 45
Documentation 9
System test 25
Total 80 100
FIGURE 7.11 Bug detection effectiveness
FIGURE 7.12 Bug injection
Bug detection % = 100 ?— Phase total
Total bugs
Bug injection% = 100 ?— Quality gate total
Total bugs
110 Manage Software Testing
??? Which functions are the least-likely to be used. If any of these are safety or mission-critical (for
example a nuclear shut-down routine) then we can identify these as high-risk/low-use components
for special testing.
??? Which features to build first (because it is easy to see which will be the most-heavily-used).
??? Early that the system has too many operations to be testable (because the combination of operations
will be very high and it is in the combinations that the worst bugs hide), and thus influence
design decisions.
A profile consists of a set of disjoint alternatives (only one can occur at a time) with the probability that each
will occur.
Pages:
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278