Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Next Steps Create or Update a Unit Test Code the Fix for a Bug |
| Activity: Decide on a Bug Fix Strategy
Developer
|  |  |  | Fix a Bug |  |
|  | Participating Roles Responsible: Developer
### Overview 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. Dependencies: The scenarios associated with the fix area are available. The scenarios and the quality of service requirements are identified. # 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. Plan a fix with a proposed change in design structure. Review the proposed bug fix with the architect.
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. 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.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |