The purpose of this workflow detail is to complete a part of the implementation so that it can be delivered for integration,

Topics

Impelementation Element - Testability Review Record Implementer Review Code Plan Subsystem Integration Implement Design Elements Implement Testability Elements Execute Developer Test Design Model - both application and testability design elements Technical Reviewer Change Request - approved Analyze Runtime Behavior Implementation Subsystem Implementation Element Implement Developre Test Integration Build Plan Use-Case Realization Iteration Plan Test Log Integrator


Description To top of page

In this workflow detail:

  • The implementers write source code, adapt existing source code, compile, link and perform unit tests, as they implement the elements in the design model. If defects in the design are discovered, the implementer submits rework feedback on the design.
  • The implementers also fix code defects and perform unit tests to verify the changes. Then the code is reviewed to evaluate quality and compliance with the Programming Guidelines.

Related Information To top of page

This section provides links to additional information related to this workflow detail.

Timing To top of page

Starts in Elaboration phase, recurs through Construction and Transition phases.

Optionality To top of page

Required

How to Staff To top of page

These activities carried out by the implementer tend to be done by a single person. The review activity is best carried out by a small team staffed by cross-functional team members, typically more senior members of technical staff with greater experience into common problems and pitfalls encountered in the programming language. Special expertise may be required in the problem domain, as is often the case in systems involving telephony or devices with special interfaces. Expertise in specific algorithms or programming techniques may also be required.

Work Guidelines To top of page

The review work is best done in several sessions, each focused on small sections of the system or on specific issues. The goal of these sessions is to identify specific problems in the code that need to be resolved, not to resolve them on the spot; resolution discussions should be postponed until after the review. More frequent reviews which are smaller in scope are more productive than less frequent sessions which are larger in scope.



© Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process   2003.06.13