Frontmatter
- Preface
  - This Document
  - Intended Audience
  - Keywords
- About The Open Group
  - The Open Group
- Participants
  - Architecture Forum Technical Reviewers
  - Architecture Forum Members
- Trademarks
- Acknowledgements
- Referenced Documents
Introduction
- Structure of the TOGAF Document
- Executive Overview
  - What is an enterprise? What is enterprise architecture?
  - Why do I need an enterprise architecture?
  - What specifically would prompt me to develop an enterprise architecture?
  - What is an architecture framework?
  - Why do I need TOGAF as a framework for enterprise architecture?
  - Who would benefit from using TOGAF?
  - Footnotes
Core Concepts
- What is TOGAF?
- What is Architecture in the Context of TOGAF?
- What Kind of Architecture Does TOGAF Deal With?
- Architecture Development Method
- Deliverables, Artifacts, and Building Blocks
- Enterprise Continuum
- Architecture Repository
- Establishing and Maintaining an Enterprise Architecture Capability
- Establishing the Architecture Capability as an Operational Entity
- Using TOGAF with Other Frameworks
- TOGAF Document Categorization Model
Definitions
- Abstraction
- Activity
- Actor
- Application
- Application Architecture
- Application Platform
- Application Platform Interface (API)
- Architectural Style
- Architecture
- Architecture Building Block (ABB)
- Architecture Continuum
- Architecture Development Method (ADM)
- Architecture Domain
- Architecture Framework
- Architecture Governance
- Architecture Landscape
- Architecture Principles
- Architecture View
- Architecture Vision
- Artifact
- Baseline
- Baseline Architecture
- Boundaryless Information Flow
- Building Block
- Business Architecture
- Business Domain
- Business Function
- Business Governance
- Business Service
- Capability
- Capability Architecture
- Capability Increment
- Communications and Stakeholder Management
- Concerns
- Constraint
- Data Architecture
- Deliverable
- Enterprise
- Enterprise Continuum
- Environment Management
- Financial Management
- Foundation Architecture
- Framework
- Gap
- Governance
- Information
- Information Technology (IT)
- Interoperability
- Knowledge
- Logical
- Metadata
- Metamodel
- Method
- Methodology
- Model
- Modeling
- Objective
- Organization
- Patterns
- Performance Management
- Physical
- Platform
- Platform Services
- Principle
- Quality Management
- Reference Model (RM)
- Repository
- Requirement
- Resource Management
- Roadmap
- Role
- Segment Architecture
- Service Management
- Service Orientation
- Service Oriented Architecture (SOA)
- Skill
- Solution Architecture
- Solution Building Block (SBB)
- Solutions Continuum
- Stakeholder
- Standards Information Base (SIB)
- Strategic Architecture
- Target Architecture
- Taxonomy of Architecture Views
- Technical Reference Model (TRM)
- Technology Architecture
- Transition Architecture
- View
- Viewpoint
- Work Package
Release Notes
- What's New in TOGAF 9?
  - Modular Structure
  - Content Framework
  - Extended Guidance on Adopting TOGAF within an Enterprise
  - Explicit Consideration of Architectural Styles, Including SOA and Security Architecture
  - Additional ADM Detail
- The Benefits of TOGAF 9
  - Greater Usability
  - More Focus on Holistic Enterprise Change
  - More Consistency of Output
- Mapping of the TOGAF 8.1.1 Structure to TOGAF 9
  - Part I: Introduction
  - Part II: Architecture Development Method
  - Part III: Enterprise Continuum
  - Part IV: Resource Base
- Mapping of TOGAF 9 Structure to TOGAF 8.1.1
- Using TOGAF
  - Conditions of Use
  - How Much Does TOGAF Cost?
  - Downloads
- Why Join The Open Group?
Introduction
- ADM Overview
  - The ADM, Enterprise Continuum, and Architecture Repository
  - The ADM and the Foundation Architecture
  - ADM and Supporting Guidelines and Techniques
- Architecture Development Cycle
  - Key Points
  - Basic Structure
- Adapting the ADM
- Architecture Governance
- Scoping the Architecture
  - Enterprise Scope/Focus
  - Architecture Domains
  - Vertical Scope/Level of Detail
  - Time Period
- Architecture Integration
- Summary
  - Footnotes
Preliminary Phase
- Objectives
- Approach
  - Enterprise
  - Organizational Context
  - Requirements for Architecture Work
  - Principles
  - Management Frameworks
  - Relating the Management Frameworks
  - Planning for Enterprise Architecture/Business Change Maturity Evaluation
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Scope the Enterprise Organizations Impacted
  - Confirm Governance and Support Frameworks
  - Define and Establish Enterprise Architecture Team and Organization
  - Identify and Establish Architecture Principles
  - Select and Tailor Architecture Framework(s)
  - Implement Architecture Tools
- Outputs
  - Footnotes
Phase A: Architecture Vision
- Objectives
- Approach
  - General
  - Creating the Architecture Vision
  - Business Scenarios
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Establish the Architecture Project
  - Identify Stakeholders, Concerns, and Business Requirements
  - Confirm and Elaborate Business Goals, Business Drivers, and Constraints
  - Evaluate Business Capabilities
  - Assess Readiness for Business Transformation
  - Define Scope
  - Confirm and Elaborate Architecture Principles, including Business Principles
  - Develop Architecture Vision
  - Define the Target Architecture Value Propositions and KPIs
  - Identify the Business Transformation Risks and Mitigation Activities
  - Develop Enterprise Architecture Plans and Statement of Architecture Work; Secure Approval
- Outputs
Phase B: Business Architecture
- Objectives
- Approach
  - General
  - Developing the Baseline Description
  - Business Modeling
  - Architecture Repository
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Select Reference Models, Viewpoints, and Tools
    - Determine Overall Modeling Process
    - Identify Required Service Granularity Level, Boundaries, and Contracts
    - Identify Required Catalogs of Business Building Blocks
    - Identify Required Matrices
    - Identify Required Diagrams
    - Identify Types of Requirement to be Collected
  - Develop Baseline Business Architecture Description
  - Develop Target Business Architecture Description
  - Perform Gap Analysis
  - Define Roadmap Components
  - Resolve Impacts Across the Architecture Landscape
  - Conduct Formal Stakeholder Review
  - Finalize the Business Architecture
  - Create Architecture Definition Document
- Outputs
Phase C: Information Systems Architectures
- Objectives
- Approach
  - Development
  - Implementation
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
- Outputs
Phase C: Information Systems Architectures - Data Architecture
- Objectives
- Approach
  - Key Considerations for Data Architecture
    - Data Management
    - Data Migration
    - Data Governance
  - Architecture Repository
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Select Reference Models, Viewpoints, and Tools
    - Determine Overall Modeling Process
    - Identify Required Catalogs of Data Building Blocks
    - Identify Required Matrices
    - Identify Required Diagrams
    - Identify Types of Requirement to be Collected
  - Develop Baseline Data Architecture Description
  - Develop Target Data Architecture Description
  - Perform Gap Analysis
  - Define Roadmap Components
  - Resolve Impacts Across the Architecture Landscape
  - Conduct Formal Stakeholder Review
  - Finalize the Data Architecture
  - Create Architecture Definition Document
- Outputs
Phase C: Information Systems Architectures - Application Architecture
- Objectives
- Approach
  - Architecture Repository
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Select Reference Models, Viewpoints, and Tools
    - Determine Overall Modeling Process
    - Identify Required Catalogs of Application Building Blocks
    - Identify Required Matrices
    - Identify Required Diagrams
    - Identify Types of Requirement to be Collected
  - Develop Baseline Application Architecture Description
  - Develop Target Application Architecture Description
  - Perform Gap Analysis
  - Define Roadmap Components
  - Resolve Impacts Across the Architecture Landscape
  - Conduct Formal Stakeholder Review
  - Finalize the Application Architecture
  - Create Architecture Definition Document
- Outputs
Phase D: Technology Architecture
- Objectives
- Approach
  - Architecture Repository
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Select Reference Models, Viewpoints, and Tools
    - Determine Overall Modeling Process
    - Identify Required Catalogs of Technology Building Blocks
    - Identify Required Matrices
    - Identify Required Diagrams
    - Identify Types of Requirement to be Collected
    - Select Services
  - Develop Baseline Technology Architecture Description
  - Develop Target Technology Architecture Description
  - Perform Gap Analysis
  - Define Roadmap Components
  - Resolve Impacts Across the Architecture Landscape
  - Conduct Formal Stakeholder Review
  - Finalize the Technology Architecture
  - Create Architecture Definition Document
- Outputs
- Postscript
Phase E: Opportunities & Solutions
- Objectives
- Approach
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Determine/Confirm Key Corporate Change Attributes
    - Create an Implementation Factor Assessment and Deduction Matrix
    - Assess Transition Capabilities of Corporate and Partner Organizations
    - Assess Transition Capabilities of the Enterprise and IT Organization
  - Determine Business Constraints for Implementation
    - Review Corporate Strategic Plan
    - Review the Enterprise Architecture Maturity Assessment
    - Review Corporate Line-of-Business Strategic Plans
  - Review and Consolidate Gap Analysis Results from Phases B to D
    - Create a Consolidated Gaps, Solutions, and Dependencies Matrix
    - Review the Phase B, C, and D Gap Analysis Results
    - Rationalize the Consolidated Gaps, Solutions, and Dependencies Matrix
  - Review IT Requirements from a Functional Perspective
    - Assess the IT Requirements from a Functional Perspective
    - Determine Issues Associated with Functional Integration
  - Consolidate and Reconcile Interoperability Requirements
    - Consolidate Interoperability Requirements
    - Reconcile Interoperability Requirements with Potential Solutions
  - Refine and Validate Dependencies
    - Assess Business Dependencies
    - Assess Information Dependencies
    - Assess Workflow Dependencies
    - Assess IT Dependencies
    - Assess Foundation Dependencies and Interim Capabilities
    - Rationalize and Consolidate Dependencies
  - Confirm Readiness and Risk for Business Transformation
  - Formulate High-Level Implementation and Migration Strategy
    - Determine Overall Strategic Implementation Direction
    - Determine an Implementation Approach
  - Identify and Group Major Work Packages
    - Identify Major Work Packages
    - Analyze the Work Packages with Respect to Business Transformation
  - Identify Transition Architectures
    - Identify Transition Architecture and Capability Increments
    - Group Portfolios and Projects into Increments
  - Create Portfolio and Project Charters and Update the Architectures
    - Create the Portfolio Charters
    - Create the Project Charters
    - Create the Transition Architectures
    - Conduct Overall Architecture Updates
- Outputs
Phase F: Migration Planning
- Objectives
- Approach
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Confirm Management Framework Interactions for Implementation and Migration Plan
    - Align Implementation and Migration Plan with Business/Capability Planning
    - Examine Business Transformation Aspects
    - Assess the Synchronization of the Enterprise Architecture and Existing IT Planning Framework
    - Align Implementation and Migration Plan with the Project Management Framework
    - Align Implementation and Migration Plan with the Operations Management Framework
    - Establish Plans for Enterprise Architecture Management
  - Assign a Business Value to Each Project
    - Confirm Organizational Business Value, Return on Investment, and Performance Measurement Parameters
    - Assign Risk to the Projects and Project Increments
    - Assign Business Value to the Projects and Project Increments
    - Determine Continuous Business Value Assessment Technique
  - Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicles
    - Determine Personnel and Infrastructure (Capital) Costs
    - Determine Operations and Maintenance Costs
    - Determine Transition Architecture/Project Increment Timings
    - Assess Best Delivery Vehicle
  - Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
    - Derive Cost Benefit Analysis for the Migration Projects
    - Validate the Risk Assessment
    - Prioritize the Projects
  - Confirm Transition Architecture Increments/Phases and Update Architecture Definition Document
    - Confirm Transition Architecture Time-Spans
    - Confirm Business Value Delivered by the Increments
    - Update Previously Created Architecture Deliverables
  - Generate the Architecture Implementation Roadmap (Time-Lined) and Migration Plan
    - Confirm Enterprise Architecture Evolution
    - Enterprise Architecture State Evolution
    - Detailed Implementation and Migration Plan
    - Incorporate Project Schedules
    - Plan the Migration Details
  - Establish the Architecture Evolution Cycle and Document Lessons Learned
    - Confirm the Enterprise Architecture Evolution Cycle
    - Confirm the Enterprise Architecture Management Processes
    - Document Lessons Learned
- Outputs
Phase G: Implementation Governance
- Objectives
- Approach
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Confirm Scope and Priorities for Deployment with Development Management
  - Identify Deployment Resources and Skills
  - Guide Development of Solutions Deployment
  - Perform Enterprise Architecture Compliance Reviews
  - Implement Business and IT Operations
  - Perform Post-Implementation Review and Close the Implementation
- Outputs
Phase H: Architecture Change Management
- Objectives
- Approach
  - Drivers for Change
  - Enterprise Architecture Change Management Process
  - Guidelines for Maintenance versus Architecture Redesign
- Inputs
  - Reference Materials External to the Enterprise
  - Non-Architectural Inputs
  - Architectural Inputs
- Steps
  - Establish Value Realization Process
  - Deploy Monitoring Tools
  - Manage Risks
  - Provide Analysis for Architecture Change Management
  - Develop Change Requirements to Meet Performance Targets
  - Manage Governance Process
  - Activate the Process to Implement Change
- Outputs
ADM Architecture Requirements Management
- Objectives
- Approach
  - General
  - Resources
    - Business Scenarios
    - Volere Requirements Specification Template
    - Requirements Tools
- Inputs
- Steps
- Outputs
  - Footnotes
Introduction
- Guidelines for Adapting the ADM Process
- Techniques for Architecture Development
Applying Iteration to the ADM
- Overview
- Iteration Cycles
- Two Styles of Architecture Definition
- Mapping TOGAF Phases to Iteration Cycles
Applying the ADM at Different Enterprise Levels
- Overview
- Classes of Architecture Engagement
- Developing Architectures at Different Levels
- ADM Cycle Approaches
  - Using Iterations within a Single ADM Cycle
  - Using a Hierarchy of ADM Processes
Security Architecture and the ADM
- Overview
- Introduction
- Guidance on Security for the Architecture Domains
- ADM Architecture Requirements Management
  - Is our security good?
  - Nothing useful can be said about a security measure outside the context of an application, or a system and its environment
- Preliminary Phase
  - Define and document applicable regulatory and security policy requirements
  - Identify a security architect or security architecture team
  - Identify first-order assumptions and boundary conditions
  - Security Inputs
  - Security Outputs
- Phase A: Architecture Vision
  - Obtain management support for security measures
  - Define necessary security-related management sign-off milestones of this architecture development cycle
  - Determine and document applicable disaster recovery or business continuity plans/requirements
  - Identify and document the anticipated physical/business/regulatory environment(s) in which the system(s) will be deployed
  - Determine and document the criticality of the system: safety-critical/mission-critical/non-critical
  - Security Inputs
  - Security Outputs
- Phase B: Business Architecture
  - Determine who are the legitimate actors who will interact with the product/service/process
  - Assess and baseline current security-specific business processes (enhancement of existing objective)
  - Determine whom/how much it is acceptable to inconvenience in utilizing security measures
  - Identify and document interconnecting systems beyond project control
  - Determine the assets at risk if something goes wrong - "What are we trying to protect?"
  - Determine the cost (both qualitative and quantitative) of asset loss/impact in failure cases
  - Identify and document the ownership of assets
  - Determine and document appropriate security forensic processes
  - Identify the criticality of the availability and correct operation of the overall service
  - Determine and document how much security (cost) is justified by the threats and the value of the assets at risk
  - Reassess and confirm Architecture Vision decisions
  - Assess alignment or conflict of identified security policies with business goals
  - Determine "what can go wrong?"
  - Security Inputs
  - Security Outputs
- Phase C: Information Systems Architectures
  - Assess and baseline current security-specific architecture elements (enhancement of existing objective)
  - Identify safe default actions and failure states
  - Identify and evaluate applicable recognized guidelines and standards
  - Revisit assumptions regarding interconnecting systems beyond project control
  - Determine and document the sensitivity or classification level of information stored/created/used
  - Identify and document custody of assets
  - Identify the criticality of the availability and correct operation of each function
  - Determine the relationship of the system under design with existing business disaster/continuity plans
  - Identify what aspects of the system must be configurable to reflect changes in policy/business environment/access control
  - Identify lifespan of information used as defined by business needs and regulatory requirements
  - Determine approaches to address identified risks:
  - Identify actions/events that warrant logging for later review or triggering forensic processes
  - Identify and document requirements for rigor in proving accuracy of logged events (non-repudiation)
  - Identify potential/likely avenues of attack
  - Determine "what can go wrong?"
  - Security Inputs
  - Security Outputs
- Phase D: Technology Architecture
  - Assess and baseline current security-specific technologies (enhancement of existing objective)
  - Revisit assumptions regarding interconnecting systems beyond project control
  - Identify and evaluate applicable recognized guidelines and standards
  - Identify methods to regulate consumption of resources
  - Engineer a method by which the efficacy of security measures will be measured and communicated on an ongoing basis
  - Identify the trust (clearance) level of:
  - Identify minimal privileges required for any entity to achieve a technical or business objective
  - Identify mitigating security measures, where justified by risk assessment
  - Determine "what can go wrong?"
  - Security Inputs
  - Security Outputs
- Phase E: Opportunities & Solutions
  - Identify existing security services available for re-use
  - Engineer mitigation measures addressing identified risks
  - Evaluate tested and re-usable security software and security system resources
  - Identify new code/resources/assets that are appropriate for re-use
  - Determine "what can go wrong?"
- Phase F: Migration Planning
  - Assess the impact of new security measures upon other new components or existing leveraged systems
  - Implement assurance methods by which the efficacy of security measures will be measured and communicated on an ongoing basis
  - Identify correct secure installation parameters, initial conditions, and configurations
  - Implement disaster recovery and business continuity plans or modifications
  - Determine "what can go wrong?"
- Phase G: Implementation Governance
  - Establish architecture artifact, design, and code reviews and define acceptance criteria for the successful implementation of the findings
  - Implement methods and procedures to review evidence produced by the system that reflects operational stability and adherence to security policies
  - Implement necessary training to ensure correct deployment, configuration, and operations of security-relevant subsystems and components; ensure awareness training of all users and non-privileged operators of the system and/or its components
  - Determine "what has gone wrong?"
- Phase H: Architecture Change Management
  - Determine "what has gone wrong?"
  - Incorporate security-relevant changes to the environment into the requirements for future enhancement (enhancement of existing objective)
- References
Using TOGAF to Define & Govern SOAs
- Overview
- Introduction
- Business-Led SOA Community
- Business- & Developer-Led SOA Communities
- Complexities Arising from SOA
- How Enterprise Architecture Supports SOA
- SOA and TOGAF
- Guidelines for Service Contract Definition
  - Service Qualities and TOGAF
  - Purpose of a Service Contract
  - Service Governance Considerations
    - Service Contracts
    - Service Policies
    - Service Lifecycle Management
    - Service Metadata
- Content and Structure of a Service Contract
- Service Contract Template
Architecture Principles
- Introduction
- Characteristics of Architecture Principles
- Components of Architecture Principles
- Developing Architecture Principles
  - Qualities of Principles
- Applying Architecture Principles
- Example Set of Architecture Principles
  - Business Principles
  - Data Principles
  - Application Principles
  - Technology Principles
Stakeholder Management
- Introduction
- Approach to Stakeholder Management
- Steps in the Stakeholder Management Process
  - Identify Stakeholders
  - Classify Stakeholder Positions
  - Determine Stakeholder Management Approach
  - Tailor Engagement Deliverables
- Template Stakeholder Map
Architecture Patterns
- Introduction
  - Background
  - Content of a Pattern
  - Terminology
    - Architecture Patterns and Design Patterns
    - Patterns and the Architecture Continuum
    - Patterns and Views
    - Patterns and Business Scenarios
  - Architecture Patterns in Use
- US Treasury Architecture Development Guidance (TADG)
  - TADG Pattern Content
  - TADG Architecture Patterns
- IBM Patterns for e-Business
- Some Pattern Resources
Business Scenarios
- Introduction
- Benefits of Business Scenarios
- Creating the Business Scenario
  - Overall Process
  - Gathering
  - Analyzing
  - Reviewing
- Contents of a Business Scenario
- Contributions to the Business Scenario
- Business Scenarios and the TOGAF ADM
- Guidelines on Developing Business Scenarios
  - General Guidelines
  - Questions to Ask for Each Area
    - Identifying, Documenting, and Ranking the Problem
    - Identifying the Business & Technical Environment, and Documenting in Models
    - Identifying and Documenting Objectives
    - Identifying Human Actors and their Place in the Business Model
    - Identifying Computer Actors and their Place in the Technology Model
    - Documenting Roles, Responsibilities, Measures of Success, Required Scripts
    - Checking for Fitness-for-Purpose, and refining if necessary
- Guidelines on Business Scenario Documentation
  - Textual Documentation
  - Business Scenario Models
- Guidelines on Goals and Objectives
  - Importance of Goals
  - Importance of SMART Objectives
    - Example of Making Objectives SMART
  - Categories of Goals and Objectives
    - Goal: Improve Business Process Performance
    - Goal: Decrease Costs
    - Goal: Improve Business Operations
    - Goal: Improve Management Efficacy
    - Goal: Reduce Risk
    - Goal: Improve Effectiveness of IT Organization
    - Goal: Improve User Productivity
    - Goal: Improve Portability and Scalability
    - Goal: Improve Interoperability
    - Goal: Increase Vendor Independence
    - Goal: Reduce Lifecycle Costs
    - Goal: Improve Security
    - Goal: Improve Manageability
- Summary
Gap Analysis
- Introduction
- Suggested Steps
- Example
Migration Planning Techniques
- Implementation Factor Assessment and Deduction Matrix
- Consolidated Gaps, Solutions, and Dependencies Matrix
- Architecture Definition Increments Table
- Enterprise Architecture State Evolution Table
- Business Value Assessment Technique
Interoperability Requirements
- Overview
- Defining Interoperability
- Enterprise Operating Model
- Refining Interoperability
- Determining Interoperability Requirements
- Reconciling Interoperability Requirements with Potential Solutions
- Summary
  - Footnotes
Business Transformation Readiness Assessment
- Introduction
  - Business Transformation Enablement Program (BTEP)
- Determine Readiness Factors
- Present Readiness Factors
- Assess Readiness Factors
  - Readiness Factor Vision
  - Readiness Factor Rating
  - Readiness Factor Risks & Actions
- Readiness and Migration Planning
- Marketing the Implementation Plan
- Conclusion
  - Footnotes
Risk Management
- Introduction
- Risk Classification
- Risk Identification
- Initial Risk Assessment
- Risk Mitigation and Residual Risk Assessment
- Conduct Residual Risk Assessment
- Risk Monitoring and Governance (Phase G)
- Summary
Capability-Based Planning
- Overview
- Capability-Based Planning Paradigm
- Concept of Capability-Based Planning
  - Capability Dimensions
  - Capability Increments
- Capabilities in an Enterprise Architecture Context
- Summary
Introduction
- Overview
- Content Metamodel
- Content Framework and the TOGAF ADM
- Structure of Part IV
Content Metamodel
- Overview
- Content Metamodel Vision and Concepts
  - Core Content Metamodel Concepts
    - Core and Extension Content
    - Core Metamodel Entities
    - Catalog, Matrix, and Diagram Concept
  - Overview of the Content Metamodel
- Content Metamodel in Detail
  - Core Content Metamodel
  - Core Architecture Artifacts
  - Full Content Metamodel
- Content Metamodel Extensions
  - Governance Extensions
    - Purpose
    - Required Changes to the Metamodel
  - Services Extensions
    - Purpose
    - Required Changes to the Metamodel
  - Process Modeling Extensions
    - Purpose
    - Required Changes to the Metamodel
  - Data Extensions
    - Purpose
    - Required Changes to the Metamodel
  - Infrastructure Consolidation Extensions
    - Purpose
    - Required Changes to the Metamodel
  - Motivation Extensions
    - Purpose
    - Required Changes to the Metamodel
- Content Metamodel Objects
- Content Metamodel Attributes
- Metamodel Relationships
  - Footnotes
Architectural Artifacts
- Basic Concepts
  - Simple Example of a Viewpoint and View
- Developing Views in the ADM
  - General Guidelines
  - View Creation Process
- Views, Tools, and Languages
  - Overview
- Views and Viewpoints
  - Example of Views and Viewpoints
  - Views and Viewpoints in Enterprise Architecture
  - Need for a Common Language and Interoperable Tools for Architecture Description
- Conclusions
- Taxonomy of Architecture Viewpoints
- Viewpoints in the Preliminary Phase
  - Principles Catalog
- Viewpoints in Phase A
  - Stakeholder Map Matrix
  - Value Chain Diagram
  - Solution Concept Diagram
- Viewpoints in Phase B
  - Organization/Actor Catalog
  - Driver/Goal/Objective Catalog
  - Role Catalog
  - Business Service/Function Catalog
  - Location Catalog
  - Process/Event/Control/Product Catalog
  - Contract/Measure Catalog
  - Business Interaction Matrix
  - Actor/Role Matrix
  - Business Footprint Diagram
  - Business Service/Information Diagram
  - Functional Decomposition Diagram
  - Product Lifecycle Diagram
  - Goal/Objective/Service Diagram
  - Business Use-Case Diagram
  - Organization Decomposition Diagram
  - Process Flow Diagram
  - Event Diagram
- Viewpoints in the Phase C Data Architecture
  - Data Entity/Data Component Catalog
  - Data Entity/Business Function Matrix
  - System/Data Matrix
  - Class Diagram
  - Data Dissemination Diagram
  - Data Security Diagram
  - Class Hierarchy Diagram
  - Data Migration Diagram
  - Data Lifecycle Diagram
- Viewpoints in the Phase C Application Architecture
  - Application Portfolio Catalog
  - Interface Catalog
  - System/Organization Matrix
  - Role/System Matrix
  - System/Function Matrix
  - Application Interaction Matrix
  - Application Communication Diagram
  - Application and User Location Diagram
  - System Use-Case Diagram
  - Enterprise Manageability Diagram
  - Process/System Realization Diagram
  - Software Engineering Diagram
  - Application Migration Diagram
  - Software Distribution Diagram
- Viewpoints in Phase D
  - Technology Standards Catalog
  - Technology Portfolio Catalog
  - System/Technology Matrix
  - Environments and Locations Diagram
  - Platform Decomposition Diagram
  - Processing Diagram
  - Networked Computing/Hardware Diagram
  - Communications Engineering Diagram
- Viewpoints in Phase E
  - Project Context Diagram
  - Benefits Diagram
- Viewpoints for Requirements Management
  - Requirements Catalog
- Developing a Business Architecture View
  - Stakeholders and Concerns
  - Developing the View
  - Key Issues
- Developing an Enterprise Security View
  - Stakeholders and Concerns
  - Developing the View
  - Basic Concepts
    - Information Domains
    - Strict Isolation
    - Absolute Protection
  - Security Generic Architecture View
  - Security Services Allocation
    - Operating System Services
    - Network Services
    - System Security Management Services
- Developing a Software Engineering View
  - Stakeholders and Concerns
    - Development Approach
    - Software Modularity and Re-Use
    - Portability
    - Migration and Interoperability
  - Key Issues
    - Data-Intensive versus Information-Intensive Software Systems
    - Achieving Interoperability
    - Software Tiers
    - Two-Tier
    - Three-Tier
    - Five-Tier
    - Some Uses of a Data Access Tier
    - One Possible Instantiation of a DAI
    - DAIs Enable Flexibility
    - Distribution
    - Infrastructure Bus
  - Conclusion
- Developing a System Engineering View
  - Stakeholders and Concerns
  - Key Issues
    - Client/Server Model
    - Master/Slave and Hierarchic Models
    - Peer-to-Peer Model
    - Distributed Object Management Model
- Developing a Communications Engineering View
  - Stakeholders and Concerns
  - Key Issues
    - Communications Infrastructure
    - Communications Models
    - The OSI Reference Model
    - Communications Framework
    - Allocation of Services to Components
- Developing a Data Flow View
  - Stakeholders and Concerns
  - Developing the View
  - Key Issues
    - Database Management Systems
    - Database Models
    - Distributed DBMSs
    - Distributed Heterogeneous DBMSs
    - Data Dictionary/Directory Systems
    - Data Administration
    - Repository
    - Database Administration
    - Data Security
- Developing an Enterprise Manageability View
  - Stakeholders and Concerns
  - Developing the View
  - Key Issues
- Developing an Acquirer View
  - Stakeholders and Concerns
  - Developing the View
  - Key Issues
  - Footnotes
Architecture Deliverables
- Introduction
- Deliverable Descriptions
  - Architecture Building Blocks
  - Architecture Contract
    - Purpose
    - Content
  - Architecture Definition Document
    - Purpose
    - Content
  - Architecture Principles
    - Purpose
    - Content
  - Architecture Repository
    - Purpose
    - Content
  - Architecture Requirements Specification
    - Purpose
    - Content
  - Architecture Roadmap
    - Purpose
    - Content
  - Architecture Vision
    - Purpose
    - Content
  - Business Principles, Business Goals, and Business Drivers
    - Purpose
    - Content
  - Capability Assessment
    - Purpose
    - Content
  - Change Request
    - Purpose
    - Content
  - Communications Plan
    - Purpose
    - Content
  - Compliance Assessment
    - Purpose
    - Content
  - Implementation and Migration Plan
    - Purpose
    - Content
  - Implementation Governance Model
    - Purpose
    - Content
  - Organizational Model for Enterprise Architecture
    - Purpose
    - Content
  - Request for Architecture Work
  - Requirements Impact Assessment
    - Purpose
    - Content
  - Solution Building Blocks
  - Statement of Architecture Work
    - Purpose
    - Content
  - Tailored Architecture Framework
    - Purpose
    - Content
  - Transition Architecture
    - Purpose
    - Content
Building Blocks
- Overview
- Introduction to Building Blocks
  - Overview
  - Generic Characteristics
  - Architecture Building Blocks
    - Characteristics
    - Specification Content
  - Solution Building Blocks
    - Characteristics
    - Specification Content
- Building Blocks and the ADM
  - Basic Principles
    - Building Blocks in Architecture Design
    - Building Block Design
  - Building Block Specification Process in the ADM
- Building Blocks Example
  - Introduction
  - Structure
  - Background to the Example
  - Identifying Building Block Scope
  - Identifying Building Block Requirements and Constraints
    - Assumptions of Required Technical Functionality
  - Architecture Modeling
    - Customer Information System Building Block Specification
    - Description
    - Mandated Building Blocks
    - Map to Business Organization Entities and Policies
  - Opportunity Identification
  - Building Block Re-Use Level
  - Footnotes
Introduction
- Introduction
- Structure of Part V
Enterprise Continuum
- Overview
- Enterprise Continuum and Architecture Re-Use
- Constituents of the Enterprise Continuum
- Enterprise Continuum in Detail
  - Architecture Continuum
    - Foundation Architecture
    - Common Systems Architectures
    - Industry Architectures
    - Organization-Specific Architectures
  - Solutions Continuum
    - Foundation Solutions
    - Common Systems Solutions
    - Industry Solutions
    - Organization-Specific Solutions
- Relationship between the Enterprise Continuum and TOGAF ADM
- Enterprise Continuum and Your Organization
  - Relationships
  - Your Enterprise
Architecture Partitioning
- Overview
- Characteristics of Solutions
- Characteristics of Architectures
- Applying Classification to Create Partitioned Architectures
  - Partitioning the Architecture Landscape to Understand the State of the Enterprise
  - Partitioning Reference Models to Encourage Good Practice and Re-Use
  - Enforce Corporate Policy though Compliance with Standards
  - Activities within the Preliminary Phase
  - Activities within Phases A to F
  - Activities within Phases G and H
  - Content Aggregation and Integration
  - Footnotes
Architecture Repository
- Overview
- Architecture Landscape
- Reference Library
  - Overview
- Standards Information Base
  - Overview
  - Types of Standard
  - Standards Lifecycle
  - Standards Classification within the Standards Information Base
- Governance Log
  - Overview
  - Contents of the Governance Log
Tools for Architecture Development
- Overview
- Issues in Tool Standardization
- Evaluation Criteria and Guidelines
  - Tool Criteria
    - Functionality
    - Key Features and Functions
    - Intuitiveness/Ease-of-Use Factors
    - Organizational Compatibility Factors
    - Tool Capacity/Scalability Constraints
    - Architecture of the Tool
    - Full Lifecycle Support
    - Interoperability Factors
    - Financial Considerations
    - Vendor Factors
  - General Pointers
Foundation Architecture: Technical Reference Model
- Concepts
  - Role of the TRM in the Foundation Architecture
  - TRM Components
  - Other TRMs
- High-Level Breakdown
  - Overview
  - Portability and Interoperability
- TRM in Detail
  - Introduction
  - TRM Entities and Interfaces
  - Application Software
    - Business Applications
    - Infrastructure Applications
  - Application Platform
    - Platform Concept
    - Extending the TRM
    - Interfaces Between Services
    - Future Developments
  - Communications Infrastructure
  - Application Platform Interface
  - Communications Infrastructure Interface
  - Qualities
- Application Platform - Taxonomy
  - Basic Principles
  - Application Platform Service Categories
    - Object-Oriented Provision of Services
  - Application Platform Service Qualities
    - Principles
    - Taxonomy of Service Qualities
- Detailed Platform Taxonomy
  - Data Interchange Services
  - Data Management Services
  - Graphics and Imaging Services
  - International Operation Services
  - Location and Directory Services
  - Network Services
  - Operating System Services
  - Software Engineering Services
  - Transaction Processing Services
  - User Interface Services
  - Security Services
  - System and Network Management Services
  - Object-Oriented Provision of Services
Integrated Information Infrastructure Reference Model
- Basic Concepts
  - Background
  - Components of the Model
  - Relationship to Other parts of TOGAF
  - Key Business and Technical Drivers
    - Problem Space: The Need for Boundaryless Information Flow
    - Solution Space: The Need for Integrated Information Infrastructure
  - Status of the III-RM
- High-Level View
  - Derivation of the III-RM from the TRM
  - High-Level III-RM Graphic
  - Components of the High-Level III-RM
- Detailed Taxonomy
  - Detailed III-RM Graphic
  - Business Applications
    - Information Provider Applications
    - Brokerage Applications
    - Information Consumer Applications
  - Infrastructure Applications
    - Development Tools
    - Business Modeling Tools
    - Design Modeling Tools
    - Implementation and Construction Tools
    - Data Modeling Tools
    - Deployment Tools
    - Libraries
    - Management Utilities
    - Operations, Administration, and Management (OA&M) Utilities
    - Quality of Service Manager Utilities
    - Copy Management Utilities
    - Storage Management Utilities
  - Application Platform
    - Software Engineering Services
    - Security Services
    - Location and Directory Services
    - Human Interaction Services
    - Data Interchange Services
    - Data Management Services
    - Additional Operating System Services
  - Qualities
  - Footnotes
Introduction
- Overview
- Structure of Part VII
Establishing an Architecture Capability
- Overview
- Phase A: Architecture Vision
- Phase B: Business Architecture
- Phase C: Information Systems Architecture - Data
- Phase C: Information Systems Architecture - Application
- Phase D: Technology Architecture
- Phase E: Opportunities & Solutions
- Phase F: Migration Planning
- Phase G: Implementation Governance
- Phase H: Architecture Change Management
- Requirements Management
Architecture Board
- Role
- Responsibilities
- Setting Up the Architecture Board
  - Triggers
  - Size of the Board
  - Board Structure
- Operation of the Architecture Board
  - General
  - Preparation
  - Agenda
    - Minutes of Previous Meeting
    - Requests for Change
    - Dispensations
    - Compliance Assessments
    - Dispute Resolution
    - Architecture Strategy and Direction Documentation
    - Actions Assigned
    - Contract Documentation Management
    - Any Other Business (AOB)
    - Schedule of Meetings
Architecture Compliance
- Introduction
- Terminology: The Meaning of Architecture Compliance
- Architecture Compliance Reviews
  - Purpose
  - Timing
  - Governance and Personnel Scenarios
- Architecture Compliance Review Process
  - Overview
  - Roles
  - Steps
- Architecture Compliance Review Checklists
  - Hardware and Operating System Checklist
  - Software Services and Middleware Checklist
  - Applications Checklists
    - Infrastructure (Enterprise Productivity) Applications
    - Business Applications
    - Application Integration Approach
  - Information Management Checklists
    - Data Values
    - Data Definition
    - Security/Protection
    - Hosting, Data Types, and Sharing
    - Common Services
    - Access Method
  - Security Checklist
  - System Management Checklist
  - System Engineering/Overall Architecture Checklists
    - General
    - Processors/Servers/Clients
    - Client
    - Application Server
    - Data Server
    - COTS (where applicable)
  - System Engineering/Methods & Tools Checklist
- Architecture Compliance Review Guidelines
  - Tailoring the Checklists
  - Conducting Architecture Compliance Reviews
Architecture Contracts
- Role
- Contents
  - Statement of Architecture Work
  - Contract between Architecture Design and Development Partners
  - Contract between Architecting Function and Business Users
- Relationship to Architecture Governance
Architecture Governance
- Introduction
  - Levels of Governance within the Enterprise
  - Nature of Governance
    - Governance: A Generic Perspective
    - Characteristics of Governance
  - Technology Governance
  - IT Governance
    - An IT Controls Framework - COBIT
  - Architecture Governance: Overview
    - Architecture Governance Characteristics
    - Architecture Governance as a Board-Level Responsibility
    - TOGAF and Architecture Governance
- Architecture Governance Framework
  - Architecture Governance Framework - Conceptual Structure
    - Key Concepts
    - Key Architecture Governance Processes
    - Policy Management and Take-On
    - Compliance
    - Dispensation
    - Monitoring and Reporting
    - Business Control
    - Environment Management
  - Architecture Governance Framework - Organizational Structure
    - Overview
    - Key Areas
    - Operational Benefits
- Architecture Governance in Practice
  - Architecture Governance - Key Success Factors
  - Elements of an Effective Architecture Governance Strategy
    - Architecture Governance and Corporate Politics
  - Footnotes
Architecture Maturity Models
- Overview
- Background
- US DoC ACMM Framework
  - Overview
  - Elements of the ACMM
  - Example: Enterprise Architecture Process Maturity Levels
    - Level 0: None
    - Level 1: Initial
    - Level 2: Under Development
    - Level 3: Defined
    - Level 4: Managed
    - Level 5: Optimizing
- Capability Maturity Models Integration (CMMI)
  - Introduction
  - SCAMPI Method
- Conclusions
  - Footnotes
Architecture Skills Framework
- Introduction
- Need for an Enterprise Architecture Skills Framework
  - Definitional Rigor
  - Basis of an Internal Architecture Practice
- Goals/Rationale
  - Certification of Enterprise Architects
  - Specific Benefits
- Enterprise Architecture Role and Skill Categories
  - Overview
  - TOGAF Roles
  - Categories of Skills
  - Proficiency Levels
- Enterprise Architecture Role and Skill Definitions
  - Generic Skills
  - Business Skills & Methods
  - Enterprise Architecture Skills
  - Program or Project Management Skills
  - IT General Knowledge Skills
  - Technical IT Skills
  - Legal Environment
- Generic Role and Skills of the Enterprise Architect
  - Generic Role
  - Characterization in Terms of the Enterprise Continuum
  - Key Characteristics of an Enterprise Architect
    - Skills and Experience in Producing Designs
    - Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines
    - Method-Driven Approach to Execution
    - Full Project Scope Experience
    - Leadership
    - Personal and Professional Skills
    - Skills and Experience in One or More Industries
- Conclusions
Glossary of Supplementary Definitions
- Access Control (AC)
- Ada
- Application Component
- Application Software
- Availability
- Batch Processing
- Business System
- Catalog
- Client
- COBIT
- Communications Network
- Communications Node
- Communications System
- Composite Application
- Configuration Management
- Connectivity Service
- Contract
- Control
- CxO
- Data Dictionary
- Data Element
- Data Entity
- Data Interchange Service
- Data Management Service
- Database
- Database Management System
- Directory Service
- Distributed Database
- Driver
- End User
- Enterprise Resource Planning (ERP) System
- Event
- External Environment Interface (EEI)
- FORTRAN
- Functional Decomposition
- Goal
- Guideline
- Hardware
- Human Computer Interface (HCI)
- Information Domain
- Information System (IS)
- Information System Service
- Interaction
- Interaction Model
- Interface
- ITIL
- Key Performance Indicator (KPI)
- Lifecycle
- Location
- Logical Application Component
- Logical Data Component
- Logical Technology Component
- Managing Successful Programs (MSP)
- Matrix
- Measure
- Metaview
- Multimedia Service
- Open Specifications
- Open System
- Operational Governance
- Operating System Service
- Organization Unit
- Packaged Services
- Physical Application Component
- Physical Data Component
- Physical Technology Component
- Portability
- Portfolio
- PRINCE2
- Process
- Product
- Profile
- Profiling
- Program
- Project
- Risk Management
- Scalability
- Security
- Server
- Service
- Service Quality
- SMART
- Supplier Management
- System
- System and Network Management Service
- System Stakeholder
- Technology Component
- Time Period
- Transaction
- Transaction Sequence
- Use-Case
- User
- User Interface Service
Abbreviations
INDEX