Calculate the bug detection effectiveness as shown in Figure 7.10.
TABLE 7.1 Where the bugs spring from
Count of features affected Severity
Feature affected Created in activity Critical High Medium Low
AE: Coding Coding 12 11 2
Design 1 7 2 1
Requirements definition 1 4
AE: Create/Save/ Delete Coding 5 5 3
Design 7 16 1 4
Requirements definition 2 1 1
AE: Display Coding 2 2
Design 2 4 1 3
AE: Menu Coding 1 4
Design 1 1 4
Requirements definition 1 1
FIGURE 7.10 Quality gate effectiveness
Quality gate e?¬?ectiveness = Phase total
quality gate total ??“ previous phase totals
Quality gates reached
?— 100% ??
Testing Processes and Infrastructure 109
7.6.6 Bug Detection and Injection Analysis
At some point the question will be asked: ???how good are we at finding bugs in the same phase in which
we fix them???? Table 7.3 shows an answer for one project. Each cell in the Bug Detection (%) column is
calculated using the data from the Phase Total column of Table 7.2. Every cell in the Bug Injection (%)
column is calculated using the data from the Quality gate total of Table 7.2. From this table it is evident
that the review process is weakest at the coding stage with no review of the documentation occurring at
all. System testing only finds 25% of the bugs and many management initiatives are urgently required.
7.7 Operational Profiles
An operational profile is a quantified characterization of how a system will be used.
Pages:
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277