• Frontmatter
• 1. Introduction
  • 1.1 Structure of this Document
  • 1.2 Structure of the TOGAF Library
  • 1.3 Executive Overview
    • What is an enterprise?
    • Why is an Enterprise Architecture needed?
    • What are the benefits of an Enterprise Architecture?
    • What specifically would prompt the development of an Enterprise Architecture?
    • What is an architecture framework?
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
    • Who would benefit from using the TOGAF standard?
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.1 Conditions of Use
    • 1.4.2 How Much Does the TOGAF Standard Cost?
    • 1.4.3 Downloads
  • 1.5 Why Join The Open Group?
    • Footnotes
• 2. Core Concepts
  • 2.1 What is the TOGAF Standard?
  • 2.2 What is Architecture in the Context of the TOGAF Standard?
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
  • 2.4 Architecture Development Method
  • 2.5 Deliverables, Artifacts, and Building Blocks
  • 2.6 Enterprise Continuum
  • 2.7 Architecture Repository
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
  • 2.9 Establishing the Architecture Capability as an Operational Entity
  • 2.10 Using the TOGAF Standard with Other Frameworks
• 3. Definitions
  • 3.1 Abstraction
  • 3.2 Actor
  • 3.3 Application Architecture
  • 3.4 Application Component
  • 3.5 Application Platform
  • 3.6 Architectural Style
  • 3.7 Architecture
  • 3.8 Architecture Building Block (ABB)
  • 3.9 Architecture Continuum
  • 3.10 Architecture Development Method (ADM)
  • 3.11 Architecture Domain
  • 3.12 Architecture Framework
  • 3.13 Architecture Governance
  • 3.14 Architecture Landscape
  • 3.15 Architecture Model
  • 3.16 Architecture Principle
  • 3.17 Architecture View
  • 3.18 Architecture Viewpoint
  • 3.19 Architecture Vision
  • 3.20 Artifact
  • 3.21 Baseline
  • 3.22 Boundaryless Information FlowTM
  • 3.23 Building Block
  • 3.24 Business Architecture
  • 3.25 Business Capability
  • 3.26 Business Function
  • 3.27 Business Governance
  • 3.28 Business Model
  • 3.29 Business Service
  • 3.30 Capability
  • 3.31 Capability Architecture
  • 3.32 Capability Increment
  • 3.33 Communications and Stakeholder Management
  • 3.34 Concern
  • 3.35 Course of Action
  • 3.36 Data Architecture
  • 3.37 Deliverable
  • 3.38 Enterprise
  • 3.39 Enterprise Continuum
  • 3.40 Foundation Architecture
  • 3.41 Framework
  • 3.42 Gap
  • 3.43 Governance
  • 3.44 Information
  • 3.45 Information System Service
  • 3.46 Information Technology (IT)
  • 3.47 Interoperability
  • 3.48 Logical
  • 3.49 Metadata
  • 3.50 Metamodel
  • 3.51 Method
  • 3.52 Modeling
  • 3.53 Model Kind
  • 3.54 Objective
  • 3.55 Organization Map
  • 3.56 Pattern
  • 3.57 Physical
  • 3.58 Principle
  • 3.59 Reference Model (RM)
  • 3.60 Repository
  • 3.61 Requirement
  • 3.62 Roadmap
  • 3.63 Role
  • 3.64 Segment Architecture
  • 3.65 Service
  • 3.66 Service Orientation
  • 3.67 Service-Oriented Architecture (SOA)
  • 3.68 Service Portfolio
  • 3.69 Solution Architecture
  • 3.70 Solution Building Block (SBB)
  • 3.71 Solutions Continuum
  • 3.72 Stakeholder
  • 3.73 Standards Information Base (SIB)
  • 3.74 Strategic Architecture
  • 3.75 Target Architecture
  • 3.76 Taxonomy of Architecture Views
  • 3.77 Technology Architecture
  • 3.78 Technology Component
  • 3.79 Technology Service
  • 3.80 Transition Architecture
  • 3.81 Value Stream
  • 3.82 View
  • 3.83 Viewpoint
  • 3.84 Viewpoint Library
  • 3.85 Work Package
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.1 The ADM, Enterprise Continuum, and Architecture Repository
    • 4.1.2 The ADM and the Foundation Architecture
    • 4.1.3 ADM and Supporting Guidelines and Techniques
  • 4.2 Architecture Development Cycle
    • 4.2.1 Key Points
    • 4.2.2 Basic Structure
  • 4.3 Adapting the ADM
  • 4.4 Architecture Governance
  • 4.5 Scoping the Architecture
    • 4.5.1 Breadth
    • 4.5.2 Depth
    • 4.5.3 Time Period
    • 4.5.4 Architecture Domains
  • 4.6 Architecture Integration
  • 4.7 Summary
• 5. Preliminary Phase
  • 5.1 Objectives
  • 5.2 Inputs
    • 5.2.1 Reference Materials External to the Enterprise
    • 5.2.2 Non-Architectural Inputs
    • 5.2.3 Architectural Inputs
  • 5.3 Steps
    • 5.3.1 Scope the Enterprise Organizations Impacted
    • 5.3.2 Confirm Governance and Support Frameworks
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization
    • 5.3.4 Identify and Establish Architecture Principles
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
  • 5.4 Outputs
  • 5.5 Approach
    • 5.5.1 Enterprise
    • 5.5.2 Organizational Context
    • 5.5.3 Requirements for Architecture Work
    • 5.5.4 Principles
    • 5.5.5 Management Frameworks
    • 5.5.6 Relating the Management Frameworks
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 6. Phase A: Architecture Vision
  • 6.1 Objectives
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
    • 6.2.2 Non-Architectural Inputs
    • 6.2.3 Architectural Inputs
  • 6.3 Steps
    • 6.3.1 Establish the Architecture Project
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 6.3.4 Evaluate Capabilities
    • 6.3.5 Assess Readiness for Business Transformation
    • 6.3.6 Define Scope
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
    • 6.3.8 Develop Architecture Vision
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval
  • 6.4 Outputs
  • 6.5 Approach
    • 6.5.1 General
    • 6.5.2 Creating the Architecture Vision
• 7. Phase B: Business Architecture
  • 7.1 Objectives
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
    • 7.2.2 Non-Architectural Inputs
    • 7.2.3 Architectural Inputs
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks
      • 7.3.1.4 Identify Required Matrices
      • 7.3.1.5 Identify Required Diagrams
      • 7.3.1.6 Identify Types of Requirement to be Collected
    • 7.3.2 Develop Baseline Business Architecture Description
    • 7.3.3 Develop Target Business Architecture Description
    • 7.3.4 Perform Gap Analysis
    • 7.3.5 Define Candidate Roadmap Components
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
    • 7.3.7 Conduct Formal Stakeholder Review
    • 7.3.8 Finalize the Business Architecture
    • 7.3.9 Create the Architecture Definition Document
  • 7.4 Outputs
  • 7.5 Approach
    • 7.5.1 General
    • 7.5.2 Developing the Baseline Description
    • 7.5.3 Applying Business Capabilities
    • 7.5.4 Applying Value Streams
    • 7.5.5 Applying the Organization Map
    • 7.5.6 Applying Modeling Techniques
    • 7.5.7 Architecture Repository
• 8. Phase C: Information Systems Architectures
  • 8.1 Objectives
  • 8.2 Approach
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.1 Objectives
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
    • 9.2.2 Non-Architectural Inputs
    • 9.2.3 Architectural Inputs
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks
      • 9.3.1.3 Identify Required Matrices
      • 9.3.1.4 Identify Required Diagrams
      • 9.3.1.5 Identify Types of Requirement to be Collected
    • 9.3.2 Develop Baseline Data Architecture Description
    • 9.3.3 Develop Target Data Architecture Description
    • 9.3.4 Perform Gap Analysis
    • 9.3.5 Define Candidate Roadmap Components
    • 9.3.6 Resolve Impacts Across the Architecture Landscape
    • 9.3.7 Conduct Formal Stakeholder Review
    • 9.3.8 Finalize the Data Architecture
    • 9.3.9 Create the Architecture Definition Document
  • 9.4 Outputs
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.1 Data Management
      • 9.5.1.2 Data Migration
      • 9.5.1.3 Data Governance
    • 9.5.2 Architecture Repository
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.1 Objectives
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
    • 10.2.2 Non-Architectural Inputs
    • 10.2.3 Architectural Inputs
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks
      • 10.3.1.3 Identify Required Matrices
      • 10.3.1.4 Identify Required Diagrams
      • 10.3.1.5 Identify Types of Requirement to be Collected
    • 10.3.2 Develop Baseline Application Architecture Description
    • 10.3.3 Develop Target Application Architecture Description
    • 10.3.4 Perform Gap Analysis
    • 10.3.5 Define Candidate Roadmap Components
    • 10.3.6 Resolve Impacts Across the Architecture Landscape
    • 10.3.7 Conduct Formal Stakeholder Review
    • 10.3.8 Finalize the Application Architecture
    • 10.3.9 Create the Architecture Definition Document
  • 10.4 Outputs
  • 10.5 Approach
    • 10.5.1 Architecture Repository
• 11. Phase D: Technology Architecture
  • 11.1 Objectives
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
    • 11.2.2 Non-Architectural Inputs
    • 11.2.3 Architectural Inputs
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
      • 11.3.1.3 Identify Required Matrices
      • 11.3.1.4 Identify Required Diagrams
      • 11.3.1.5 Identify Types of Requirement to be Collected
      • 11.3.1.6 Select Services
    • 11.3.2 Develop Baseline Technology Architecture Description
    • 11.3.3 Develop Target Technology Architecture Description
    • 11.3.4 Perform Gap Analysis
    • 11.3.5 Define Candidate Roadmap Components
    • 11.3.6 Resolve Impacts Across the Architecture Landscape
    • 11.3.7 Conduct Formal Stakeholder Review
    • 11.3.8 Finalize the Technology Architecture
    • 11.3.9 Create the Architecture Definition Document
  • 11.4 Outputs
  • 11.5 Approach
    • 11.5.1 Emerging Technologies
    • 11.5.2 Architecture Repository
• 12. Phase E: Opportunities & Solutions
  • 12.1 Objectives
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
    • 12.2.2 Non-Architectural Inputs
    • 12.2.3 Architectural Inputs
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes
    • 12.3.2 Determine Business Constraints for Implementation
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions
    • 12.3.5 Consolidate and Reconcile Interoperability Requirements
    • 12.3.6 Refine and Validate Dependencies
    • 12.3.7 Confirm Readiness and Risk for Business Transformation
    • 12.3.8 Formulate Implementation and Migration Strategy
    • 12.3.9 Identify and Group Major Work Packages
    • 12.3.10 Identify Transition Architectures
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
  • 12.4 Outputs
  • 12.5 Approach
• 13. Phase F: Migration Planning
  • 13.1 Objectives
  • 13.2 Inputs
    • 13.2.1 Reference Materials External to the Enterprise
    • 13.2.2 Non-Architectural Inputs
    • 13.2.3 Architectural Inputs
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 13.3.2 Assign a Business Value to Each Work Package
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
    • 13.3.6 Complete the Implementation and Migration Plan
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
  • 13.4 Outputs
  • 13.5 Approach
• 14. Phase G: Implementation Governance
  • 14.1 Objectives
  • 14.2 Inputs
    • 14.2.1 Reference Materials External to the Enterprise
    • 14.2.2 Non-Architectural Inputs
    • 14.2.3 Architectural Inputs
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management
    • 14.3.2 Identify Deployment Resources and Skills
    • 14.3.3 Guide Development of Solutions Deployment
    • 14.3.4 Perform Enterprise Architecture Compliance Reviews
    • 14.3.5 Implement Business and IT Operations
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation
  • 14.4 Outputs
  • 14.5 Approach
• 15. Phase H: Architecture Change Management
  • 15.1 Objectives
  • 15.2 Inputs
    • 15.2.1 Reference Materials External to the Enterprise
    • 15.2.2 Non-Architectural Inputs
    • 15.2.3 Architectural Inputs
  • 15.3 Steps
    • 15.3.1 Establish Value Realization Process
    • 15.3.2 Deploy Monitoring Tools
    • 15.3.3 Manage Risks
    • 15.3.4 Provide Analysis for Architecture Change Management
    • 15.3.5 Develop Change Requirements to Meet Performance Targets
    • 15.3.6 Manage Governance Process
    • 15.3.7 Activate the Process to Implement Change
  • 15.4 Outputs
  • 15.5 Approach
    • 15.5.1 Drivers for Change
    • 15.5.2 Enterprise Architecture Change Management Process
    • 15.5.3 Guidelines for Maintenance versus Architecture Redesign
• 16. ADM Architecture Requirements Management
  • 16.1 Objectives
  • 16.2 Inputs
  • 16.3 Steps
  • 16.4 Outputs
  • 16.5 Approach
    • 16.5.1 General
    • 16.5.2 Requirements Development
    • 16.5.3 Resources
      • 16.5.3.1 Business Scenarios
      • 16.5.3.2 Requirements Tools
• 17. Introduction to Part III
  • 17.1 Guidelines for Adapting the ADM Process
  • 17.2 Techniques for Architecture Development
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
    • Footnotes
• 18. Applying Iteration to the ADM
  • 18.1 Overview
  • 18.2 Iteration Cycles
  • 18.3 Classes of Architecture Engagement
  • 18.4 Approaches to Architecture Development
  • 18.5 Iteration Considerations
    • 18.5.1 Iteration between ADM Cycles
    • 18.5.2 Iteration within an ADM Cycle
  • 18.6 Conclusions
    • Footnotes
• 19. Applying the ADM Across the Architecture Landscape
  • 19.1 Overview
  • 19.2 Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
  • 19.4 Developing Architectures at Different Levels
• 20. Architecture Principles
  • 20.1 Introduction
  • 20.2 Characteristics of Architecture Principles
  • 20.3 Components of Architecture Principles
  • 20.4 Developing Architecture Principles
    • 20.4.1 Qualities of Principles
  • 20.5 Applying Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 1: Primacy of Principles
      • Principle 2: Maximize Benefit to the Enterprise
      • Principle 3: Information Management is Everybody's Business
      • Principle 4: Business Continuity
      • Principle 5: Common Use Applications
      • Principle 6: Service Orientation
      • Principle 7: Compliance with Law
      • Principle 8: IT Responsibility
      • Principle 9: Protection of Intellectual Property
    • 20.6.2 Data Principles
      • Principle 10: Data is an Asset
      • Principle 11: Data is Shared
      • Principle 12: Data is Accessible
      • Principle 13: Data Trustee
      • Principle 14: Common Vocabulary and Data Definitions
      • Principle 15: Data Security
    • 20.6.3 Application Principles
      • Principle 16: Technology Independence
      • Principle 17: Ease-of-Use
    • 20.6.4 Technology Principles
      • Principle 18: Requirements-Based Change
      • Principle 19: Responsive Change Management
      • Principle 20: Control Technical Diversity
      • Principle 21: Interoperability
• 21. Stakeholder Management
  • 21.1 Introduction
  • 21.2 Approach to Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.1 Identify Stakeholders
      • 21.3.1.1 Sample Stakeholder Analysis
    • 21.3.2 Classify Stakeholder Positions
    • 21.3.3 Determine Stakeholder Management Approach
    • 21.3.4 Tailor Engagement Deliverables
  • 21.4 Template Stakeholder Map
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.1 Background
    • 22.1.2 Content of a Pattern
    • 22.1.3 Terminology
      • 22.1.3.1 Architecture Patterns and Design Patterns
      • 22.1.3.2 Patterns and the Architecture Continuum
      • 22.1.3.3 Patterns and Views
      • 22.1.3.4 Patterns and Business Scenarios
  • 22.2 Some Pattern Resources
• 23. Gap Analysis
  • 23.1 Introduction
  • 23.2 Suggested Steps
  • 23.3 Example
• 24. Migration Planning Techniques
  • 24.1 Implementation Factor Assessment & Deduction Matrix
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix
  • 24.3 Architecture Definition Increments Table
  • 24.4 Transition Architecture State Evolution Table
  • 24.5 Business Value Assessment Technique
• 25. Interoperability Requirements
  • 25.1 Overview
  • 25.2 Defining Interoperability
  • 25.3 Enterprise Operating Model
  • 25.4 Refining Interoperability
  • 25.5 Determining Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions
    • Footnotes
• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)
  • 26.2 Determine Readiness Factors
  • 26.3 Present Readiness Factors
  • 26.4 Assess Readiness Factors
    • 26.4.1 Readiness Factor Vision
    • 26.4.2 Readiness Factor Rating
    • 26.4.3 Readiness Factor Risks & Actions
  • 26.5 Readiness and Migration Planning
  • 26.6 Marketing the Implementation Plan
  • 26.7 Conclusion
    • Footnotes
• 27. Risk Management
  • 27.1 Introduction
  • 27.2 Risk Classification
  • 27.3 Risk Identification
  • 27.4 Initial Risk Assessment
  • 27.5 Risk Mitigation and Residual Risk Assessment
  • 27.6 Conduct Residual Risk Assessment
  • 27.7 Risk Monitoring and Governance (Phase G)
  • 27.8 Summary
• 28. Capability-Based Planning
  • 28.1 Overview
  • 28.2 Capability-Based Planning Paradigm
  • 28.3 Concept of Capability-Based Planning
    • 28.3.1 Capability Dimensions
    • 28.3.2 Capability Increments
  • 28.4 Capabilities in an Enterprise Architecture Context
  • 28.5 Summary
• 29. Introduction to Part IV
  • 29.1 Overview
  • 29.2 Content Metamodel
  • 29.3 Content Framework and the TOGAF ADM
  • 29.4 Structure of Part IV
• 30. Content Metamodel
  • 30.1 Overview
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content
      • Core Metamodel Entities
    • 30.2.2 Overview of the Content Metamodel
  • 30.3 Content Metamodel in Detail
    • 30.3.1 Core Content Metamodel
    • 30.3.2 Full Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
    • 30.4.2 Services Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
    • 30.4.3 Process Modeling Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
    • 30.4.4 Data Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
    • 30.4.5 Infrastructure Consolidation Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
    • 30.4.6 Motivation Extensions
      • Purpose
      • Required Extensions to the Core Metamodel
  • 30.5 Content Metamodel Entities
  • 30.6 Content Metamodel Attributes
  • 30.7 Metamodel Relationships
    • Footnotes
• 31. Architectural Artifacts
  • 31.1 Basic Concepts
    • 31.1.1 Simple Example of an Architecture Viewpoint and Architecture View
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.1 General Guidelines
    • 31.2.2 Architecture View Creation Process
  • 31.3 Views, Tools, and Languages
    • 31.3.1 Overview
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.1 Example of Architecture Views and Architecture Viewpoints
    • 31.4.2 Architecture Views and Architecture Viewpoints in Enterprise Architecture
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description
  • 31.5 Conclusions
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept
    • 31.6.1 Preliminary Phase
      • Principles Catalog
    • 31.6.2 Phase A: Architecture Vision
      • Stakeholder Map Matrix
      • Value Chain Diagram
      • Solution Concept Diagram
      • Business Model Diagram
      • Business Capability Map
      • Value Stream Map
    • 31.6.3 Phase B: Business Architecture
      • Organization/Actor Catalog
      • Driver/Goal/Objective Catalog
      • Role Catalog
      • Business Service/Function Catalog
      • Location Catalog
      • Process/Event/Control/Product Catalog
      • Contract/Measure Catalog
      • Business Capabilities Catalog
      • Value Stream Catalog
      • Value Stream Stages Catalog
      • Business Interaction Matrix
      • Actor/Role Matrix
      • Value Stream/Capability Matrix
      • Strategy/Capability Matrix
      • Capability/Organization 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
      • Business Capability Map
      • Value Stream Map
      • Organization Map
    • 31.6.4 Phase C: Data Architecture
      • Data Entity/Data Component Catalog
      • Data Entity/Business Function Matrix
      • Application/Data Matrix
      • Conceptual Data Diagram
      • Logical Data Diagram
      • Data Dissemination Diagram
      • Data Security Diagram
      • Data Migration Diagram
      • Data Lifecycle Diagram
    • 31.6.5 Phase C: Application Architecture
      • Application Portfolio Catalog
      • Interface Catalog
      • Application/Organization Matrix
      • Role/Application Matrix
      • Application/Function Matrix
      • Application Interaction Matrix
      • Application Communication Diagram
      • Application and User Location Diagram
      • Application Use-Case Diagram
      • Enterprise Manageability Diagram
      • Process/Application Realization Diagram
      • Software Engineering Diagram
      • Application Migration Diagram
      • Software Distribution Diagram
    • 31.6.6 Phase D: Technology Architecture
      • Technology Standards Catalog
      • Technology Portfolio Catalog
      • Application/Technology Matrix
      • Environments and Locations Diagram
      • Platform Decomposition Diagram
      • Processing Diagram
      • Networked Computing/Hardware Diagram
      • Network and Communications Diagram
    • 31.6.7 Phase E: Opportunities and Solutions
      • Project Context Diagram
      • Benefits Diagram
    • 31.6.8 Requirements Management
      • Requirements Catalog
    • Footnotes
• 32. Architecture Deliverables
  • 32.1 Introduction
  • 32.2 Deliverable Descriptions
    • 32.2.1 Architecture Building Blocks
    • 32.2.2 Architecture Contract
      • Purpose
      • Content
    • 32.2.3 Architecture Definition Document
      • Purpose
      • Content
    • 32.2.4 Architecture Principles
      • Purpose
      • Content
    • 32.2.5 Architecture Repository
      • Purpose
      • Content
    • 32.2.6 Architecture Requirements Specification
      • Purpose
      • Content
    • 32.2.7 Architecture Roadmap
      • Purpose
      • Content
    • 32.2.8 Architecture Vision
      • Purpose
      • Content
    • 32.2.9 Business Principles, Business Goals, and Business Drivers
      • Purpose
      • Content
    • 32.2.10 Capability Assessment
      • Purpose
      • Content
    • 32.2.11 Change Request
      • Purpose
      • Content
    • 32.2.12 Communications Plan
      • Purpose
      • Content
    • 32.2.13 Compliance Assessment
      • Purpose
      • Content
    • 32.2.14 Implementation and Migration Plan
      • Purpose
      • Content
    • 32.2.15 Implementation Governance Model
      • Purpose
      • Content
    • 32.2.16 Organizational Model for Enterprise Architecture
      • Purpose
      • Content
    • 32.2.17 Request for Architecture Work
      • Purpose
      • Content
    • 32.2.18 Requirements Impact Assessment
      • Purpose
      • Content
    • 32.2.19 Solution Building Blocks
    • 32.2.20 Statement of Architecture Work
      • Purpose
      • Content
    • 32.2.21 Tailored Architecture Framework
      • Purpose
      • Content
• 33. Building Blocks
  • 33.1 Overview
  • 33.2 Introduction to Building Blocks
    • 33.2.1 Overview
    • 33.2.2 Generic Characteristics
    • 33.2.3 Architecture Building Blocks
      • 33.2.3.1 Characteristics
      • 33.2.3.2 Specification Content
    • 33.2.4 Solution Building Blocks
      • 33.2.4.1 Characteristics
      • 33.2.4.2 Specification Content
  • 33.3 Building Blocks and the ADM
    • 33.3.1 Basic Principles
      • 33.3.1.1 Building Blocks in Architecture Design
      • 33.3.1.2 Building Block Design
    • 33.3.2 Building Block Specification Process in the ADM
    • Footnotes
• 34. Introduction to Part V
  • 34.1 Introduction
  • 34.2 Structure of Part V
• 35. Enterprise Continuum
  • 35.1 Overview
  • 35.2 Enterprise Continuum and Architecture Re-Use
  • 35.3 Constituents of the Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Foundation Architecture
      • Common Systems Architectures
      • Industry Architectures
      • Organization-Specific Architectures
    • 35.4.2 Solutions Continuum
      • Foundation Solutions
      • Common Systems Solutions
      • Industry Solutions
      • Organization-Specific Solutions
  • 35.5 The Enterprise Continuum and the ADM
  • 35.6 The Enterprise Continuum and Your Organization
    • 35.6.1 Relationships
    • 35.6.2 Your Enterprise
• 36. Architecture Partitioning
  • 36.1 Overview
  • 36.2 Applying Classification to Create Partitioned Architectures
    • 36.2.1 Activities within the Preliminary Phase
  • 36.3 Integration
• 37. Architecture Repository
  • 37.1 Overview
  • 37.2 Architecture Landscape
  • 37.3 Reference Library
    • 37.3.1 Overview
  • 37.4 Standards Information Base
    • 37.4.1 Overview
    • 37.4.2 Types of Standard
    • 37.4.3 Standards Lifecycle
    • 37.4.4 Standards Classification within the Standards Information Base
  • 37.5 Governance Log
    • 37.5.1 Overview
    • 37.5.2 Contents of the Governance Log
  • 37.6 The Architecture Requirements Repository
    • 37.6.1 Overview
    • 37.6.2 Contents of the Architecture Requirements Repository
  • 37.7 Solutions Landscape
  • 37.8 The Enterprise Repository
  • 37.9 External Repositories
    • 37.9.1 External Reference Models
    • 37.9.2 External Standards
    • 37.9.3 Architecture Board Approvals
• 38. Tools for Architecture Development
  • 38.1 Overview
  • 38.2 Issues in Tool Standardization
• 39. Introduction to Part VI
  • 39.1 Overview
  • 39.2 Structure of Part VI
• 40. Establishing an Architecture Capability
  • 40.1 Overview
  • 40.2 Phase A: Architecture Vision
  • 40.3 Phase B: Business Architecture
  • 40.4 Phase C: Data Architecture
  • 40.5 Phase C: Application Architecture
  • 40.6 Phase D: Technology Architecture
  • 40.7 Phase E: Opportunities & Solutions
  • 40.8 Phase F: Migration Planning
  • 40.9 Phase G: Implementation Governance
  • 40.10 Phase H: Architecture Change Management
  • 40.11 Requirements Management
• 41. Architecture Board
  • 41.1 Role
  • 41.2 Responsibilities
  • 41.3 Setting Up the Architecture Board
    • 41.3.1 Triggers
    • 41.3.2 Size of the Board
    • 41.3.3 Board Structure
  • 41.4 Operation of the Architecture Board
    • 41.4.1 General
    • 41.4.2 Preparation
    • 41.4.3 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
• 42. Architecture Compliance
  • 42.1 Introduction
  • 42.2 Terminology: The Meaning of Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.1 Purpose
    • 42.3.2 Timing
    • 42.3.3 Governance and Personnel Scenarios
  • 42.4 Architecture Compliance Review Process
    • 42.4.1 Overview
    • 42.4.2 Roles
    • 42.4.3 Steps
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.1 Hardware and Operating System Checklist
    • 42.5.2 Software Services and Middleware Checklist
    • 42.5.3 Applications Checklists
      • 42.5.3.1 Infrastructure (Enterprise Productivity) Applications
      • 42.5.3.2 Business Applications
      • 42.5.3.3 Application Integration Approach
    • 42.5.4 Information Management Checklists
      • 42.5.4.1 Data Values
      • 42.5.4.2 Data Definition
      • 42.5.4.3 Security/Protection
      • 42.5.4.4 Hosting, Data Types, and Sharing
      • 42.5.4.5 Common Services
      • 42.5.4.6 Access Method
    • 42.5.5 Security Checklist
    • 42.5.6 System Management Checklist
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.1 General
      • 42.5.7.2 Processors/Servers/Clients
      • 42.5.7.3 Client
      • 42.5.7.4 Application Server
      • 42.5.7.5 Data Server
      • 42.5.7.6 COTS (where applicable)
    • 42.5.8 System Engineering/Methods & Tools Checklist
  • 42.6 Architecture Compliance Review Guidelines
    • 42.6.1 Tailoring the Checklists
    • 42.6.2 Conducting Architecture Compliance Reviews
• 43. Architecture Contracts
  • 43.1 Role
  • 43.2 Contents
    • 43.2.1 Statement of Architecture Work
    • 43.2.2 Contract between Architecture Design and Development Partners
    • 43.2.3 Contract between Architecting Function and Business Users
  • 43.3 Relationship to Architecture Governance
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
    • 44.1.2 Nature of Governance
      • 44.1.2.1 Governance: A Generic Perspective
      • 44.1.2.2 Characteristics of Governance
    • 44.1.3 Technology Governance
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.1 Architecture Governance Characteristics
      • 44.1.5.2 Architecture Governance as a Board-Level Responsibility
      • 44.1.5.3 The TOGAF Standard and Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • 44.2.1.1 Key Concepts
      • 44.2.1.2 Key Architecture Governance Processes
      • Policy Management and Take-On
      • Compliance
      • Dispensation
      • Monitoring and Reporting
      • Business Control
      • Environment Management
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.1 Overview
      • 44.2.2.2 Key Areas
      • 44.2.2.3 Operational Benefits
  • 44.3 Architecture Governance in Practice
    • 44.3.1 Architecture Governance - Key Success Factors
    • 44.3.2 Elements of an Effective Architecture Governance Strategy
      • 44.3.2.1 Architecture Governance and Corporate Politics
• 45. Architecture Maturity Models
  • 45.1 Overview
  • 45.2 Background
  • 45.3 US DoC ACMM Framework
    • 45.3.1 Overview
    • 45.3.2 Elements of the ACMM
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 0: None
      • Level 1: Initial
      • Level 2: Under Development
      • Level 3: Defined
      • Level 4: Managed
      • Level 5: Measured
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction
    • 45.4.2 SCAMPI Method
  • 45.5 Conclusions
    • Footnotes
• 46. Architecture Skills Framework
  • 46.1 Introduction
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.1 Definitional Rigor
    • 46.2.2 Basis of an Internal Architecture Practice
  • 46.3 Goals/Rationale
    • 46.3.1 Certification of Enterprise Architects
    • 46.3.2 Specific Benefits
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.1 Overview
    • 46.4.2 TOGAF Roles
    • 46.4.3 Categories of Skills
    • 46.4.4 Proficiency Levels
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.1 Generic Skills
    • 46.5.2 Business Skills & Methods
    • 46.5.3 Enterprise Architecture Skills
    • 46.5.4 Program or Project Management Skills
    • 46.5.5 IT General Knowledge Skills
    • 46.5.6 Technical IT Skills
    • 46.5.7 Legal Environment
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.1 Generic Role
    • 46.6.2 Characterization in Terms of the Enterprise Continuum
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.1 Skills and Experience in Producing Designs
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines
      • 46.6.3.3 Method-Driven Approach to Execution
      • 46.6.3.4 Full Project Scope Experience
      • 46.6.3.5 Leadership
      • 46.6.3.6 Personal and Professional Skills
      • 46.6.3.7 Skills and Experience in One or More Industries
  • 46.7 Conclusions
• A. Glossary of Supplementary Definitions
  • A.1 Application Software
  • A.2 Availability
  • A.3 Business System
  • A.4 Catalog
  • A.5 Client
  • A.6 COBIT
  • A.7 Configuration Management
  • A.8 Contract
  • A.9 Control
  • A.10 CxO
  • A.11 Data Dictionary
  • A.12 Data Element
  • A.13 Data Entity
  • A.14 Database
  • A.15 Database Management System
  • A.16 Driver
  • A.17 End User
  • A.18 Enterprise Resource Planning (ERP) System
  • A.19 Event
  • A.20 Functional Decomposition
  • A.21 Goal
  • A.22 Guideline
  • A.23 Hardware
  • A.24 Information Domain
  • A.25 Information System (IS)
  • A.26 Interaction
  • A.27 Interaction Model
  • A.28 Interface
  • A.29 Key Performance Indicator (KPI)
  • A.30 Lifecycle
  • A.31 Location
  • A.32 Logical Application Component
  • A.33 Logical Data Component
  • A.34 Logical Technology Component
  • A.35 Managing Successful Programs (MSP)
  • A.36 Matrix
  • A.37 Measure
  • A.38 Metaview
  • A.39 Open System
  • A.40 Operational Governance
  • A.41 Packaged Services
  • A.42 Physical Application Component
  • A.43 Physical Data Component
  • A.44 Physical Technology Component
  • A.45 Portability
  • A.46 Portfolio
  • A.47 PRINCE2
  • A.48 Process
  • A.49 Product
  • A.50 Profile
  • A.51 Profiling
  • A.52 Program
  • A.53 Project
  • A.54 Risk Management
  • A.55 Scalability
  • A.56 Security
  • A.57 Server
  • A.58 Service Quality
  • A.59 SMART
  • A.60 Supplier Management
  • A.61 System
  • A.62 Time Period
  • A.63 Transaction
  • A.64 Use-Case
  • A.65 User
• B. Abbreviations
• INDEX

return to top of page