Phases E & F: Opportunities & Solutions and Migration Planning

For Phases E and F, the TOGAF Standard, 10^th Edition introduces the Transition Architecture, representing a possible intermediate situation or plateau between the Baseline Architecture and the Target Architecture.

In the ArchiMate language, the Baseline, Target, and Transition Architectures, as well as their relationships, are shown using the Migration viewpoint:

The Migration viewpoint involves models and concepts that can be used for specifying the transition from an existing architecture to a desired architecture.

Figure 34 shows an example of the ArchiMate Migration Viewpoint to convey how the ArchiSurance group plans to accomplish the migration from its Baseline Architecture to its desired Target Architecture. The IT department of ArchiSurance does not have sufficient resources to carry out the standardization of the back-office systems and the integration of the CRM systems at the same time. Therefore, the following potential migration paths are proposed: one proposes to first replace the two CRM systems with a central, enterprise-wide system, whilst maintaining the separate, per-division back-office systems (Transition A), and then unify the back-office systems into a single back-office suite (Transition C); another proposes first to deploy a single back-office suite with two CRMs (Transition B), and then replace the two CRM systems with a central, enterprise-wide system (Transition C). After that, the data warehousing and IoT solution will be implemented.

Figure 34: Migration View

Transition Architectures enable the planning of implementation projects such as CRM integration and back-office application integration. The sequence of these projects depends on which of the Transition Architectures is selected. This can be is shown in a TOGAF Project Context diagram (Figure 35):

A Project Context diagram shows the scope of a work package to be implemented as part of a broader transformation roadmap. The Project Context diagram links a work package to the organizations, functions, services, processes, applications, data, and technology that will be added, removed, or impacted by the project.

Figure 35: TOGAF Project Context Diagram, expressed in the ArchiMate Language