This chapter provides an architectural oversight of the implementation.

Objectives

The objectives of Phase G are to:

• Formulate recommendations for each implementation project.
• Construct an Architecture Contract to govern the overall implementation and deployment process.
• Perform appropriate governance functions while the system is being implemented and deployed.
• Ensure conformance with the defined architecture by implementation projects and other projects.

Approach

It is here that all the information for successful management of the various implementation projects is brought together. Note that in parallel with Phase G there is the execution of an organizational-specific development process, where the actual development happens.

Phase G 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

Implementation governance is closely allied to overall architecture governance, which is discussed in Part IV: Resource Base, Architecture Governance .

A key aspect of Phase G is ensuring compliance with the defined architecture(s), not only by the implementation projects, but also by other ongoing projects within the enterprise. The considerations involved with this are explained in detail in Part IV: Resource Base, Architecture Compliance .

Inputs

Inputs to Phase G are:

• Request for Architecture Work (Request for Architecture Work)
• Statement of Architecture Work (Major Output Descriptions)
• Re-usable Solution Building Blocks (from organization's Solutions Continuum (see Part III: Enterprise Continuum), if available)
• Impact Analysis (see Impact Analysis) - detailed Implementation Plan and Migration Plan (including Architecture Implementation Contract, if appropriate)

Steps

Key steps in Phase G include:

1. Formulate Project Recommendation

   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 timeline requirements from roadmap in Impact Analysis
2. Document Architecture Contract
   • Obtain signature from all developing organizations and sponsoring organization
3. Review Ongoing Implementation Governance and Architecture Compliance

Outputs

The outputs of Phase G are:

• Impact Analysis (see Impact Analysis) - implementation recommendations
• Architecture Contract (see Architecture Contract), as recommended in Part IV: Resource Base, Architecture Contracts
• The architecture-compliant 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 ADM. The direct involvement of architecture staff in implementation will vary according to organizational policy, as described in Part IV: Resource Base, Architecture Governance .

The TOGAF document set is designed for use with frames. To navigate around the document:

• In the main Contents frame at the top of the page, click the relevant hyperlink (Part I, Part II, etc.) to load the Contents List for that Part of the TOGAF document into the Secondary Index frame in the left margin.
  
  
• Then click in that Contents List to load a page into this main frame.
  
  

Downloads of the TOGAF documentation, are available under license from the TOGAF information web site. The license is free to any organization wishing to use TOGAF entirely for internal purposes (for example, to develop an information system architecture for use within that organization). A hardcopy book is also available from The Open Group Bookstore as document G063.