Framework: TOGAF

Framework: TOGAF

Classification: Official Standard Maintained by: The Open Group Version: TOGAF 9.2 / TOGAF Standard (10th Edition) Evaluation: N/A — auto-approved as Official Standard

What It Is

TOGAF (The Open Group Architecture Framework) is a comprehensive enterprise architecture methodology that provides a systematic approach to the design, planning, implementation, and governance of enterprise IT architecture. First published in 1995, TOGAF has become the most widely adopted EA framework globally, used by over 80% of the world's leading enterprises.

TOGAF centers on the Architecture Development Method (ADM) — an iterative cycle of phases that guides architects from establishing an architecture capability through defining business, data, application, and technology architectures to governing their implementation. It provides a common vocabulary, recommended standards, a method for designing architectures, and a repository model for storing architecture artifacts.

When to Use It

Select TOGAF when the client context includes:

  • Large or complex organizations that need structured enterprise architecture practice across multiple business units or domains
  • IT transformation programs requiring a disciplined approach to moving from current-state to target-state architecture
  • Architecture governance needs — the organization wants formal oversight of architectural decisions and compliance
  • Multi-system landscape management — the client operates a complex portfolio of interconnected systems and needs rationalization or modernization
  • Regulatory or compliance environments where architecture documentation and traceability are mandated
  • Organizations with existing TOGAF adoption that need architecture work aligned with their established practice

TOGAF is less suited for small teams, single-application contexts, or organizations that need a lightweight approach. In those cases, consider solution architecture patterns or a simplified framework.

Key Concepts

Architecture Development Method (ADM)

The ADM is TOGAF's core — an iterative cycle of phases that produces enterprise architecture:

Phase Name Purpose
Preliminary Framework and Principles Establish architecture capability and principles
A Architecture Vision Define scope, stakeholders, and high-level vision
B Business Architecture Model the business strategy, processes, and organization
C Information Systems Architecture Design data and application architectures
D Technology Architecture Define the technology infrastructure
E Opportunities and Solutions Identify delivery vehicles and implementation projects
F Migration Planning Create detailed implementation and migration plan
G Implementation Governance Oversee architecture-compliant implementation
H Architecture Change Management Manage changes to the architecture over time
— Requirements Management Continuous process managing architecture requirements throughout all phases

Four Architecture Domains

TOGAF organizes architecture into four interrelated domains:

  1. Business Architecture — Business strategy, governance, organization, and key business processes
  2. Data Architecture — Structure of logical and physical data assets and data management resources
  3. Application Architecture — Blueprint for individual applications, their interactions, and relationships to business processes
  4. Technology Architecture — Hardware, software, and network infrastructure needed to support deployment of business, data, and application services

Architecture Building Blocks

  • Architecture Building Blocks (ABBs) — Abstract, technology-neutral components that describe required capability (e.g., "customer data store")
  • Solution Building Blocks (SBBs) — Concrete, product-specific components that implement the capability (e.g., "Salesforce CRM")

Architecture Repository

The Architecture Repository is TOGAF's model for storing all architecture outputs:

  • Architecture Metamodel — definitions of artifact types and their relationships
  • Architecture Landscape — current-state, transition, and target-state architectures at strategic, segment, and capability levels
  • Reference Library — guidelines, templates, patterns, and reference architectures
  • Standards Information Base (SIB) — list of standards governing the architecture
  • Governance Log — record of governance decisions, compliance assessments, and dispensations

Viewpoints and Views

  • Viewpoint — A perspective from which to examine the architecture, defined by stakeholder concerns (e.g., "security viewpoint," "data flow viewpoint")
  • View — A concrete representation of the architecture from a given viewpoint, tailored to a specific audience

Architecture Governance

The framework for managing and controlling architecture at an enterprise level, including compliance reviews, dispensation processes, and architecture boards.

Official Resources