F. Implementation

Phase F: Implementation

Objective

The objective of this phase is to formulate recommendations for each implementation project, and construct an architecture contract to govern the system implementation and deployment. The system is then implemented and deployed during this phase.

Approach

It is here that one brings together all the information for successful management of the various implementation projects. Note that during this phase there is the execution of an organizational specific development process, where the actual development happens.

This phase establishes the connection between architecture and implementation organization, through the Architecture Contract.

Project details are developed, including:

Name, description and objectives
Scope, deliverables and constraints
Measures of effectiveness
Acceptance criteria
Risks and issues

Inputs

Inputs to this phase are:

Request for Architecture Work
Statement of Architecture Work
Re-usable solutions building blocks (from organization's Solutions Continuum, if available)
Impact Analysis - Migration Plan

Steps

Key steps in this phase include:

Project recommendation formulation, for each separate implementation project do the following:
- document scope of individual project in Impact Analysis
- document strategic requirements (from the architectural perspective) in Impact Analysis
- document change requests (such as support for a standard interface) in Impact Analysis
- document rules for conformance in Impact Analysis
- document time-line requirements from road-map in Impact Analysis
Document Architecture Contract
- obtain signature from all developing organizations and sponsoring organization

Outputs

The output of this phase is:

Impact Analysis - Implementation recommendations
Architecture Contract, as recommended in the IT Governance section
The implemented system
- Note: the implemented system is actually an output of the development process. However, given the importance of this output, it is stated here as an output of the architecture development method. The direct involvement of architecture staff in implementation will vary according to organizational policy, as described in Part IV under IT Governance.