10 Phases of TOGAF (v 9.2) - A Complete Breakdown

IT architectures are products of iterative design – the making of which does not include a waterfall or other sequential approaches. To excel in making an architecture, iterative approaches such as Agile-Scrum are essential. But this does not imply a lack of management or documentation.

It means there is a restriction on producing pertinent and useful documentation that enhances business strategic plans. The objective is to create a working IS architecture, not create countless, completely pointless artefacts. 

In today’s world, every start-up or business is using the internet to make their business process smooth, quick, and transparent. This is where TOGAF ADM phases help. You can learn about them in detail in the TOGAF 9.2 training. 

The Open Group of Architecture Framework (TOGAF) is a sort of methodology that provides a framework to develop enterprise software. TOGAF is a systematic process that reduces errors, completes deadlines, is within budget, and combines IT with business units to give the utmost results.

The TOGAF was developed in 1995. It is common in the field of enterprise architecture, so newer versions and models were developed. TOGAF is now updated to the 9.2 version. TOGAF has many tools and certified courses to maintain its standards.

A total of 71 courses and 8 tools offered by various organisations are certified by the Open Group.

In this article, we break down what is TOGAF, the TOGAF phases explained, and the TOGAF phases summary. Also, you will find 10 phases, which include the TOGAF ADM preliminary phase and requirement management. Let’s get started! 

Why TOGAF?

For many, the TOGAF architecture vision is a new discipline. Businesses are still figuring out how to use it to increase their profitability even when it has been 2 decades since its launch. Using new software in a business means making a significant change. There are so many points to remember for creating new strategies and plans.

TOGAF takes care that all the technological processes are taking place smoothly. Businesses can more clearly see their existing IT architecture and infrastructure because of TOGAF. It aids in the establishment of precise business development strategies.

It provides a defined process for many businesses and organisations for achieving their goals. All the participating departments are taken into consideration in order to identify the issues they are facing technically. The methodology in this includes COBIT 5, ITIL, and others.

TOGAF teaches how a business can operate as a single unit. One can enhance the processes so that all departments operate effectively. The Open Group of Architecture makes your business operations simpler. The professionals take IT service management certification online to learn all they need to know to help businesses operate smoothly. 

TOGAF ADM CYCLE/Phases – Overview

The Architecture Development Method (ADM) is used to create an enterprise architecture that satisfies the business and IT requirements of the company. The TOGAF professional helps with developing and managing a company’s architecture and to form the base of TOGAF. To do this, the ADM is tailored according to the organisation’s needs.

There are 10 phases of an ADM cycle. It is a detailed process that changes the enterprise’s architecture. The 10 TOGAF ADM phases are: 

1. Preliminary Stage
2. Phase A: Architecture Vision 
3. Phase B: Business Architecture
4. Phase C: Information System Architecture
5. Phase D: Technical Architecture
6. Phase E: Opportunities and Solutions
7. Phase F: Migration planning
8. Phase G: Implement governance
9. Phase H: Architecture change-management
10. Requirement Management

ADM Input and Output 

From each phase, you get deliverables from input and output: 

1. You need not follow the exact suggestions of outputs.
2. Every TOGAF phase deliverable must show where the change has been made.
3. You must follow version numbering.

10 Phases/Life Cycle of TOGAF

Here are 10 TOGAF phases: 

1. Preliminary Phase

Here you need to determine and create a framework for the architectural capabilities of the company. The primary point here is to determine the changes to be done and their implementation.

During this stage, TOGAF is designed to satisfy the requirements. Here we design fundamental concepts, assess how well the company can adapt the structure, and combine TOGAF with different architectural frameworks.

At this stage, there are limits so that organisations are not affected by the amendments in the framework. All the preparations to follow an ADM cycle must be done.

Consider a TOGAF preliminary phase example: the main output is an architectural work request. This request outlines what the requirements are and decides the scope, tools, structure, or framework required to meet the support. 

2. Phase A: Architecture Vision

This TOGAF phase A gives a clear statement and is included in the iteration of ADM. It provides information on the scope of architecture development, building an architecture vision, finding stakeholders, and getting approval to proceed with the framework. 

For better understanding, TOGAF professionals consider probable business scenarios. This helps to get clarity of the requirements. Phase A ensures that the company is ready, committed, and willing to consider the changes in the architectural structure.

In order for the relevant ADM stages to properly dispose of, address, and prioritise requirements, necessities must be identified, maintained, and supplied into and out of them. 

This includes the formation of an architecture project, defining its scope, and going through the principles of business and architecture. 

Phase A involves converting the construction work requirement into a precise design work statement and confirming that the business has the appropriate skills, resources, and commitment to make the required architectural alterations. 

3. Phase B: Business Architecture

As per TOGAF, enterprise architecture is to improve the business abilities of an organisation. The primary goal of Phase B is to create a target business architecture that determines how the company looks and solves the architecture work request.

First, it needs to identify the candidate architecture roadmap to fulfil the gap between the base and achievement.

Phase B, C, and D follow similar steps. There is a necessity to reuse the model from the stakeholder’s view. The architect then creates a baseline and objective specification for the service strategy and conducts a gap analysis to know how to switch back and forth in time. 

4. Phase C: Information System Architecture

The TOGAF Phase C is the blend of application and data architecture. There are proponents for both approaches, till they are used. It also doesn’t matter what order they are used in.

The steps involved in making the data and application architectures include: selecting views, reference models, and tools, developing baselines, searching for architecture descriptions, doing gap analyses, and defining the potential roadmap.

The theme is where the main difference between data and applications comes from. This reflects the use of different models, architectural representations, and technologies. The focus of Phase C is to create a framework for data and application systems. 

5. Phase D: Technical Architecture

Technical architecture comes in Phase D of TOGAF. Technology architecture defines the interaction and structure of physical and logical components of technology.

The target technology architecture is developed during phase D. This target technology architecture supports the application and data which realise components of the business. 

The steps in Phase D are similar to C and B. The main difference here is that the focus is technology. However, it includes technical reference models or measurements.

Measurements include performance, location, maintainability, and availability. Deliverables and Outputs are necessary to succeed in technical architecture that is important for business architecture. 

6. Phase E: Opportunities and Solutions 

Finding possibilities to deploy practical solutions that will deliver the intended architecture is how Phase E takes its title. Phase E creates the first comprehensive version of the architectural blueprint by fusing the suggestions from cycles B, C, and D of structure testing and enhancement. 

The primary concern at this point is how to offer the framework. In order to attain the intended design, it is focused on developing an architectural roadmap that lists project tasks in a timeframe.

Phase E is the first to deal specifically with implementation. The assignment is to determine the primary projects or deliverables that will be carried out. 

Stage E will result in an iterative algorithm made up of intermediary or transitional structures when the modification is so significant that moving from the basic to the desired system is not practicable. 

7. Phase F: Migration planning

The primary stages of ADM phases TOGAF identify what is the need for changes in the architecture, technical architecture, data, and application and why to support it.

Phase F's objective is to prioritise implementation projects that are currently underway. One of the tasks is to assess the costs, benefits, and interconnections of the various migration programmes. 

Sorting the numerous implementation projects in terms of priority is the aim of Phase F. Evaluating the dependencies, expenses, and advantages of the various migration initiatives are one of the activities. 

There are four basic frameworks that phase F requires. The four frameworks are: 

• Business Plan 
• Enterprise Architecture
• Portfolio Management
• Project management

These 4 areas must be the priority since the business must evaluate performance, investment returns, success factors, the value of the business, and strategic fit in this phase. 

Migration planning, or how to transition from the Starting point to the Target Structures by concluding a thorough Execution and Migration Plan, is covered in Phase F (Migration Planning). 

8. Phase G: Implement Governance

Phase G takes assurance whether the current projects or the operational project adhere to the specified architecture.

To maximise value creation and advantages while minimising risks associated with the reform program, the target architecture is generally built as a sequence of conversions. Each change moves the firm closer to realising its own commercial objectives. 

It provides oversight of the structure that is implemented. All the information for successful management is brought up together in this phase. 

9. Phase H: Architecture Change-Management

There will always be new requirements and adjustments to the architecture so that the business operates dynamically. The organisational change procedure for managing modifications to the architecture in a coordinated and organised manner is described in Phase H.

Phase H is to make sure that the framework works out well for the target business. This typically necessitates constant observation of regulatory requests, emerging technology, or modifications to the corporate environment.

In the end, the framework that supports the organisation's previous and present functions is no longer functional. A transformation request's outcome in Phase H can be categorised as either simplification, which is typically motivated by the need to decrease funding, or iterative change.

It also calls for extra value from financial policy or redesigns change, which again is motivated by the need to encourage investment and develop new worth. 

10. Architecture Requirements Management

Methods for handling changes to the new design are established through architecture change management. It needs management to investigate how architecture requirements are managed across the ADM. 

Our expert-led PMP Exam Prep program is tailored to help you ace the PMP exam and advance your project management skills, propelling your career growth.

3 Pillars of TOGAF

Three pillars aid in the development of a methodical procedure for organising and utilising technology platforms in a concise way that is in line with the company’s governance goals.

TOGAF's purpose of communicating in the same language promotes and enables the many stakeholders to remain on the same page, something that may not normally occur in corporate environments.

Product development relies on cooperation across diverse business divisions within or outside of Information Technology. This leads us to the three pillars of TOGAF: 

1. Enterprise Architecture Domains

There are four main areas under this: 

• Business Architecture 

This defines the standards and governance, the strategy used in business, and processes. 

• Data Architecture 

It maintains the structure of physical data and logical data assets. It also includes other data structures.

• Applications Architecture 

You get a framework to deploy individual systems, this includes the application and maintaining a relationship important for the process in business. 

• Technical Architecture 

Under this comes the hardware, software, and infrastructure of the network.

2. Architecture Development Model (ADM)

Productivity engineering is used throughout the iterative approach to creating a real corporate framework. Furthermore, this can be tailored to the needs of the business; this is not a one-size-fits-all strategy.

When an architecture has been created, the business can iteratively push it out to all divisions or departments, minimizing potential error and further fostering coherent communication across the organization.

3. Enterprise Continuum

This categorization system keeps track of a variety of architecture, from general, industry-standard choices to specialized, enterprise-specific ones. 

TOGAF: 7 Categories of Work

TOGAF has 7 categories of work. These categories are important to assess the business needs. The 7 categories are given below: 

1. Introduction 

An overview of the fundamental ideas underpinning enterprise architecture, with a focus on the TOGAF methodology. It includes the latest update outlining the modifications here between the current edition and the prior edition of TOGAF as well as explanations of words used across TOGAF.

2. Architecture Development Method 

It outlines the TOGAF ADM, a method for creating an enterprise architecture that is step-by-step.

3. ADM Guidelines and Techniques 

A selection of principles and methods for implementing TOGAF and also the TOGAF ADM.

4. Architecture Content Framework 

The TOGAF architecture includes an outline of common design outputs, the utilisation of reused architecture basic components, and a standardised metamodel defining architecture artefacts.

5. Enterprise Continuum and Tools 

Techniques and taxonomies for organising and storing the results of architectural activity inside an organisation.

6. TOGAF Reference Models 

A number of architecture modelling purposes, including the Comprehensive Assessment Infrastructure Reference Model and the TOGAF Foundation Architecture. 

7. Architecture Capability Framework 

The structure, procedures, knowledge, abilities, tasks, and duties are necessary to build and run an enterprise's architectural function. 

Business Benefits of TOGAF

Even now, many organisations are not aware of TOGAF. Here are the ways how TOGAF is beneficial to your business: 

1. TOGAF Results in Increased Efficiency of Business

A company’s architecture blueprint includes different departments, IT infrastructure, stakeholders, and investors. Because of strong market competition, businesses need to change their business strategies.

A TOGAF professional may contribute to your success. These may help to create effective strategies and make some needful changes. This may save your time and risk which even saves your funds.

2. A Common Terminology All Around the World

There is wide use of TOGAF with clear and common terms. This makes communication between professionals easy. Using this, one can collaborate with many national and international companies.

Professionals can find solutions to the company’s problems and focus on their work. They can create a new architecture for security reasons. Identifying errors helps to provide quick solutions.

3. TOGAF Can Help in Futureproofing Organizations

You can use TOGAF-based architectures repeatedly. Once a blueprint is created, companies can use it to make additional changes to the framework.

The framework can be modified as per the new changes. This enhances the IT capabilities and its structure. 

4. Flexible For Businesses

TOGAF has all the features to make a successful framework for a business. The changes don’t affect your business. If you have various business branches, set goals that make you distinct from other competitors. A TOGAF professional will come up with a unique framework.

5. TOGAF is Evolving Continuously 

To succeed and stay ahead of your competitors you need to evolve regularly. TOGAF keeps on improving by developing new tools and techniques for a smooth process.

However, the core principle still remains the same. Therefore, the professionals familiar with older versions can work with the ones who have just stepped into the field. 

Conclusion

The TOGAF framework offers instructions on how to organise and control the creation of enterprise architecture. It also offers advice on how to evaluate the situation as it is and how to design a successful strategy.

Earning a TOGAF certification can be quite lucrative since the demand for knowledgeable professionals is high. A nice way to prepare yourself for a TOGAF job is to get an TOGAF 9.2 training at KnowledgeHut. 

Businesses can use the TOGAF framework to support their architecture in a number of ways. Its structure allows it to be suitably customised to meet the needs of the company.

This framework will reduce time, cost, and risk in recruiting, and training. A TOGAF certificate can be used worldwide.