Home The TOGAF® Standard
Word Search | Search Index

Advanced Search
Provide feedback on this page

TOGAF® Fundamental Content

Extended Guidance

General How-To

Establishing an EA Team

Agile Methods
Business Architecture
Data/Information Architecture
Security Architecture

Reference Models & Method

6. Migration Planning Techniques

This chapter contains a number of techniques used to support migration planning in Phases E and F.

6.1 Implementation Factor Catalog

The technique of creating an Implementation Factor catalog can be used to document factors impacting the architecture Implementation and Migration Plan.

The catalog should include a list of the factors to be considered, their descriptions, and the deductions that indicate the actions or constraints that have to be taken into consideration when formulating the plans.

Factors typically include:

An example catalog is shown in Figure 6-1 .

Figure 6-1: Implementation Factor Catalog

6.2 Consolidated Gaps, Solutions, & Dependencies Matrix

The technique of creating a Consolidated Gaps, Solutions, and Dependencies matrix allows the architect to group the gaps identified in the domain architecture gap analysis results and assess potential solutions and dependencies to one or more gaps.

This matrix can be used as a planning tool when creating work packages. The identified dependencies will drive the creation of projects and migration planning in Phases E and F.

An example matrix is shown in Figure 6-2 .

Figure 6-2: Consolidated Gaps, Solutions, and Dependencies Matrix

6.3 Architecture Definition Increments Table

The technique of creating an Architecture Definition Increments table allows the architect to plan a series of Transition Architectures outlining the status of the Enterprise Architecture at specified times.

A table should be drawn up, as shown in Figure 6-3 , listing the projects and then assigning their incremental deliverables across the Transition Architectures.

Figure 6-3: Architecture Definition Increments Table

6.4 Transition Architecture State Evolution Table

The technique of creating the Transition Architecture State Evolution table allows the architect to show the proposed state of the architectures at various levels using the defined taxonomy (e.g., the TOGAF TRM).

A table should be drawn, listing the services from the taxonomy used in the enterprise, the Transition Architectures, and proposed transformations, as shown in Figure 6-4 .

All SBBs should be described with respect to their delivery and impact on these services. They should also be marked to show the progression of the Enterprise Architecture. In the example, where target capability has been reached, this is shown as "new" or "retain"; where capability is transitioned to a new solution, this is marked as "transition"; and where a capability is to be replaced, this is marked as "replace".

Figure 6-4: Transition Architecture State Evolution Table

Another technique (not shown here) is to use color coding in the matrix; for example:

6.5 Business Value Assessment Technique

A technique to assess business value is to draw up a matrix based on a value index dimension and a risk index dimension. An example is shown in Figure 6-5 . The value index should include criteria such as compliance to principles, financial contribution, strategic alignment, and competitive position. The risk index should include criteria such as size and complexity, technology, organizational capacity, and impact of a failure. Each criterion should be assigned an individual weight.

The index and its criteria and weighting should be developed and approved by senior management. It is important to establish the decision-making criteria before the options are known.

Figure 6-5: Sample Project Assessment with Respect to Business Value and Risk
return to top of page