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

Project Portal
| ### Next Steps Create or Update a Unit Test Perform a Unit Test Perform Code Analysis |
| ### Patterns & Practices Performance Checklist Security Checklist |
| Activity: Write Code for a Development Task
Developer
|  |  |  | Implement a Development Task |  |
|  | Participating Roles Responsible: Developer
### Overview To write code for a development task, identify the area where the change should occur, then write unit tests to validate the code, review and fix the written code, and finally integrate the code into the version control server. Additional steps may include debugging, refactoring, and shelving the code. After the code is written, reviews are necessary to ensure the quality of the code conforms to established practices and requirements. The code must not cause harmful side-effects to other parts of the application. # Entry Criteria Dependencies: A development task derived from a scenario or quality of service requirement is identified and costed. The system and application diagrams have been updated as necessary to reflect the architecture for the new scenario or quality of service requirement. The latest version of the source code is loaded. The development task is scheduled for the current iteration. If test driven development is used, a unit test for the task is created. # Sub-Activities
1 | Select Code Component | Map the task to the component where the functionality is located. If this is a new component, select it in the application diagram. Choose to implement the functionality from the component to create a map.
2 | Create New Classes or Methods | From the class diagram, create the classes necessary to implement the functionality. Create new methods and name them appropriately. Make sure the method name and the abstraction are consistent.
3 | Implement Method Logic | Check out existing classes that need to be changed. Add or change the code to implement the functionality in each of the new methods. Change logic in existing methods where appropriate. When writing the code, keep security and performance requirements in mind. Look for the best data structures and algorithms to implement the solution. If an unfamiliar area is found, look for coding examples that implement a similar solution. Use these examples as a basis, rework them, and fit them into the appropriate class and method structure.
# Exit Criteria
| The code for the development task is complete.
| Any new methods are consistent with the classes that they populate.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |