TOGAF 9 Architecture Development (ADM) Cycle – The Easy Way!

TOGAF is an architecture framework. TOGAF provides the methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture. It is based on an iterative process model supported by best practices and a re-usable set of existing architecture assets.

Table of Contents

Hello and welcome to the TOGAF 9 Architecture Development Cycle Quick Reference Guide. In this session, you’ll get an overview of important activities performed in each phase of ADM. Let’s get started with the TOGAF ADM Cycle.

TOGAF Introduction.

The term TOGAF Stands for ” The Open Group Architecture Framework“. TOGAF is the de-facto global standard for Enterprise Architecture and it can be used freely by any enterprise organization.

TOGAF is an architecture framework. It provides a set of tools and a method to build an Enterprise Architecture (EA).

TOGAF was initially developed in 1995 and it was based on Technical Architecture Framework for Information Management (TAFIM), developed by the US Department of Defense (DoD). The Open Group members developed and maintain the TOGAF 9.

TOGAF ADM Cycle Overview.

The TOGAF Architecture Development Method (ADM) cycle, is the result of continuous efforts from an enormous number of architecture practitioners. It describes a method for developing and managing the lifecycle of enterprise architecture and forms the core of TOGAF.

TOGAF Architecture Development Cycle (ADM) is a combination of ten separate phases. Each ADM phase integrates various architectural assets to meet the business and IT needs of an organization.

TOGAF Architecture Development Cycle

Now, Let’s go through the objective and list of activities performed in each phase.

TOGAF Preliminary Phase.

The first phase of the TOGAF ADM cycle is the Preliminary Phase. The objective of the preliminary phase is to determine and establish the architecture capability desired by the organization.

The following activities are performed during the Preliminary Phase.

  • Prepare the organization for successful TOGAF architecture projects.
  • Preparation and initiation activities required to create an Architecture Capability.
  • Customization of TOGAF.
  • Selection of tools, and the definition of Architecture Principles.

Phase A - Architecture Vision

The initial stage of the TOGAF Architecture Development Method (ADM) cycle is Phase A (i.e. Architecture Vision). In this phase, the primary objective is to define the scope, identifying the stakeholders, creating the architecture vision, and obtaining approvals.

Following are the key tasks performed in this phase are:

  1. Set the scope, constraints, and expectations for a TOGAF project.
  2. Create an Architecture Vision Document.
  3. Identify key stakeholders.
  4. Validate the business context and create the Statement of Architecture Work.
  5. Obtain approvals.

Phase B - Business Architecture

The objectives of Phase B is to focuses on the development of the Business Architecture to support the agreed vision of architecture. In practical terms, the Business Architecture is also often necessary as a means of demonstrating the business value of subsequent architecture work to key stakeholders, and the return on investment to those stakeholders from supporting and participating in the subsequent work.

Following are the activity performed in Phase B – Business Architecture.

  1. Select reference models, viewpoints, and tools.
  2. Define Baseline Business Architecture description.
  3. Define Target Business Architecture Description.
  4. Perform gap analysis.
  5. Define candidate roadmap components.
  6. Conduct formal stakeholder review.
  7. Create Architecture Definition Document.

Phase C - Information Systems Architectures

The development of Data and Application Architectures for an Enterprise Architecture project is outlined in Phase C or Information Systems Architecture. It describes how the Information Systems Architecture of the company will allow the Business Architecture and the Architecture Vision to address the Architecture Work Request and the concerns of stakeholders.

Information Systems Architecture describes the fundamental organization of an IT system, embodied in.

  1. The major types of information and applications that process them.
  2. Relationships to each other and the environment; and
  3. Principles governing its design and evolution.

Information Systems Architecture shows how the IT systems meet the business goals of the enterprise.

Phase D - Technology Architecture

The Technology Architecture development for an Enterprise Architecture project is described in Phase D. The Target Technology Architecture allows the application and data components to be logical and physical. It also allows the vision of architecture, addressing the issues associated with the Request for Architecture Work and stakeholders.

Technology Architecture describes the fundamental organization of an IT system, embodied in.

  1. its hardware, software, and communications technology;
  2. their relationships to each other and the environment; and
  3. the principles governing its design and evolution.

By the end of Phase D, the logical Enterprise Architecture, that is the blueprint of the target state, is ready. From the next screen onwards, we will focus on the solutioning phases where the blueprint of Enterprise Architecture will be realized.

Phase E - Opportunities and Solutions.

The process of identifying delivery vehicles such as projects, programs, or portfolios that effectively deliver the Target Architecture identified in previous phases is described in Phase E or ‘Opportunities and Solutions.’

This phase starts with initial implementation planning. Gaps found in the previous phases are consolidated, prioritized, and grouped according to the dependencies. Major implementation projects are identified based on the identified gaps and roadmap components to be developed. Following are the steps performed in Phase E.

  1. Perform initial implementation planning and the identification of delivery vehicles for the building blocks identified in the previous phases.
  2. Determine whether an incremental approach is required, and if so identify Transition Architectures.

Once the approach is decided, assess the priorities and schedule the implementation projects based on business goals, requirements, urgency, and business value. The dependency of one component on another must be understood. This also acts as an input to implementation project scheduling.

Phase F - Migration Planning.

In cooperation with the portfolio and project managers, Phase F addresses migration planning, that is, how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan. For work packages and projects identified in Phase E, the following tasks are executed:

The following tasks are performed for work packages and projects identified in Phase E:

  1. Cost/benefit analysis: Perform cost/benefit analysis to assess the business value of every project
  2. Risk assessment: Perform risk assessment to see which projects are at high risk and which ones are at low risk.
  3. Based on the business value and the associated risk, projects are prioritized and documented in the detailed Implementation and Migration Plan.
  4. At the end of phase F, transition planning is concluded.

Phase G - Implementation Governance.

In Phase G, implementation projects are kicked off, and the architecture team provides the oversight and governance. This phase continues until the implementation projects deliver the operational systems that are deployed onto the production environment.

Following are the key activities of this phase:

  1. Provide architectural oversight for the implementation.
  2. Prepare and issue Architecture Contracts.
  3. Ensure that the implementation project conforms to the architecture.

Phase H - Architecture Change Management

Procedures for managing change to the new architecture are established in Phase H or Architecture Change Management. Typically, this process will provide for the continuous monitoring of requests for governance, new technology developments, and changes in the business environment. When changes are identified, change management will determine if a new architecture evolution cycle is to be formally initiated.

Following are the key activity performed in Phase H – Architecture Change Management.

  1. Provide continual monitoring and a change management process to ensure that the architecture responds to the needs of the enterprise, and maximizes the business value.

TOGAF Requirements Management.

As indicated by the ‘‘Requirements Management’’ circle at the center of the ADM graphic, the ADM is continuously driven by the requirements management process.

It is important to note that the Requirements Management circle denotes not a static set of requirements, but a dynamic process whereby requirements for enterprise architecture and subsequent changes to those requirements are identified, stored, and fed into and out of the relevant ADM phases, and also between cycles of the ADM.

Following are the key activities performed in Requirements Management.

  1. Ensure that every stage of a TOGAF project is based on and validates business requirements.
  2. Requirements are identified, stored, and fed into and out of the relevant
  3. ADM phases, which dispose of, address, and prioritize requirements.


Summary .

The Architecture Development Method forms the core of TOGAF and is a method for deriving Organization-Specific Enterprise Architecture. ADM phase is divided into ten phases and each has its own significance in the implementation of the project. Please do check out our Youtube channel for more such tutorial videos.