TOGAF anchors

Vault note, not reviewed against the source. Written in the knowledge vault on 2026-05-12 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

Primary documents, operating body, training providers, named practitioners, reference resources for the TOGAF cluster.

Primary documents (TOGAF Standard, 10th Edition)

The 10th Edition is structured into two parts:

TOGAF Fundamental Content (the stable core)

  • TOGAF Standard โ€” Introduction and Core Concepts
  • TOGAF Standard โ€” Architecture Development Method โ€” the ADM, its phases, objectives, inputs, steps, outputs.
  • TOGAF Standard โ€” ADM Techniques โ€” architecture principles, stakeholder management, architecture patterns, gap analysis, migration planning techniques, interoperability requirements, business transformation readiness, risk management, capability-based planning.
  • TOGAF Standard โ€” Applying the ADM โ€” iteration, levels, security architecture integration, using the ADM in different contexts.
  • TOGAF Standard โ€” Architecture Content โ€” the content framework, deliverables, artifacts, building blocks, the content metamodel.
  • TOGAF Standard โ€” Enterprise Architecture Capability and Governance โ€” establishing an architecture capability, the architecture board, architecture governance, compliance, contracts, maturity models, skills framework.

TOGAF Series Guides (modular, updatable)

A growing library, including:

  • The TOGAF Leader's Guide to Establishing and Evolving an EA Capability
  • A Practitioners' Approach to Developing Enterprise Architecture Following the TOGAF ADM
  • TOGAF Series Guide: Business Architecture (and a Body of Knowledge companion)
  • TOGAF Series Guide: Information Architecture / Data Architecture
  • TOGAF Series Guide: The TOGAF Technical Reference Model (TRM)
  • TOGAF Series Guide: Integrating Risk and Security within a TOGAF Enterprise Architecture
  • TOGAF Series Guide: Enabling Enterprise Agility
  • TOGAF Series Guide: Digital Technology Adoption
  • TOGAF Series Guide: Microservices Architecture
  • TOGAF Series Guide: Government Reference Model (GRM)
  • TOGAF Series Guide: Organization Mapping
  • TOGAF Series Guide: Value Streams
  • TOGAF Series Guide: Business Capabilities
  • TOGAF Series Guide: Business Models
  • Topic guides on architecture project management, sustainability, cloud, and others (the library expands)

Publisher: The Open Group. opengroup.org / togaf.org. Documents available free for personal / non-commercial use after registration; commercial use under license.

Primary documents (historical)

  • TOGAF 9.2 (2018) โ€” five-part structure: ADM, ADM Guidelines and Techniques, Architecture Content Framework, Enterprise Continuum and Tools, Architecture Capability Framework, plus TOGAF Reference Models. Still in use in 9.x-trained workforces.
  • TOGAF 9.1 (2011) โ€” maintenance update.
  • TOGAF 9 (2009) โ€” the major restructure version.
  • TOGAF 8 (2002-2003) โ€” "Enterprise Edition." Historical reference.

Owning body

  • The Open Group โ€” vendor-neutral technology consortium. Members include major IT vendors (IBM, Oracle, SAP, Microsoft, others), large enterprises, government bodies, consultancies, and academic institutions. Also owns:
    • ArchiMate โ€” enterprise architecture modeling notation; companion to TOGAF.
    • IT4IT โ€” reference architecture for managing the business of IT.
    • Open CA / Open CITS โ€” experience-based architect / technical-specialist certifications.
    • FACE, SOSA โ€” defence / aerospace open standards.
    • Open FAIR โ€” quantitative risk analysis (FAIR-based).
    • Open Agile Architecture (O-AA) โ€” agile-oriented architecture standard.
    • Dependability through Assuredness, Open Trusted Technology Provider Standard, and others.

Companion standards and notations

  • ArchiMate 3.2 โ€” the modeling language. Layers: business, application, technology, plus motivation, strategy, implementation/migration, physical. Maps onto TOGAF's content metamodel.
  • Open Agile Architecture (O-AA) โ€” The Open Group's agile-architecture standard; intended to sit alongside or within TOGAF for agile contexts.
  • IT4IT โ€” reference architecture for the IT value chain (Strategy to Portfolio, Requirement to Deploy, Request to Fulfil, Detect to Correct). Complements TOGAF.
  • BIZBOK (Business Architecture Body of Knowledge, from the Business Architecture Guild) โ€” referenced in TOGAF's business architecture Series Guide.

Adjacent and competing EA frameworks

  • Zachman Framework โ€” John Zachman, 1987. A taxonomy / ontology: a 6ร—6 matrix (What/How/Where/Who/When/Why ร— Executive/Business/Architect/Engineer/Technician/Enterprise perspectives). Classifies architecture artefacts; does not provide a method. Complementary to TOGAF.
  • FEAF / FEA (US Federal Enterprise Architecture Framework) โ€” US government EA. Reference models (performance, business, data, application, infrastructure, security). Bidirectional influence with TOGAF.
  • DoDAF (US Department of Defense Architecture Framework) โ€” defence-specific viewpoints and views. Domain-specialized.
  • MODAF (UK Ministry of Defence Architecture Framework) โ€” UK defence equivalent; largely superseded by NAF.
  • NAF (NATO Architecture Framework) โ€” NATO defence EA.
  • Gartner EA (formerly Meta Group EA) โ€” consulting-driven, business-outcome-oriented, less prescriptive on method. Competes with TOGAF in the "how do we do EA" decision.
  • Forrester EA โ€” analyst-driven EA guidance.
  • PEAF (Pragmatic Enterprise Architecture Framework) โ€” Kevin Smith; positioned as a leaner alternative.
  • Capgemini IAF (Integrated Architecture Framework) โ€” consultancy-proprietary; TOGAF-influenced.
  • SAFe (architecture parts) โ€” Scaled Agile Framework includes architecture roles (Enterprise Architect, System Architect) and concepts (architectural runway, intentional architecture vs emergent design). Tension and reconciliation with TOGAF.

Named practitioners and reference voices

TOGAF / The Open Group

  • Allen Brown โ€” long-serving former CEO of The Open Group; oversaw TOGAF 8 through 9.2.
  • Steve Nunn โ€” CEO of The Open Group (succeeded Brown); oversaw the 10th Edition restructure.
  • Chris Forde โ€” The Open Group GVP / architecture forum lead; public voice on TOGAF evolution.
  • TOGAF working group / Architecture Forum members โ€” the framework is institutionally authored; less individually attributed than, say, Zachman.

Enterprise architecture thought leaders

  • John Zachman โ€” originator of the Zachman Framework. The foundational EA-classification thinker.
  • Jeanne Ross, Peter Weill, David Robertson โ€” MIT CISR; "Enterprise Architecture as Strategy" (2006). The "operating model" framing influential on how EA connects to business strategy.
  • Roger Sessions โ€” "Simple Architectures for Complex Enterprises"; critic of EA complexity.
  • Tom Graves โ€” "Real Enterprise Architecture"; broadens EA beyond IT; critic of IT-centric TOGAF use.
  • Gerben Wierda โ€” "Mastering ArchiMate", "Chess and the Art of Enterprise Architecture"; pragmatic, critical-of-overreach voice.
  • Svyatoslav Kotusev โ€” academic researcher; "The Practice of Enterprise Architecture"; empirical critique of TOGAF-as-described vs EA-as-practiced. Influential skeptical voice.
  • Len Fehskens โ€” former Open Group EA program lead; reflective writing on what EA is for.

Agile EA

  • Scott Ambler โ€” "Disciplined Agile"; agile-architecture thinking.
  • Gregor Hohpe โ€” "The Software Architect Elevator", "Platform Strategy"; architect-as-connector-of-levels framing; bridges architecture and modern engineering.
  • Eltjo Poort โ€” "Risk- and Cost-Driven Architecture"; lightweight architecture decision-making.

Modern engineering adjacent

  • Team Topologies authors (Matthew Skelton, Manuel Pais) โ€” "enabling team" concept directly relevant to repositioning EA functions.
  • Gene Kim, Nicole Forsgren, Jez Humble โ€” DevOps research; "Accelerate"; the delivery-velocity evidence that puts pressure on heavyweight EA.

Reference resources

  • opengroup.org / togaf.org โ€” official body. Standard downloads, Series Guides, certification scheme, accredited training register.
  • The Open Group Architecture Forum โ€” the working group that maintains TOGAF; public events and webinars.
  • The Open Group conferences / events โ€” quarterly, with EA tracks.
  • Association of Enterprise Architects (AEA) โ€” professional body (linked to The Open Group); chapters, certification recognition.
  • EA-focused publications โ€” Architecture & Governance Magazine, InfoQ architecture content, Cutter Consortium EA practice.
  • ArchiMate community โ€” modeling tools (Archi โ€” open source; BiZZdesign, Sparx EA, Avolution, others โ€” commercial).

Regulatory and procurement context

  • No regulatory mandate for TOGAF. Voluntary framework.
  • Government adoption โ€” many governments (UK, Australia, others) reference TOGAF or TOGAF-derived approaches in their EA standards. Some procurement specifies TOGAF-aligned EA capability for IT-services suppliers.
  • Procurement-readiness benefit โ€” enterprise RFPs for architecture services often specify TOGAF certification (Foundation, Practitioner) for proposed staff, or Open CA for senior architects.
  • No certifiable management system โ€” unlike ISO 27001 or ISO 20000, there is no "TOGAF-certified organization." Certification is individual.

See also