Skip to main content

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Locate the Cause of a Bug (Test a Quality of Service Requirement)  

Activity - Locate the Cause of a Bug (Test a Quality of Service Requirement)

Activity Information

Locate the Cause of a Bug

Description

When a bug is reported, it is up to the developer to 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 such as logs, a debugger, analysis of the code, or print statements to pinpoint the cause and record the location assessment.

Roles

PerformerDeveloper

Steps

  1. Isolate Functional Area:
    In searching for the offending area of code, eliminate areas in the code that do not involve the bug.

  2. Trace Involved Code Areas:
    Using debugging tools, sparingly mark the identified code area with tags that provide output visually to a debugger or log file.

  3. Analyze System with External Tools (Optional):
    In addition to tracing code, use other tools in the environment to gauge the effects on the system when running certain identified areas.

  4. Pinpoint the Problem:
    Run the defect scenario as many times as necessary to pinpoint the lines of code causing the problem.

  5. Perform Code Analysis:
    If debugging the code is not possible due to untraceable quantities such as performance or resource problem, analyze the code line-by-line to identify the problem.

Inputs and Outputs

WorkProductInputOutputAllowable States
BugActive

Predecessors

TypeNameDependency Type
Reproduce the BugFinish-Start

Successors

TypeNameDependency Type
Decide on a Bug Fix StrategyFinish-Start

Last modified at 1/17/2008 11:18 PM  by Administrator