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

Project Portal
| ### Next Steps Write or Update a Unit Test for Bug Fix Code Fix |
| Decide on Strategy for a Fix ( 3 : VER : 3 : 3.2 ) Developer
Activity: Decide on Strategy for a Fix
Developer
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Developer Consult: Solution Architect Developer
### Overview To modify code for a bug fix, the developer must decide on the best method to correct the problem while preventing the introduction of additional 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 The bug work item is in the Active state. The bug work item is in the Active state. The scenario lists associated with the fix area are available. The scenario lists associated with the fix area are available. The scenarios or the quality of service requirements are identified. The scenarios or the quality of service requirements are identified. # Sub-Activities
1 | Analyze Located Bug | Verify the cause and 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 and lead developer responsible for the area of change.
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 the lead developer responsible for 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 re-factoring or moving code segments, can positively affect the system. Review the proposed bug fix with the lead developer responsible for the area of change.
5 | Reassign Bug | If the cause or type of bug is incorrect, reassign the bug to a developer who can determine the correct cause and type of bug. Provide information to help the next developer examine the bug. Update the Assigned To field in the bug work item with the appropriate developer.
# Exit Criteria
| The fix strategy is identified allowing the bug area to be changed with a predetermined goal.
| The bug work item is updated with the correct cause and type of bug and then reassigned.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |