Skip to main content

Enterprise MSF Agile (with CobiT)

Go Search
Home
  
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Write Code for a Development Task (Create a Quality of Service Requirement)  

Activity - Write Code for a Development Task (Create a Quality of Service Requirement)

Activity Information

Write Code for a Development Task

Description

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.

Roles

PerformerDeveloper

Steps

  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.

Inputs and Outputs

WorkProductInputOutputAllowable States
Class Diagram(none)
Code(none)

Predecessors

TypeNameDependency Type
Cost a Development TaskFinish-Start
Determine InterfacesFinish-Start
Partition the SystemFinish-Start

Successors

TypeNameDependency Type
Perform a Unit TestFinish-Start
Perform a Unit TestFinish-Start
Perform Code AnalysisStart-Start

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