Netspective Logo
Third-Party Resources

TOGAF Resources

The Open Group Architecture Framework for enterprise architecture

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

PhasePurposeKey Deliverables
PreliminaryPrepare organizationArchitecture principles, governance
A. VisionSet scope and visionArchitecture Vision document
B. BusinessDevelop business architectureBusiness Architecture
C. Information SystemsDevelop data and application architecturesData/Application Architecture
D. TechnologyDevelop technology architectureTechnology Architecture
E. OpportunitiesIdentify implementation approachProject list, roadmap
F. Migration PlanningCreate detailed implementation planMigration plan
G. ImplementationProvide architecture oversightCompliance assessments
H. Change ManagementManage architecture changesChange requests

Architecture Domains

TOGAF defines four architecture domains:

Business Architecture

ComponentDescription
Organization StructureHow the business is organized
Business ProcessesCore business workflows
Business CapabilitiesWhat the business can do
Business ServicesServices provided to customers

Data Architecture

ComponentDescription
Data EntitiesKey business data objects
Data RelationshipsHow data relates
Data GovernanceData management policies
Data LifecycleData creation to retirement

Application Architecture

ComponentDescription
Application PortfolioAll applications
Application InterfacesHow apps communicate
Application ServicesCapabilities provided
Application IntegrationIntegration patterns

Technology Architecture

ComponentDescription
InfrastructureHardware, networks
PlatformsOperating systems, middleware
Technology StandardsApproved technologies
Technology RoadmapPlatform 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

CategoryArtifacts
CatalogsLists of building blocks (Application Catalog, Technology Catalog)
MatricesRelationships between entities (Application/Data Matrix)
DiagramsVisual 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

ComponentPurpose
Architecture BoardOversee architecture decisions
Architecture ContractsAgreements between parties
Architecture ComplianceEnsure solutions align
Architecture PrinciplesGuide 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 PhaseNUP PhaseIntegration
Preliminary, AInceptionEstablish vision and principles
B, C, DElaborationDefine architecture
E, FElaboration/ConstructionPlan implementation
GConstruction/TransitionGovern implementation
HOperationsManage changes

Using TOGAF Artifacts in NUP

NUP DeliverableTOGAF Artifact
Architecture DocumentArchitecture Definition Document
System ContextContext Diagram
Component DesignApplication Architecture
Data ModelData Architecture
Infrastructure DesignTechnology Architecture

ArchiMate Modeling Language

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

Core Layers

LayerElementsPurpose
BusinessActors, Roles, ProcessesBusiness operations
ApplicationComponents, Services, DataApplications
TechnologyNodes, Devices, NetworksInfrastructure

Motivation Elements

ElementPurpose
StakeholderIndividual or organization
DriverExternal or internal condition
GoalEnd state to be achieved
RequirementStatement of need
ConstraintLimitation


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

How is this guide?

Last updated on

On this page