Bug Analysis Report
We have conducted thorough analyses and classification of bugs reported during development and
after release of products. In these analyses we classified bugs according to a taxonomy.
The Bug Return Times Analysis Graphic
Return Bug ID
| Bryan |
Carl |
Toby |
Kelsen |
| 4957 |
9480 |
7655 |
|
| 8856 |
9479 |
8342 |
|
| 8927 |
|
8445 |
|
| 7586 |
|
|
|
| 9412 |
|
|
|
Purpose
The bug return times graphic is intended to analyze the times that bugs are returned and the fix rate of these bugs.
Analysis
With this graphic, PM is able to analyze the fix rate of each developer, and locate the cause of bugs by looking into
Return Bug ID. The cause can be 1: Not familiar with relevant modules; 2. incaution; 3. working efficiency. Besides, the fix rate of the whole team can be calculated, so to forecast the bug amount that can be fixed by the whole team.
Note
Fix Rate = (Fix bugs – Return bugs) / Fix bugs * 100%
The SPEC Return Times Analysis Graphic
Purpose
The SPEC Return Times graphic is intended to analyze the interaction between each SPEC.
Analysis
PM is able to evaluate the quality of each SPEC with this graphic.
Note
Valid Page: the page number of a SPEC without the header and index.
Return times per page = Return times / Valid Page (The small the better)
The Number of Bugs Per Spec
Purpose
The number of bugs per SPEC graphic is intended to analyze the bug amount per SPEC, remaining bug amount up to now, and the average bug amount per page.
Analysis
PM is able to analyze the bug amount per SPEC, the complexity of each SPEC (valid pages of each SPEC), and the quality of the finished SPEC (Bugs per page).
Note
Bugs per page = total bugs / valid pages (the small the better)
The Number of Bugs Per Module
Purpose
The number of bugs per module graphic is intended to analyze the bug amount per module, the cohesion of each module, and the coupling between each module.
Analysis
With this graphic, PM is able to analyze the complexity and difficulty of each module, and evaluate whether this module needs re-factoring.
The Type of Bugs Reported by Customer
Purpose
The bugs reported by tester vs. client graphic is intended to analyze the bug amount reported by the client and the bug amount report by internal testers.
Analysis
PM is able to analyze whether the testing force is sufficient.
The Type of Bugs Reported by Customer
Purpose
The type of bugs reported by customer graphic is intended to classify the bugs reported by the
client and calculate the number of each kind.
Analysis
With this graphic, PM is able to know the modules that the client focuses on during a period of time,
and the type of bugs the client reports. Besides, he can analyze whether the testing force for certain module
is sufficient and find out where can be improved.
The Bugs Converge Tendency Graphic
Purpose
The bugs converge tendency graphic is intended to analyze the change tendency of the bugs per week,
and find out the reason so to forecast the future change tendency.
Analysis
PM is able to analyze the tendency of the Remain Bugs curve and adjust the plan accordingly.
