Skip to content
Software Architecture Guide

TOGAF

Explanation

Section titled “Explanation”

TOGAF is a framework for architecture work across a whole organization. The first version appeared in 1995. It drew mainly on TAFIM, a US Department of Defense framework for information management.

The core: the ADM. The Architecture Development Method (ADM) is the core of the framework. It is central to architecture work. See the article TOGAF Architecture Development Method.

Four domains. TOGAF is typically modeled at four levels, also called domains: Business, Application, Data and Technology. Related articles cover Business Architecture, Application Architecture, Data Architecture and Technology Architecture.

Content framework. TOGAF offers a menu of architecture products and a metamodel. A metamodel defines the kinds of things you describe and how they link. TOGAF 9 added a formal content metamodel that links TOGAF’s artifacts together. The framework does not prescribe how you document your architectures.

Enterprise Continuum. This is a classification structure for building blocks and artifacts. It has two parts: the Architecture Continuum and the Solutions Continuum. It is not the same thing as the repository.

Reference models. A reference model is a general pattern that constrains and steers system design. TOGAF includes two: the III-RM and the TRM.

Architecture capability. Part 7 covers the roles of architects in an enterprise. Its focus is governance.

Current edition. The 10th Edition is split into the TOGAF Fundamental Content and the TOGAF Series Guides.

Example

Section titled “Example”

A company wants to improve its order handling. The architects use the ADM as their working cycle. They describe the business, data, application and technology domains. They pick the artifacts they need from the content framework’s menu. They file reusable pieces in the Enterprise Continuum classification. They check designs against a reference model.

Trade-offs

Section titled “Trade-offs”

The content framework gives you a menu and a metamodel, not a fixed documentation method. You must choose your own notation and level of detail. The Enterprise Continuum only classifies material. You still need a separate repository to hold it.

Main parts of TOGAF.

Diagram source 
mindmap
  root((TOGAF))
    ADM
    Content framework
    Enterprise Continuum
      Architecture Continuum
      Solutions Continuum
    Reference models
      III-RM
      TRM
    Domains
      Business
      Data
      Application
      Technology

Checks

Section titled “Checks”
  • The document names which of the four domains (Business, Application, Data, Technology) each architecture description covers.
  • The document states which artifacts from the content framework are used, rather than assuming TOGAF prescribes a format.
  • Reference models, if used, are named and their constraining role on design is clear.
  • Architecture governance roles are described.
Section titled “Related”

Sources

Section titled “Sources”