An Introduction to the TOGAF Enterprise Architecture Framework

Among many enterprise architecture frameworks, TOGAF® is neither the first nor likely the last, yet it has been used worldwide for nearly two decades, marking an impressive achievement in today’s technology landscape.

TOGAF stands for The Open Group Architecture Framework, developed by The Open Group, a non‑profit technology industry consortium that continues to update and reaffirm the standard.

This article focuses on familiarising beginners with TOGAF.

Understanding Enterprise Architecture

In the previous article we explored enterprise architecture frameworks. Enterprise architecture (EA) refers to an overall view and approach to software and other technologies across a company.

EA is not merely about organizing internal infrastructure; its goal is to analyse, design, plan, and implement the right technologies in a way that truly solves business needs.

Increasingly, EA also encompasses business‑process management and data analytics, aiming to execute business strategies with efficiency, agility, and security.

If all this sounds complex—designing and implementing a clear, long‑term solution for all enterprise software—it is, because it truly is. That is why enterprise architecture frameworks began appearing informally and formally over 50 years ago.

TOGAF History and Facts

As a subset of computer architecture, enterprise architecture traces back to the mid‑1960s when IBM and other companies and universities first adopted explicit methods for building enterprise systems.

In the following decades technology grew more complex; today most companies, regardless of size, use the Internet to simplify and accelerate business processes. EA has become essential for understanding hardware and software options both on‑premises and in the cloud, and for ensuring security when sharing data across platforms.

TOGAF was originally developed in 1995. Like many later versions, it offered iterative improvements and theory. It drew heavily from the U.S. Department of Defense’s Technical Architecture Framework for Information Management (TAFIM). Interestingly, a few years after TOGAF’s emergence, the DoD stopped using TAFIM, yet TOGAF’s implementation and success have continued globally for over 20 years.

The Open Group has updated TOGAF to the latest 9.1 version, first released in 2011. The group also certifies tools and courses that conform to the standard. Today, eight organisations provide eight certified tools and 71 courses, all officially recognised by The Open Group.

The TOGAF Approach within EAF

The Open Group defines TOGAF as the de‑facto global standard for enterprise architecture. The framework aims to help organisations address all critical business needs through four objectives:

Ensure that all users, from key stakeholders to team members, speak the same language, fostering a shared understanding of the framework, its content, and goals.

Avoid vendor lock‑in to proprietary EA solutions; TOGAF is free for internal use.

Save time and money, making resource utilisation more efficient.

Deliver demonstrable return on investment (ROI).

TOGAF’s Three Pillars

If the four objectives represent the theoretical outcomes of using TOGAF, the three pillars describe the methods to achieve them. These pillars create a systematic process that aligns software technology with governance and business goals, encouraging collaboration across IT and business units.

TOGAF is organised into three major pillars:

Enterprise Architecture Domains

These domains divide architecture into four key areas (sometimes called the “BDAT” areas):

Business Architecture – defines business strategy, organisation, key processes, governance, and standards.

Application Architecture – provides a blueprint for deploying individual systems, including interactions between applications and their relationship to core business processes.

Data Architecture – records the structure of logical and physical data assets and related data‑management resources.

Technical Architecture – describes the hardware, software, and network infrastructure needed to support critical applications.

Architecture Development Method (ADM)

This iterative cycle uses performance engineering to develop a concrete enterprise architecture. It is customisable to an organisation’s needs, rather than a one‑size‑fits‑all approach. Once an architecture is created, it can be rolled out across teams or departments, minimising errors and fostering coherent communication.

Enterprise Continuum

This classification system tracks a series of architecture solutions, starting from generic industry‑standard options and extending to custom, organisation‑specific solutions.

Supporters claim that ADM is the core of TOGAF —the pillar that makes TOGAF effective and distinguishes it from other frameworks. The Architecture Development Method provides eight steps to determine an enterprise’s current position and desired future state across the four architecture domains.

Once business processes are established throughout the lifecycle, ADM helps bridge the gap between current state and long‑term goals, breaking that gap into smaller, actionable, understandable packages that teams can implement.

TOGAF’s main pillars sometimes also include two additional aspects: certified tools and qualifications.

The Open Group offers two certification levels: a foundational level teaching basic EA principles and TOGAF introduction, and an advanced level covering business analysis and application architecture. The group also validates tools aligned with TOGAF; for the latest version, eight organisations provide eight certified tools.

Benefits of Using TOGAF

ADM’s benefit is that it can be customised to an organisation’s needs—no need to adopt a structure that doesn’t fit your business. These smaller packages are scalable; if one team implements them successfully, other teams can adopt them with minimal adjustment, creating a process with multiple checkpoints that reduces errors as the scope of architecture implementation expands.

Certified individuals also benefit: a study of industry professionals showed that enterprise architects, software architects, and IT leaders who obtain TOGAF certification earn on average $10,000–$20,000 more per year than similarly positioned peers without certification.

Some experts note that while TOGAF appears logical, it represents a significant shift for traditional technical consultants—but if adoption continues steadily, the perception may change.

Successes and Criticisms

According to The Open Group, TOGAF is used by over 80% of employees in 50 companies worldwide and by over 60% of Fortune 500 firms. Critics often claim the framework is overly complex or theoretically impractical, yet many organisations still employ it.

Companies that successfully implement the framework acknowledge that failures do occur because TOGAF cannot solve every enterprise problem. While issues may stem from TOGAF principles or EA itself, others argue that key stakeholders and C‑level executives sometimes do not allocate sufficient time to define crucial factors such as key performance indicators (KPIs), which hampers architecture team success.

This lack of full buy‑in sometimes results from TOGAF’s complexity overall. In practice, the best advice may be to adopt only the parts that suit your company, skipping overly burdensome sections and focusing on the most necessary elements. After all, the critical stakeholders are those who need the structure to work for them.

Many recognise that TOGAF is an evolving effort, with new versions released every few years. Even skeptics find that applying TOGAF is usually better than doing nothing.

When a company wants to adopt a new technology, it often has to build a suitable technical team from scratch and track various data, leading to chaos as technology rapidly evolves. This explains why busy IT and architecture teams feel perpetually behind.

TOGAF is not a magical tool, but it does provide a structured approach that helps teams and senior management avoid reinventing the wheel each time a new technology is integrated.

Technical expert Jason Bloomberg highlighted why TOGAF remains a paradoxical topic in the EA industry. Organisations using TOGAF typically fall into four groups: those who apply it incorrectly and see no value; those who achieve baseline success with legacy issues; those who meet clear business goals; and those who aim for greater agility overall. The last group views architecture as a path to increased agility.

As its widespread use demonstrates, TOGAF can help enterprises of any size and industry, but users should first understand its pros and cons and then apply the parts that make sense for their specific context.

Source: http://jiagoushi.pro/node/1077

Discussion: Join the Knowledge Planet "Chief Architect Circle" or follow the WeChat account "jiagoushi_pro".

WeChat Public Account

Follow the public account

Chief Architect Think Tank

WeChat Small Account

Groups to join: Architecture, Cloud Computing, Big Data, Data Science, IoT, AI, Security, Full‑Stack Development, DevOps, Digital Transformation, Product Transformation.

Knowledge Planet

Ask experts, get close contact, or receive private sharing.

Click to join Knowledge Planet "Chief Architect Circle"

WeChat Circle

Exchange with like‑minded peers.

Click to join WeChat Circle "Chief Architect Circle"

Himalaya

Listen on the road or in the car to the latest tech news and architecture insights.

Click to listen to "Smart Moments, Architecture Guy Talks Black Tech"

Knowledge Planet

Meet more friends, discuss career and technology.

Click to join Knowledge Planet "Knowledge and Technology"