|
|
|
|
|
|
|
|
|
MSF for CMMI Process Improvement > Wiki Pages > Activity - Locate Cause of Bug
|
Activity - Locate Cause of Bug
|
|
|
|
|
|
Activity Information Locate Cause of Bug
DescriptionWhen a bug work item is created and reproducible, the developer must find the cause of the bug. The developer can employ a number of tactics and tools to find the root cause of the bug. The strategy to fix the bug often becomes more apparent while locating the cause. Use development tools and resources such as event logs, a debugger, analysis of the code, or traces to pinpoint the cause of the bug. Once the cause is determined, document it in the bug work item. Attributes| Element Categories | [CMMI Level 3] VER SP 3.2, [CMMI Cycle 1] Check In, [CMMI Track 3] Build, [CMMI Track 4] Stabilize, [CMMI Level 5] CAR SP 1.2 | | Guidance | How to: Reassign a Bug | | Entry Criteria | The bug is assigned to a developer and the same developer is locating the bug:
The bug is assigned to a developer and the same developer is locating the bug.
The test configuration is the same one used when the bug was found:
The test configuration is the same one used when the bug was found.
Up-to-date source code must be available:
Up-to-date source code must be available. | | Exit Criteria | There is enough information from the identified bug location to develop a fix:
There is enough information from the identified bug location to develop a fix.
The cause and location of the bug is documented in the bug work item:
The cause and location of the bug is documented in the bug work item.
Root Cause Documented:
The root cause of the bug is documented, if it is determined. | | Is Required | Yes |
StepsIsolate Functional Area:
In the search for the offending area of code, eliminate areas in the code that do not involve the bug. Reassign Bug (Optional):
If the identified code is in another developer's area, reassign the bug to that developer.
Provide information to help the next developer examine the bug.
Update the Assigned To field in the bug work item with the appropriate developer. Trace Involved Code Areas :
Using debugging tools, use breakpoints and variable watches to examine the identified code for any anomalies that cause the bug. Or mark the code sparingly with tags that provide visible output to a debugger or a log file. Analyze Product with External Tools (Optional):
In addition to tracing code, use other tools in the environment to gauge the effects on the product when certain identified areas are run. Pinpoint the Problem:
Follow the steps to reproduce the bug as many times as necessary to pinpoint the lines of code causing the problem. Document the cause and location of the bug in the bug work item. If the larger root cause is identified, choose an appropriate value for the Root Cause field to assist with querying on all bugs that have this type of information available.
Inputs and Outputs| WorkProduct | Input | Output | Allowable States |
|---|
| Bug |  |  | Active |
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|
|
|
 |
|
|
|
|