TOGAF Primer & Modelling Guide — Enterprise Architecture with Linked.Archi¶

TOGAF gives enterprise architects a common metamodel and method, but its content usually lives in documents and diagrams that cannot be queried or checked for consistency. Formalizing the TOGAF Enterprise Metamodel as semantic assets makes entities, relationships, and ADM phases machine-readable — so you can trace goals to work packages and applications to technology across the whole estate.

This guide introduces the TOGAF framework as formalized in Linked.Archi, explains how its concepts map to semantic assets, and demonstrates practical modelling through a worked example.

TOGAF Concepts¶

What is TOGAF?¶

TOGAF (The Open Group Architecture Framework) is the most widely adopted enterprise architecture framework globally. Published by The Open Group, it provides a comprehensive approach for designing, planning, implementing, and governing enterprise IT architecture.

TOGAF consists of: - Architecture Development Method (ADM) — the iterative process for developing architecture - Enterprise Metamodel — the entity types and relationships that constitute architecture content - Architecture Content Framework — how content is structured, classified, and delivered - Architecture Capability Framework — how to establish and operate an EA practice

"TOGAF is a framework — a detailed method and a set of supporting tools — for developing an enterprise architecture." — The Open Group

References: - TOGAF Standard — the official specification - The Open Group Architecture Forum

The Architecture Development Method (ADM)¶

The ADM is TOGAF's core — an iterative cycle of phases for developing and managing architecture:

graph TD
    P["Preliminary<br/>Framework & Principles"] --> A
    A["Phase A<br/>Architecture Vision"] --> B
    B["Phase B<br/>Business Architecture"] --> C
    C["Phase C<br/>Information Systems<br/>(Data + Application)"] --> D
    D["Phase D<br/>Technology Architecture"] --> E
    E["Phase E<br/>Opportunities & Solutions"] --> F
    F["Phase F<br/>Migration Planning"] --> G
    G["Phase G<br/>Implementation Governance"] --> H
    H["Phase H<br/>Architecture Change Management"] --> A
    RM["Requirements<br/>Management"] --- A
    RM --- B
    RM --- C
    RM --- D

    style P fill:#4A90D9,stroke:#333,color:#fff
    style A fill:#4A90D9,stroke:#333,color:#fff
    style B fill:#E8A838,stroke:#333,color:#000
    style C fill:#7BC67B,stroke:#333,color:#000
    style D fill:#9B59B6,stroke:#333,color:#fff
    style E fill:#E74C3C,stroke:#333,color:#fff
    style F fill:#E74C3C,stroke:#333,color:#fff
    style G fill:#E74C3C,stroke:#333,color:#fff
    style H fill:#E74C3C,stroke:#333,color:#fff
    style RM fill:#95A5A6,stroke:#333,color:#000

Phase	Focus	Key Outputs
Preliminary	Framework setup, principles	Architecture principles, governance framework
A — Vision	Scope, stakeholders, vision	Architecture Vision, Statement of Work
B — Business	Business architecture	Business capability map, process models
C — Information Systems	Data + Application architecture	Data models, application portfolio
D — Technology	Technology architecture	Technology standards, deployment models
E — Opportunities	Solution alternatives	Transition architectures, work packages
F — Migration	Implementation roadmap	Migration plan, architecture roadmap
G — Governance	Implementation oversight	Compliance assessments, change requests
H — Change Management	Architecture evolution	Change impact assessments

The Enterprise Metamodel¶

The TOGAF Enterprise Metamodel defines the entity types that constitute architecture content. It is organized into six domains:

graph TD
    subgraph Motivation["Motivation"]
        Principle(["Principle"])
        Requirement(["Requirement"])
        Constraint(["Constraint"])
        Driver(["Driver"])
        Goal(["Goal"])
        Objective(["Objective"])
    end

    subgraph Business["Business Architecture"]
        OrgUnit["Organization Unit"]
        Actor["Actor"]
        Role["Role"]
        BusCap(["Business Capability"])
        Process{{"Process"}}
        BusService{{"Business Service"}}
        Product["Product"]
    end

    subgraph Data["Data Architecture"]
        DataEntity["Data Entity"]
        LogicalData["Logical Data Component"]
        PhysicalData["Physical Data Component"]
    end

    subgraph Application["Application Architecture"]
        LogicalApp["Logical App Component"]
        PhysicalApp["Physical App Component"]
        AppService{{"Application Service"}}
    end

    subgraph Technology["Technology Architecture"]
        LogicalTech["Logical Tech Component"]
        PhysicalTech["Physical Tech Component"]
        TechService{{"Technology Service"}}
    end

    subgraph Implementation["Implementation & Migration"]
        WorkPackage{{"Work Package"}}
        ValueStream{{"Value Stream"}}
    end

    style Motivation fill:#FFE0B2,stroke:#333,color:#000
    style Business fill:#E8A838,stroke:#333,color:#000
    style Data fill:#7BC67B,stroke:#333,color:#000
    style Application fill:#7BC67B,stroke:#333,color:#000
    style Technology fill:#9B59B6,stroke:#333,color:#fff
    style Implementation fill:#E74C3C,stroke:#333,color:#fff

Key Relationships¶

Relationship	Meaning	Example
supports	One element provides support for another	Application Service supports Business Service
realizes	Physical component realizes a logical element	Physical App realizes Logical App
governs	Principle/constraint governs an element	Principle governs Application Component
accesses	Process/function accesses data	Process accesses Data Entity
communicatesWith	Data exchange between applications	App A communicates with App B
decomposesInto	Element breaks into finer-grained parts	Capability decomposes into sub-capabilities
dependsOn	Element depends on another	Service depends on Technology Component
contains	Containment relationship	Organization Unit contains Roles
isRealizedThrough	Abstract realized through implementation	Goal is realized through Work Package

Semantic Assets¶

Asset Set¶

frameworks/togaf/
├── togaf-metamodel.ttl             ← Entry point: arch:Metamodel
├── togaf-vp.ttl                    ← Viewpoints (catalogs, matrices, diagrams by ADM phase)
├── togaf-deliverable-templates.ttl ← 5 deliverable templates
├── togaf-crossmappings.ttl         ← TOGAF ↔ ArchiMate mappings
├── 10/
│   ├── togaf10-onto.ttl            ← TOGAF 10 Enterprise Metamodel (OWL)
│   └── togaf10-tax.ttl             ← SKOS taxonomy
└── 9.2/
    ├── togaf9.2-onto.ttl           ← TOGAF 9.2 Content Metamodel (OWL)
    └── togaf9.2-tax.ttl            ← SKOS taxonomy

Concept-to-Asset Mapping¶

TOGAF Concept	Semantic Representation	File
Entity types (Organization Unit, Process, etc.)	`owl:Class rdfs:subClassOf arch:Element`	`togaf10-onto.ttl`
Domain groupings (BusinessArchitectureElement, etc.)	`owl:Class` with `arch:isAbstractClass true`	`togaf10-onto.ttl`
Relationships (supports, realizes, governs)	`owl:ObjectProperty` with `arch:domainIncludes`/`arch:rangeIncludes`	`togaf10-onto.ttl`
ADM phase classification	`skos:ConceptScheme`	`togaf10-tax.ttl`
Viewpoints (catalogs, matrices, diagrams)	`arch:Viewpoint` with `arch:includesConcept`	`togaf-vp.ttl`
Deliverable templates	`arch:DeliverableTemplate`	`togaf-deliverable-templates.ttl`
ArchiMate alignment	`skos:exactMatch` / `skos:closeMatch`	`togaf-crossmappings.ttl`
Entry point	`arch:Metamodel` instance	`togaf-metamodel.ttl`

Abstract vs Concrete Classes¶

Abstract (not instantiable)	Concrete (palette items)
`togaf:MotivationElement`	Principle, Requirement, Constraint, Assumption, Gap, Driver, Goal, Objective, Measure, Course of Action
`togaf:BusinessArchitectureElement`	Organization Unit, Actor, Role, Function, Process, Event, Business Service, Business Capability, Product, Contract, Control, Location
`togaf:DataArchitectureElement`	Data Entity, Logical Data Component, Physical Data Component
`togaf:ApplicationArchitectureElement`	Logical Application Component, Physical Application Component, Application Service
`togaf:TechnologyArchitectureElement`	Logical Technology Component, Physical Technology Component, Technology Service
`togaf:ImplementationElement`	Work Package, Capability, Value Stream

Cross-Language Mapping (TOGAF ↔ ArchiMate)¶

The togaf-crossmappings.ttl file provides formal alignments between TOGAF and ArchiMate concepts:

togaf:BusinessCapability skos:exactMatch am4:Capability .
togaf:Process skos:exactMatch am4:BusinessProcess .
togaf:BusinessService skos:closeMatch am4:BusinessService .
togaf:LogicalApplicationComponent skos:closeMatch am4:ApplicationComponent .
togaf:PhysicalApplicationComponent skos:closeMatch am4:ApplicationComponent .
togaf:Product skos:exactMatch am4:Product .

This enables SPARQL queries that traverse both frameworks seamlessly.

Worked Example: Atlas Global Bank¶

Prerequisites¶

Load the TOGAF semantic assets:

core/core-onto.ttl                              # Foundation
frameworks/togaf/10/togaf10-onto.ttl            # Enterprise Metamodel entities
frameworks/togaf/10/togaf10-tax.ttl             # SKOS taxonomy
frameworks/togaf/togaf-vp.ttl                   # Viewpoints
frameworks/togaf/togaf-deliverable-templates.ttl # Deliverable templates
frameworks/togaf/togaf-crossmappings.ttl        # ArchiMate alignment
frameworks/togaf/togaf-metamodel.ttl            # Metamodel manifest

About Atlas Global Bank¶

Atlas Global Bank is a multinational financial services group headquartered in Frankfurt, operating retail banking, corporate banking, and wealth management across 20 countries. Atlas is executing a cloud-first digital transformation programme to modernise its core banking platform while maintaining regulatory compliance across multiple jurisdictions.

The complete, validatable example model is available at examples/atlas-bank/atlas-model.ttl.

Model File Header¶

Start the model with this header, which binds it to the TOGAF 10 metamodel:

@prefix owl:     <http://www.w3.org/2002/07/owl#> .
@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .
@prefix skos:    <http://www.w3.org/2004/02/skos/core#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix arch:    <https://meta.linked.archi/core#> .
@prefix togaf:   <https://meta.linked.archi/togaf/onto#> .
@prefix togafvp: <https://meta.linked.archi/togaf/viewpoints#> .
@prefix :        <https://model.atlas-bank.example/> .

:AtlasModel
    a                          arch:Model ;
    skos:prefLabel             "Atlas Global Bank — Enterprise Architecture Model"@en ;
    arch:modelConformsToMetamodel <https://meta.linked.archi/togaf/metamodel#TOGAF10> ;
    dcterms:created            "2025-06-27"^^xsd:date ;
.

Element Patterns¶

Declare each architecture element with its TOGAF type, label, and definition. The patterns below cover all six metamodel domains — paste and rename to match your own estate.

Motivation Elements¶

:CloudFirstPrinciple
    a              togaf:Principle ;
    skos:prefLabel "Cloud-First Principle"@en ;
    skos:definition "All new systems must be deployed on cloud infrastructure unless regulatory constraints prevent it."@en ;
.

:PSD2Compliance
    a              togaf:Requirement ;
    skos:prefLabel "PSD2 Open Banking Compliance"@en ;
    skos:definition "All payment services must expose APIs compliant with PSD2 directive by Q4 2026."@en ;
.

:DigitalDisruption
    a              togaf:Driver ;
    skos:prefLabel "Digital Disruption from Neobanks"@en ;
    skos:definition "Challenger banks capturing 15% of retail deposits in key markets."@en ;
.

:ReduceTimeToMarket
    a              togaf:Goal ;
    skos:prefLabel "Reduce Time-to-Market"@en ;
    skos:definition "Reduce product launch cycle from 18 months to 3 months by 2027."@en ;
.

Business Architecture Elements¶

:RetailBanking
    a              togaf:OrganizationUnit ;
    skos:prefLabel "Retail Banking Division"@en ;
    skos:definition "Division serving 12 million individual customers across 20 markets."@en ;
.

:PaymentProcessing
    a              togaf:BusinessCapability ;
    skos:prefLabel "Payment Processing"@en ;
    skos:definition "The ability to execute, clear, and settle payment transactions across all channels and payment schemes."@en ;
.

:LoanOrigination
    a              togaf:Process ;
    skos:prefLabel "Loan Origination Process"@en ;
    skos:definition "End-to-end process from application through credit assessment to disbursement."@en ;
.

:AccountManagementService
    a              togaf:BusinessService ;
    skos:prefLabel "Account Management Service"@en ;
    skos:definition "Service enabling customers to open, manage, and close accounts across all channels."@en ;
.

:CustomerData
    a              togaf:BusinessInformation ;
    skos:prefLabel "Customer Master Data"@en ;
    skos:definition "Core customer identity, KYC, and relationship data across all products."@en ;
.

Data and Application Architecture Elements¶

:CustomerEntity
    a              togaf:DataEntity ;
    skos:prefLabel "Customer"@en ;
    skos:definition "A person or organisation that holds or applies for banking products."@en ;
.

:TransactionEntity
    a              togaf:DataEntity ;
    skos:prefLabel "Transaction"@en ;
    skos:definition "A financial operation that changes the balance of one or more accounts."@en ;
.

:CoreBankingLogical
    a              togaf:LogicalApplicationComponent ;
    skos:prefLabel "Core Banking System (Logical)"@en ;
    skos:definition "Logical application managing accounts, transactions, and product lifecycle."@en ;
.

:CoreBankingPhysical
    a              togaf:PhysicalApplicationComponent ;
    skos:prefLabel "Temenos Transact"@en ;
    skos:definition "Physical realisation of core banking on Temenos Transact platform deployed on AWS."@en ;
.

:OpenBankingAPI
    a              togaf:ApplicationService ;
    skos:prefLabel "Open Banking API Gateway"@en ;
    skos:definition "PSD2-compliant API gateway exposing account and payment services to third parties."@en ;
.

Technology Architecture Elements¶

:CloudPlatformLogical
    a              togaf:LogicalTechnologyComponent ;
    skos:prefLabel "Cloud Platform (Logical)"@en ;
    skos:definition "Logical cloud infrastructure providing compute, storage, and networking."@en ;
.

:AWSPlatform
    a              togaf:PhysicalTechnologyComponent ;
    skos:prefLabel "AWS EU (Frankfurt)"@en ;
    skos:definition "Amazon Web Services EU-Central-1 region hosting Atlas production workloads."@en ;
.

:ContainerOrchestration
    a              togaf:TechnologyService ;
    skos:prefLabel "Container Orchestration Service"@en ;
    skos:definition "Kubernetes-based container orchestration for microservices deployment."@en ;
.

Implementation Elements¶

:CoreBankingMigration
    a              togaf:WorkPackage ;
    skos:prefLabel "Core Banking Migration Programme"@en ;
    skos:definition "3-year programme to migrate from legacy mainframe to cloud-native core banking."@en ;
.

:PaymentsValueStream
    a              togaf:ValueStream ;
    skos:prefLabel "Payments Value Stream"@en ;
    skos:definition "End-to-end value delivery from payment initiation through clearing to settlement."@en ;
.

Relationship Patterns¶

Wire the elements together with TOGAF relationships — governance, realization, support, and dependencies:

## Motivation governs architecture
:CloudFirstPrinciple togaf:governs :CoreBankingPhysical .
:PSD2Compliance togaf:governs :OpenBankingAPI .

## Goals realized through work packages
:ReduceTimeToMarket togaf:isRealizedThrough :CoreBankingMigration .

## Business architecture relationships
:RetailBanking togaf:contains :PaymentProcessing .
:LoanOrigination togaf:accesses :CustomerEntity .
:AccountManagementService togaf:supports :RetailBanking .
:PaymentProcessing togaf:decomposesInto :DomesticPayments .
:PaymentProcessing togaf:decomposesInto :CrossBorderPayments .

## Application realizes business
:OpenBankingAPI togaf:supports :AccountManagementService .
:CoreBankingLogical togaf:supports :PaymentProcessing .
:CoreBankingPhysical togaf:realizes :CoreBankingLogical .

## Technology supports application
:AWSPlatform togaf:realizes :CloudPlatformLogical .
:ContainerOrchestration togaf:supports :CoreBankingPhysical .

## Application communicates
:OpenBankingAPI togaf:communicatesWith :CoreBankingPhysical .

## Dependencies
:CoreBankingPhysical togaf:dependsOn :ContainerOrchestration .
:OpenBankingAPI togaf:dependsOn :CoreBankingPhysical .

Architecture Landscape¶

graph TD
    subgraph Motivation["Motivation & Principles"]
        D["Digital Disruption<br/>(Driver)"]
        G(["Reduce Time-to-Market<br/>(Goal)"])
        P["Cloud-First Principle"]
        R["PSD2 Compliance<br/>(Requirement)"]
    end

    subgraph Business["Business Architecture"]
        RB["Retail Banking<br/>(Org Unit)"]
        PP(["Payment Processing<br/>(Capability)"])
        AMS{{"Account Mgmt Service"}}
    end

    subgraph Application["Application Architecture"]
        CBL["Core Banking<br/>(Logical)"]
        CBP["Temenos Transact<br/>(Physical)"]
        API{{"Open Banking API"}}
    end

    subgraph Technology["Technology Architecture"]
        AWS["AWS EU Frankfurt<br/>(Physical)"]
        K8S{{"Container Orchestration"}}
    end

    subgraph Implementation["Implementation"]
        WP{{"Core Banking Migration"}}
    end

    D --> G
    G -->|"realized through"| WP
    P -->|"governs"| CBP
    R -->|"governs"| API
    RB -->|"contains"| PP
    AMS -->|"supports"| RB
    CBL -->|"supports"| PP
    API -->|"supports"| AMS
    CBP -->|"realizes"| CBL
    AWS -->|"realizes"| CLP["Cloud Platform (Logical)"]
    K8S -->|"supports"| CBP
    API -->|"communicates"| CBP

    style Motivation fill:#FFE0B2,stroke:#333,color:#000
    style Business fill:#E8A838,stroke:#333,color:#000
    style Application fill:#7BC67B,stroke:#333,color:#000
    style Technology fill:#9B59B6,stroke:#333,color:#fff
    style Implementation fill:#E74C3C,stroke:#333,color:#fff

Views and Viewpoints¶

Declare views that conform to TOGAF viewpoints — catalogs, matrices, and roadmap diagrams:

:AtlasBusinessCapabilityView
    a arch:View ;
    skos:prefLabel "Atlas Business Capability Map"@en ;
    arch:viewConformsToViewpoint togafvp:BusinessServiceFunctionCatalog ;
.

:AtlasApplicationPortfolioView
    a arch:View ;
    skos:prefLabel "Atlas Application Portfolio"@en ;
    arch:viewConformsToViewpoint togafvp:ApplicationPortfolioCatalog ;
.

:AtlasMigrationRoadmapView
    a arch:View ;
    skos:prefLabel "Atlas Migration Roadmap"@en ;
    arch:viewConformsToViewpoint togafvp:ArchitectureRoadmap ;
.

Comparison Articles¶

For detailed comparisons of TOGAF with other frameworks in Linked.Archi:

EA Frameworks Compared — Broader comparison across TOGAF, Zachman, EA on a Page, and others
Zachman Framework vs EA on a Page — Two classification lenses on the same artifacts

Disclaimer: This is a community semantic representation of the TOGAF framework for interoperability purposes. It is not produced by, endorsed by, or affiliated with The Open Group. "TOGAF" is a registered trademark of The Open Group.