Skip to main content

Command Palette

Search for a command to run...

quick reference

TOGAF ADM Cheat Sheet

Quick reference card for the TOGAF Architecture Development Method phases, deliverables, and key activities.

TOGAF ADM Cheat Sheet

Phase Summary

PhaseNamePurposeKey Deliverable
PrelimPreliminaryEstablish EA capabilityArchitecture Principles
AArchitecture VisionDefine scope and visionStatement of Architecture Work
BBusiness ArchitectureModel business capabilitiesBusiness Architecture Document
CInformation SystemsModel data and applicationsData & Application Architecture
DTechnology ArchitectureModel infrastructureTechnology Architecture Document
EOpportunities & SolutionsDefine work packagesImplementation Strategy
FMigration PlanningPrioritize and sequenceArchitecture Roadmap
GImplementation GovernanceOversee implementationCompliance Reports
HArchitecture Change MgmtManage changesChange Requests
RMRequirements ManagementManage requirementsRequirements Repository

Phase Details

Preliminary Phase

PURPOSE: Establish the architecture capability

INPUTS                          OUTPUTS
• Business principles           • Organizational Model for EA
• Business goals               • Tailored Architecture Framework
• Governance framework         • Architecture Principles
                               • Architecture Repository

Phase A: Architecture Vision

PURPOSE: Develop high-level vision and secure approval

INPUTS                          OUTPUTS
• Request for Architecture      • Architecture Vision document
• Business principles          • Statement of Architecture Work
• Architecture principles      • Refined business goals
• Enterprise Continuum         • Stakeholder Map

Phase B: Business Architecture

PURPOSE: Develop target Business Architecture

INPUTS                          OUTPUTS
• Architecture Vision          • Business Architecture Document
• Architecture Repository      • Gap Analysis (Business)
• Business principles          • Candidate Roadmap Components
                               • Updated Architecture Repository

Phase C: Information Systems Architecture

PURPOSE: Develop target Data and Application Architecture

C.1 DATA ARCHITECTURE          C.2 APPLICATION ARCHITECTURE
• Data entities                • Application portfolio
• Data relationships           • Application interactions
• Data management              • Integration requirements
• Data governance              • Application services

OUTPUTS: Data Architecture Document, Application Architecture Document

Phase D: Technology Architecture

PURPOSE: Develop target Technology Architecture

INPUTS                          OUTPUTS
• Architecture Vision          • Technology Architecture Document
• Application Architecture     • Gap Analysis (Technology)
• Data Architecture           • Candidate Roadmap Components
• Technology principles        • Updated Architecture Repository

Phase E: Opportunities & Solutions

PURPOSE: Generate implementation approach

INPUTS                          OUTPUTS
• Gap analysis (all domains)   • Project list
• Candidate components         • Work packages
• Architecture Repository      • Transition Architectures
                               • Implementation Factor Assessment

Phase F: Migration Planning

PURPOSE: Finalize implementation roadmap

INPUTS                          OUTPUTS
• Implementation Strategy      • Architecture Roadmap
• Work packages               • Implementation and Migration Plan
• Transition Architectures    • Implementation Governance Model

Phase G: Implementation Governance

PURPOSE: Architectural oversight of implementation

ACTIVITIES
• Confirm scope and priorities
• Identify resources and skills
• Guide solution development
• Perform compliance reviews
• Conduct post-implementation review

Phase H: Architecture Change Management

PURPOSE: Manage architecture changes

CHANGE TYPES
• Simplification → Minor changes
• Enhancement   → Architecture Board review
• Strategic     → New architecture cycle

TRIGGERS: Technology changes, business changes, lessons learned

Key Artifacts by Domain

Business Architecture

  • Capability Map
  • Value Stream Map
  • Organization Map
  • Business Process Models
  • Business Use Cases

Data Architecture

  • Conceptual Data Model
  • Logical Data Model
  • Data Entity/Function Matrix
  • Data Lifecycle Diagram
  • Data Security Diagram

Application Architecture

  • Application Portfolio Catalog
  • Application Communication Diagram
  • Application/Function Matrix
  • Application Migration Diagram
  • Application Use-Case Diagram

Technology Architecture

  • Technology Standards Catalog
  • Technology Portfolio Catalog
  • Environments and Locations Diagram
  • Platform Decomposition Diagram
  • Network Computing Diagram

ADM Iteration Patterns

ARCHITECTURE LANDSCAPE (Enterprise-wide)
├── Scope: All domains, conceptual level
├── Cycle: 12-24 months
└── Focus: Strategic direction

ARCHITECTURE CAPABILITY (Domain-specific)
├── Scope: Single domain, detailed
├── Cycle: 3-6 months
└── Focus: Capability development

ARCHITECTURE GOVERNANCE (Project-level)
├── Scope: Solution architecture
├── Cycle: Project-aligned
└── Focus: Compliance

Governance Checkpoints

CheckpointPhaseFocus
Initial ReviewAScope and vision alignment
Architecture ReviewB-DDomain architecture compliance
Solution ReviewE-FWork package feasibility
Implementation ReviewGDelivery compliance
Post-ImplementationHOutcomes assessment

Quick Decision Guide

Which phase to start with?

  • New EA capability → Preliminary
  • New initiative → Phase A
  • Business change → Phase B
  • Technology refresh → Phase D
  • Project compliance → Phase G

When to iterate?

  • Major requirements change → Return to A
  • Domain gap identified → Return to B/C/D
  • Implementation issue → Phase E/F adjustment
  • Ongoing change → Phase H triggers

Common Deliverable Templates

Architecture Principles Template

PRINCIPLE: [Name]
Statement:  [Concise statement of the principle]
Rationale:  [Why this principle is important]
Implications:
• [Impact on architecture decisions]
• [Impact on implementation]
• [Constraints introduced]

Gap Analysis Template

DOMAIN: [Business/Data/Application/Technology]

| Baseline | Target | Gap | Priority | Action |
|----------|--------|-----|----------|--------|
| Current  | Future | Δ   | H/M/L    | Work   |

Architecture Decision Record

ADR-[###]: [Decision Title]
Status: [Proposed | Accepted | Deprecated]
Context: [Why is this decision needed?]
Decision: [What is the decision?]
Consequences: [What are the implications?]

Sources