Introduction to Implementation

• Purpose
• Relation to Other Core Workflows
• Concepts:
  • Implementation View
  • Mapping from Design to Code
  • Build
  • Software Integration
  • Stubs
  • Development and Integration Areas

Purpose

The purpose of implementation are:

• To define the organization of the code, in terms of implementation subsystems organized in layers.
• To implement classes and objects in terms of components (source files, binaries, executables, and others).
• To test the developed components as units.
• to integrate the results produced by individual implementers (or teams), into an executable system.

The Implementation workflow limits its scope to how individual classes are to be unit tested. System test and integration test are described in the Test workflow.

Relation to Other Workflows

The implementation is related to other workflows:

• The requirements  workflow describes how to, in a use-case model, capture requirements that the implementation should fulfill.
• The analysis and design workflow describes how to develop a design model. The design model represents the intent of the implementation, and is the primary input to the Implementation workflow.
• The test workflow describes how to integration test each build during the integration of the system. It also describes how to test the system to verify that all requirements have been met, as well as how defects are detected and submitted.
• The environment workflow describes how to develop and maintain supporting artifacts that are used during implementation, such as the process description, the design guidelines, and the programming guidelines. See the Rational Unified Process - Artifacts for more details.
• The deployment workflow describes how to use the implementation model to produce and deliver the code to the end-customer.
• The project management workflow describes how to best plan the project. Important aspects of the planning process are the iteration plan, change management and defect tracking systems.