|
|
 |
 |
 |
 |
Activity:
Decide on a Bug Fix Strategy
 |
|
Participating Roles
Responsible:
Developer |
To modify code for a bug fix, the developer must decide on the best method to correct the problem and prevent the introduction of bugs. Bug fix decisions should involve architectural, resource, and performance considerations. When deciding on a bug fix, the solution should focus on eliminating the problem. However, it might be necessary to compromise some system functionality to meet requirements and user experience criteria.
Entry Criteria
When:
- The bug is located in the code base.
Dependencies:
- The scenarios associated with the fix area are available.
Sub-Activities
|
|
1 |
Analyze Located Bug |
- Determine the type of bug problem; architectural, resource, or performance.
|
|
2 |
Decide on an Architectural Fix |
- Optional
- Identify the areas in the architecture affected by the bug fix.
- Outline a fix with a change in the design structure.
- Discuss the proposed bug fix with an architect. If the fix impacts areas beyond your code, work with architects and other developers to coordinate the fix.
|
|
3 |
Decide on a Resource Fix |
- Optional
- Identify the affected areas of code.
- Determine whether removing or adding code is best.
- Review the proposed fix with another developer familiar in the area of change.
|
|
4 |
Decide on a Performance Fix |
- Optional
- Identify the areas in the code that are affected by the bug fix.
- Determine whether code optimization fixes, such as refactoring or moving code segments, can positively affect the system.
- If there is any doubt, review the proposed bug fix with another developer familiar in the area of change.
|
Exit Criteria
 |
The design strategy is identified allowing the bug area to be changed with a predetermined goal. | |
 |
 |
 |
 |
© 2006 Microsoft Corporation. All rights reserved.
Version 4.1.0 |
 |
Overview 