TOGAF Resources

TOGAF (The Open Group Architecture Framework) provides a comprehensive approach to designing, planning, implementing, and governing enterprise information architecture. It complements NUP by providing enterprise-level architecture guidance.

TOGAF Overview

TOGAF is a framework for enterprise architecture that provides methods and tools for assisting in the acceptance, production, use, and maintenance of an enterprise architecture.

Architecture Development Method (ADM)

┌─────────────────────────────────────────────────────────────────────────────┐
│                    TOGAF ADM CYCLE                                           │
└─────────────────────────────────────────────────────────────────────────────┘

                         ┌───────────────┐
                         │   Preliminary │
                         │    Phase      │
                         └───────┬───────┘
                                 │
                                 ▼
                    ┌────────────────────────┐
           ┌───────│    A. Architecture     │───────┐
           │       │       Vision           │       │
           │       └────────────────────────┘       │
           │                                        │
           ▼                                        ▼
    ┌─────────────┐                          ┌─────────────┐
    │B. Business  │                          │H. Arch      │
    │ Architecture│    ┌────────────────┐    │ Change Mgmt │
    └──────┬──────┘    │ Requirements   │    └──────┬──────┘
           │           │  Management    │           │
           ▼           └────────────────┘           ▲
    ┌─────────────┐                          ┌─────────────┐
    │C. Info Sys  │                          │G. Implement │
    │ Architecture│                          │ Governance  │
    └──────┬──────┘                          └──────┬──────┘
           │                                        │
           ▼                                        │
    ┌─────────────┐    ┌─────────────┐    ┌─────────────┐
    │D. Technology│───▶│E. Opportunit│───▶│F. Migration │
    │ Architecture│    │ & Solutions │    │  Planning   │
    └─────────────┘    └─────────────┘    └─────────────┘

ADM Phases

Phase	Purpose	Key Deliverables
Preliminary	Prepare organization	Architecture principles, governance
A. Vision	Set scope and vision	Architecture Vision document
B. Business	Develop business architecture	Business Architecture
C. Information Systems	Develop data and application architectures	Data/Application Architecture
D. Technology	Develop technology architecture	Technology Architecture
E. Opportunities	Identify implementation approach	Project list, roadmap
F. Migration Planning	Create detailed implementation plan	Migration plan
G. Implementation	Provide architecture oversight	Compliance assessments
H. Change Management	Manage architecture changes	Change requests

Architecture Domains

TOGAF defines four architecture domains:

Business Architecture

Component	Description
Organization Structure	How the business is organized
Business Processes	Core business workflows
Business Capabilities	What the business can do
Business Services	Services provided to customers

Data Architecture

Component	Description
Data Entities	Key business data objects
Data Relationships	How data relates
Data Governance	Data management policies
Data Lifecycle	Data creation to retirement

Application Architecture

Component	Description
Application Portfolio	All applications
Application Interfaces	How apps communicate
Application Services	Capabilities provided
Application Integration	Integration patterns

Technology Architecture

Component	Description
Infrastructure	Hardware, networks
Platforms	Operating systems, middleware
Technology Standards	Approved technologies
Technology Roadmap	Platform evolution

TOGAF Content Framework

Architecture Building Blocks (ABBs)

┌─────────────────────────────────────────────────────────────────────────────┐
│                    BUILDING BLOCKS                                           │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                              │
│  Architecture Building Blocks (ABBs)                                         │
│  ┌─────────────────────────────────────────────────────────────────────┐   │
│  │ Define WHAT functionality is required                                │   │
│  │ Technology-independent                                               │   │
│  │ Examples: Payment Service, Customer Repository                       │   │
│  └─────────────────────────────────────────────────────────────────────┘   │
│                              │                                              │
│                              ▼                                              │
│  Solution Building Blocks (SBBs)                                            │
│  ┌─────────────────────────────────────────────────────────────────────┐   │
│  │ Define HOW functionality is implemented                              │   │
│  │ Technology-specific                                                  │   │
│  │ Examples: Stripe API, PostgreSQL Database                            │   │
│  └─────────────────────────────────────────────────────────────────────┘   │
│                                                                              │
└─────────────────────────────────────────────────────────────────────────────┘

Architecture Artifacts

Category	Artifacts
Catalogs	Lists of building blocks (Application Catalog, Technology Catalog)
Matrices	Relationships between entities (Application/Data Matrix)
Diagrams	Visual representations (System Context, Data Flow)

Enterprise Continuum

The Enterprise Continuum classifies architectures from generic to specific:

Generic ────────────────────────────────────────────────▶ Specific

┌─────────────┐  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│  Foundation │  │  Common     │  │  Industry   │  │Organization │
│ Architecture│  │  Systems    │  │ Architecture│  │ Specific    │
│             │  │ Architecture│  │             │  │             │
│ TRM, IIIRM  │  │ SOA, Cloud  │  │ Healthcare  │  │ Your        │
│             │  │             │  │ Finance     │  │ Enterprise  │
└─────────────┘  └─────────────┘  └─────────────┘  └─────────────┘

Architecture Governance

Governance Framework

Component	Purpose
Architecture Board	Oversee architecture decisions
Architecture Contracts	Agreements between parties
Architecture Compliance	Ensure solutions align
Architecture Principles	Guide decision-making

Architecture Principles Template

# Architecture Principle: [Name]

## Statement
[Clear statement of the principle]

## Rationale
[Why this principle is important]

## Implications
[What this means in practice]
- Implication 1
- Implication 2

## Example Principles
- Reuse over build
- Buy over build
- Technology independence
- Data is an asset
- Security by design

TOGAF and NUP Integration

Mapping ADM to NUP Phases

TOGAF ADM Phase	NUP Phase	Integration
Preliminary, A	Inception	Establish vision and principles
B, C, D	Elaboration	Define architecture
E, F	Elaboration/Construction	Plan implementation
G	Construction/Transition	Govern implementation
H	Operations	Manage changes

Using TOGAF Artifacts in NUP

NUP Deliverable	TOGAF Artifact
Architecture Document	Architecture Definition Document
System Context	Context Diagram
Component Design	Application Architecture
Data Model	Data Architecture
Infrastructure Design	Technology Architecture

ArchiMate Modeling Language

ArchiMate is an open standard for enterprise architecture modeling that works with TOGAF.

Core Layers

Layer	Elements	Purpose
Business	Actors, Roles, Processes	Business operations
Application	Components, Services, Data	Applications
Technology	Nodes, Devices, Networks	Infrastructure

Motivation Elements

Element	Purpose
Stakeholder	Individual or organization
Driver	External or internal condition
Goal	End state to be achieved
Requirement	Statement of need
Constraint	Limitation

Compliance

This section fulfills ISO 13485 requirements for design planning (7.3.2), design interfaces (7.3.1), and documentation requirements (4.2.3), and ISO 27001 requirements for secure architecture (A.8.27), information security in project management (A.5.8), and documented operating procedures (A.5.37).

View full compliance matrix