INDEX

1.

• 1. Introduction
  • 1.5 Why Join The Open Group?
    • Footnotes
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
    • Footnotes
• 18. Applying Iteration to the ADM
  • 18.6 Conclusions
    • Footnotes
• 25. Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions
    • Footnotes
• 26. Business Transformation Readiness Assessment
  • 26.7 Conclusion
    • Footnotes
• 30. Content Metamodel
  • 30.7 Metamodel Relationships
    • Footnotes
• 31. Architectural Artifacts
  • Footnotes
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • Footnotes
• 45. Architecture Maturity Models
  • 45.5 Conclusions
    • Footnotes

2.

• 45. Architecture Maturity Models
  • 45.5 Conclusions
    • Footnotes

a.10

• A. Glossary of Supplementary Definitions
  • A.10 CxO

a.11

• A. Glossary of Supplementary Definitions
  • A.11 Data Dictionary

a.12

• A. Glossary of Supplementary Definitions
  • A.12 Data Element

a.13

• A. Glossary of Supplementary Definitions
  • A.13 Data Entity

a.14

• A. Glossary of Supplementary Definitions
  • A.14 Database

a.1

• A. Glossary of Supplementary Definitions
  • A.1 Application Software

a.15

• A. Glossary of Supplementary Definitions
  • A.15 Database Management System

a.16

• A. Glossary of Supplementary Definitions
  • A.16 Driver

a.17

• A. Glossary of Supplementary Definitions
  • A.17 End User

a.18

• A. Glossary of Supplementary Definitions
  • A.18 Enterprise Resource Planning (ERP) System

a.19

• A. Glossary of Supplementary Definitions
  • A.19 Event

a.20

• A. Glossary of Supplementary Definitions
  • A.20 Functional Decomposition

a.21

• A. Glossary of Supplementary Definitions
  • A.21 Goal

a.22

• A. Glossary of Supplementary Definitions
  • A.22 Guideline

a.23

• A. Glossary of Supplementary Definitions
  • A.23 Hardware

a.24

• A. Glossary of Supplementary Definitions
  • A.24 Information Domain

a.2

• A. Glossary of Supplementary Definitions
  • A.2 Availability

a.25

• A. Glossary of Supplementary Definitions
  • A.25 Information System (IS)

a.26

• A. Glossary of Supplementary Definitions
  • A.26 Interaction

a.27

• A. Glossary of Supplementary Definitions
  • A.27 Interaction Model

a.28

• A. Glossary of Supplementary Definitions
  • A.28 Interface

a.29

• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

a.30

• A. Glossary of Supplementary Definitions
  • A.30 Lifecycle

a.31

• A. Glossary of Supplementary Definitions
  • A.31 Location

a.32

• A. Glossary of Supplementary Definitions
  • A.32 Logical Application Component

a.33

• A. Glossary of Supplementary Definitions
  • A.33 Logical Data Component

a.34

• A. Glossary of Supplementary Definitions
  • A.34 Logical Technology Component

a.3

• A. Glossary of Supplementary Definitions
  • A.3 Business System

a.35

• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)

a.36

• A. Glossary of Supplementary Definitions
  • A.36 Matrix

a.37

• A. Glossary of Supplementary Definitions
  • A.37 Measure

a.38

• A. Glossary of Supplementary Definitions
  • A.38 Metaview

a.39

• A. Glossary of Supplementary Definitions
  • A.39 Open System

a.40

• A. Glossary of Supplementary Definitions
  • A.40 Operational Governance

a.41

• A. Glossary of Supplementary Definitions
  • A.41 Packaged Services

a.42

• A. Glossary of Supplementary Definitions
  • A.42 Physical Application Component

a.43

• A. Glossary of Supplementary Definitions
  • A.43 Physical Data Component

a.44

• A. Glossary of Supplementary Definitions
  • A.44 Physical Technology Component

a.4

• A. Glossary of Supplementary Definitions
  • A.4 Catalog

a.45

• A. Glossary of Supplementary Definitions
  • A.45 Portability

a.46

• A. Glossary of Supplementary Definitions
  • A.46 Portfolio

a.47

• A. Glossary of Supplementary Definitions
  • A.47 PRINCE2

a.48

• A. Glossary of Supplementary Definitions
  • A.48 Process

a.49

• A. Glossary of Supplementary Definitions
  • A.49 Product

a.50

• A. Glossary of Supplementary Definitions
  • A.50 Profile

a.51

• A. Glossary of Supplementary Definitions
  • A.51 Profiling

a.52

• A. Glossary of Supplementary Definitions
  • A.52 Program

a.53

• A. Glossary of Supplementary Definitions
  • A.53 Project

a.54

• A. Glossary of Supplementary Definitions
  • A.54 Risk Management

a.5

• A. Glossary of Supplementary Definitions
  • A.5 Client

a.55

• A. Glossary of Supplementary Definitions
  • A.55 Scalability

a.56

• A. Glossary of Supplementary Definitions
  • A.56 Security

a.57

• A. Glossary of Supplementary Definitions
  • A.57 Server

a.58

• A. Glossary of Supplementary Definitions
  • A.58 Service Quality

a.59

• A. Glossary of Supplementary Definitions
  • A.59 SMART

a.60

• A. Glossary of Supplementary Definitions
  • A.60 Supplier Management

a.61

• A. Glossary of Supplementary Definitions
  • A.61 System

a.62

• A. Glossary of Supplementary Definitions
  • A.62 Time Period

a.63

• A. Glossary of Supplementary Definitions
  • A.63 Transaction

a.64

• A. Glossary of Supplementary Definitions
  • A.64 Use-Case

a.6

• A. Glossary of Supplementary Definitions
  • A.6 COBIT

a.65

• A. Glossary of Supplementary Definitions
  • A.65 User

a.7

• A. Glossary of Supplementary Definitions
  • A.7 Configuration Management

a.8

• A. Glossary of Supplementary Definitions
  • A.8 Contract

a.9

• A. Glossary of Supplementary Definitions
  • A.9 Control

ABB

• 3. Definitions
  • 3.8 Architecture Building Block (ABB)
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.1 Background
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.1 Architecture Building Blocks
• 33. Building Blocks
  • 33.1 Overview
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks

abbreviations

• B. Abbreviations
• INDEX

abstraction

• 3. Definitions
  • 3.1 Abstraction

access

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.6 Access Method

accessible

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 12: Data is Accessible

ACMM

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.2 Elements of the ACMM

across

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.6 Resolve Impacts Across the Architecture Landscape
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.6 Resolve Impacts Across the Architecture Landscape
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.6 Resolve Impacts Across the Architecture Landscape
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions
• 19. Applying the ADM Across the Architecture Landscape

action

• 3. Definitions
  • 3.35 Course of Action
• 26. Business Transformation Readiness Assessment
  • 26.4 Assess Readiness Factors
    • 26.4.3 Readiness Factor Risks & Actions
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Actions Assigned

activate

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.7 Activate the Process to Implement Change

Active Store

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Industry Architectures

activities

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures
    • 36.2.1 Activities within the Preliminary Phase

activity model

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

actor

• 3. Definitions
  • 3.2 Actor
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Actor/Role

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Actor/Role Matrix

Actor/Role matrix

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Actor/Role Matrix

adapting

• 4. Introduction to Part II
  • 4.3 Adapting the ADM
• 17. Introduction to Part III
  • 17.1 Guidelines for Adapting the ADM Process

ADM

• 1. Introduction
  • 1.1 Structure of this Document
• 3. Definitions
  • 3.10 Architecture Development Method (ADM)
• 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

ADM guidelines and techniques

• 1. Introduction
  • 1.1 Structure of this Document
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.3 ADM and Supporting Guidelines and Techniques
• 17. Introduction to Part III

ADM iteration

• 18. Applying Iteration to the ADM

ADM, Requirements Management

• 16. ADM Architecture Requirements Management

agenda

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda

amp

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan

analysis

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.4 Perform Gap Analysis
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.4 Perform Gap Analysis
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.4 Perform Gap Analysis
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.4 Provide Analysis for Architecture Change Management
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.1 Identify Stakeholders
      • 21.3.1.1 Sample Stakeholder Analysis
• 23. Gap Analysis

any

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Any Other Business (AOB)

AOB

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Any Other Business (AOB)

applicable

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.6 COTS (where applicable)

application

• 3. Definitions
  • 3.3 Application Architecture
  • 3.4 Application Component
  • 3.5 Application Platform
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks
    • 10.3.2 Develop Baseline Application Architecture Description
    • 10.3.3 Develop Target Application Architecture Description
    • 10.3.8 Finalize the Application Architecture

Application and User Location diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application and User Location Diagram

Application Architecture

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
• 3. Definitions
  • 3.3 Application Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture

application building blocks

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks

Application Communication diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Communication Diagram

application component

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Application/Data

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Application/Data Matrix

Application/Data matrix

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Application/Data Matrix

Application/Function

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application/Function Matrix

Application/Function matrix

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application/Function Matrix

Application Interaction matrix

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Interaction Matrix

Application Migration diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Migration Diagram

Application/Organization

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application/Organization Matrix

Application/Organization matrix

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application/Organization Matrix

Application Platform

• 3. Definitions
  • 3.5 Application Platform

Application Portfolio catalog

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Portfolio Catalog

application principles, examples

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles

applications

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 5: Common Use Applications
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.3 Applications Checklists
      • 42.5.3.1 Infrastructure (Enterprise Productivity) Applications
      • 42.5.3.2 Business Applications

Application Software

• A. Glossary of Supplementary Definitions
  • A.1 Application Software

Applications Standards

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

Application/Technology

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Application/Technology Matrix

Application/Technology matrix

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Application/Technology Matrix

Application Use-Case diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Use-Case Diagram

applying

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 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
• 18. Applying Iteration to the ADM
• 19. Applying the ADM Across the Architecture Landscape
• 20. Architecture Principles
  • 20.5 Applying Architecture Principles
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures

applying the ADM

• 19. Applying the ADM Across the Architecture Landscape

approach

• 5. Preliminary Phase
  • 5.5 Approach
• 6. Phase A: Architecture Vision
  • 6.5 Approach
• 7. Phase B: Business Architecture
  • 7.5 Approach
• 8. Phase C: Information Systems Architectures
  • 8.2 Approach
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.5 Approach
• 11. Phase D: Technology Architecture
  • 11.5 Approach
• 12. Phase E: Opportunities & Solutions
  • 12.5 Approach
• 13. Phase F: Migration Planning
  • 13.5 Approach
• 14. Phase G: Implementation Governance
  • 14.5 Approach
• 15. Phase H: Architecture Change Management
  • 15.5 Approach
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
• 21. Stakeholder Management
  • 21.2 Approach to Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.3 Determine Stakeholder Management Approach
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.3 Applications Checklists
      • 42.5.3.3 Application Integration Approach
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.3 Method-Driven Approach to Execution

approaches

• 18. Applying Iteration to the ADM
  • 18.4 Approaches to Architecture Development

approval

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval
• 37. Architecture Repository
  • 37.9 External Repositories
    • 37.9.3 Architecture Board Approvals

architect

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect

architecting

• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.3 Contract between Architecting Function and Business Users

architects

• 46. Architecture Skills Framework
  • 46.3 Goals/Rationale
    • 46.3.1 Certification of Enterprise Architects

architectural

• 3. Definitions
  • 3.6 Architectural Style
• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.3 Architectural Inputs
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.3 Architectural Inputs
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.3 Architectural Inputs
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.3 Architectural Inputs
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.3 Architectural Inputs
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.3 Architectural Inputs
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.3 Architectural Inputs
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.3 Architectural Inputs
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.3 Architectural Inputs
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.3 Architectural Inputs
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase

architectural artifact

• 31. Architectural Artifacts

architectural artifact, concepts

• 31. Architectural Artifacts
  • 31.1 Basic Concepts

architectural style

• 3. Definitions
  • 3.6 Architectural Style
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles

architecture

• 1. Introduction
  • 1.3 Executive Overview
    • 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?
• 2. Core Concepts
  • 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.7 Architecture Repository
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 3. Definitions
  • 3.3 Application Architecture
  • 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.24 Business Architecture
  • 3.31 Capability Architecture
  • 3.36 Data Architecture
  • 3.40 Foundation Architecture
  • 3.64 Segment Architecture
  • 3.67 Service-Oriented Architecture (SOA)
  • 3.69 Solution Architecture
  • 3.74 Strategic Architecture
  • 3.75 Target Architecture
  • 3.76 Taxonomy of Architecture Views
  • 3.77 Technology Architecture
  • 3.80 Transition Architecture
• 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.2 Architecture Development Cycle
  • 4.4 Architecture Governance
  • 4.5 Scoping the Architecture
    • 4.5.4 Architecture Domains

architecture artifacts

• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase

Architecture Board

• 4. Introduction to Part II
  • 4.4 Architecture Governance
• 41. Architecture Board

Architecture Building Block

• 3. Definitions
  • 3.8 Architecture Building Block (ABB)
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks

Architecture/Business

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

Architecture Capability

• 2. Core Concepts
  • 2.7 Architecture Repository
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles
• 37. Architecture Repository
  • 37.1 Overview
• 40. Establishing an Architecture Capability

Architecture Capability Framework

• 1. Introduction
  • 1.1 Structure of this Document
• 39. Introduction to Part VI

architecture change management

• 15. Phase H: Architecture Change Management

Architecture Compliance

• 42. Architecture Compliance
  • 42.2 Terminology: The Meaning of Architecture Compliance

Architecture Compliance, checklists

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists

Architecture Compliance, guidelines

• 42. Architecture Compliance
  • 42.6 Architecture Compliance Review Guidelines

Architecture Compliance, review

• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews

Architecture Compliance, review process

• 42. Architecture Compliance
  • 42.4 Architecture Compliance Review Process
    • 42.4.1 Overview

Architecture Content Framework

• 1. Introduction
  • 1.1 Structure of this Document
• 29. Introduction to Part IV

Architecture Continuum

• 2. Core Concepts
  • 2.6 Enterprise Continuum
• 3. Definitions
  • 3.9 Architecture Continuum
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.2 Patterns and the Architecture Continuum
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum

Architecture Contract

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.2 Architecture Contract
• 43. Architecture Contracts

architecture, definition

• 2. Core Concepts
  • 2.2 What is Architecture in the Context of the TOGAF Standard?

Architecture Definition Document

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.3 Architecture Definition Document

architecture deliverables

• 32. Architecture Deliverables

Architecture Description

• 31. Architectural Artifacts
  • 31.1 Basic Concepts

architecture development

• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles
  • 18.4 Approaches to Architecture Development
• 38. Tools for Architecture Development

Architecture Development Method

• 1. Introduction
  • 1.1 Structure of this Document
• 3. Definitions
  • 3.10 Architecture Development Method (ADM)
• 4. Introduction to Part II

architecture development, techniques

• 17. Introduction to Part III
  • 17.2 Techniques for Architecture Development

architecture domain

• 3. Definitions
  • 3.11 Architecture Domain
• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.4 Architecture Domains

architecture engagement

• 18. Applying Iteration to the ADM
  • 18.3 Classes of Architecture Engagement

Architecture Forum

• 1. Introduction

Architecture Framework

• 3. Definitions
  • 3.12 Architecture Framework

Architecture Governance

• 3. Definitions
  • 3.13 Architecture Governance
• 4. Introduction to Part II
  • 4.4 Architecture Governance
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.4 Principles
• 14. Phase G: Implementation Governance
  • 14.5 Approach
• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles
• 41. Architecture Board
  • 41.1 Role
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.1 Architecture Governance Characteristics

Architecture Governance Framework

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
  • 44.2 Architecture Governance Framework

Architecture Governance Framework, structure

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • 44.2.1.1 Key Concepts

Architecture Governance, implementation

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice

architecture integration

• 4. Introduction to Part II
  • 4.6 Architecture Integration

Architecture Landscape

• 2. Core Concepts
  • 2.7 Architecture Repository
• 3. Definitions
  • 3.14 Architecture Landscape
• 19. Applying the ADM Across the Architecture Landscape
  • 19.2 Architecture Landscape
• 37. Architecture Repository
  • 37.1 Overview
  • 37.2 Architecture Landscape

Architecture Metamodel

• 2. Core Concepts
  • 2.7 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview

architecture model

• 3. Definitions
  • 3.15 Architecture Model
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process
• 31. Architectural Artifacts
  • 31.1 Basic Concepts

architecture partition

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture

architecture partitioning

• 36. Architecture Partitioning

architecture pattern

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.1 Architecture Patterns and Design Patterns

architecture pattern, content

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.2 Content of a Pattern

Architecture Principle

• 3. Definitions
  • 3.16 Architecture Principle
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.4 Principles
• 20. Architecture Principles
  • 20.1 Introduction

Architecture Principles, characteristics

• 20. Architecture Principles
  • 20.2 Characteristics of Architecture Principles

Architecture Principles, components

• 20. Architecture Principles
  • 20.3 Components of Architecture Principles

Architecture Principles, criteria

• 20. Architecture Principles
  • 20.4 Developing Architecture Principles
    • 20.4.1 Qualities of Principles

Architecture Report

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.9 Create the Architecture Definition Document

Architecture Repository

• 2. Core Concepts
  • 2.7 Architecture Repository
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.2 Architecture Repository
• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.2 Architecture Repository
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.5 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview

Architecture Requirements Repository

• 2. Core Concepts
  • 2.7 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview
  • 37.6 The Architecture Requirements Repository

Architecture Requirements Specification

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.6 Architecture Requirements Specification

Architecture Roadmap

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.7 Architecture Roadmap

architectures

• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.10 Identify Transition Architectures
• 19. Applying the ADM Across the Architecture Landscape
  • 19.4 Developing Architectures at Different Levels
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Common Systems Architectures
      • Industry Architectures
      • Organization-Specific Architectures
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures

architecture, scoping

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture

Architecture Skills Framework

• 46. Architecture Skills Framework

Architecture Skills Framework, proficiency levels

• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.4 Proficiency Levels

Architecture Skills Framework, skills

• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.3 Categories of Skills

architecture view

• 3. Definitions
  • 3.17 Architecture View
• 21. Stakeholder Management
  • 21.2 Approach to Stakeholder Management
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.3 Patterns and Views
• 31. Architectural Artifacts
  • 31.1 Basic Concepts

architecture view, creation

• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.2 Architecture View Creation Process

architecture view, examples

• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.1 Example of Architecture Views and Architecture Viewpoints

architecture view, guidelines

• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.1 General Guidelines

architecture viewpoint

• 3. Definitions
  • 3.18 Architecture Viewpoint
• 21. Stakeholder Management
  • 21.2 Approach to Stakeholder Management
• 31. Architectural Artifacts
  • 31.1 Basic Concepts

architecture viewpoint, examples

• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.1 Example of Architecture Views and Architecture Viewpoints

Architecture Vision

• 3. Definitions
  • 3.19 Architecture Vision
• 4. Introduction to Part II
  • 4.3 Adapting the ADM
• 6. Phase A: Architecture Vision
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.8 Architecture Vision

are

• 1. Introduction
  • 1.3 Executive Overview
    • What are the benefits of an Enterprise Architecture?

areas

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.2 Key Areas

artifact

• 2. Core Concepts
  • 2.5 Deliverables, Artifacts, and Building Blocks
• 3. Definitions
  • 3.20 Artifact
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase

ARTS

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.2 Architecture Repository

as

• 1. Introduction
  • 1.3 Executive Overview
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.2 Architecture Governance as a Board-Level Responsibility

assess

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.5 Assess Readiness for Business Transformation
• 26. Business Transformation Readiness Assessment
  • 26.4 Assess Readiness Factors

assessment

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
• 24. Migration Planning Techniques
  • 24.1 Implementation Factor Assessment & Deduction Matrix
  • 24.5 Business Value Assessment Technique
• 26. Business Transformation Readiness Assessment
• 27. Risk Management
  • 27.4 Initial Risk Assessment
  • 27.5 Risk Mitigation and Residual Risk Assessment
  • 27.6 Conduct Residual Risk Assessment
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.10 Capability Assessment
    • 32.2.13 Compliance Assessment
    • 32.2.18 Requirements Impact Assessment
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Compliance Assessments

asset

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 10: Data is an Asset

assign

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.2 Assign a Business Value to Each Work Package

assigned

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Actions Assigned

attributes

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes
• 30. Content Metamodel
  • 30.6 Content Metamodel Attributes

audit information

• 4. Introduction to Part II
  • 4.4 Architecture Governance

availability

• A. Glossary of Supplementary Definitions
  • A.2 Availability

Availability/Delivery

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

b

• 7. Phase B: Business Architecture
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
• 40. Establishing an Architecture Capability
  • 40.3 Phase B: Business Architecture
• B. Abbreviations
• INDEX

background

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.1 Background
• 45. Architecture Maturity Models
  • 45.2 Background

Balanced Scorecard technique

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques

base

• 3. Definitions
  • 3.73 Standards Information Base (SIB)
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

baseline

• 3. Definitions
  • 3.21 Baseline
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.2 Develop Baseline Business Architecture Description
  • 7.5 Approach
    • 7.5.2 Developing the Baseline Description
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.2 Develop Baseline Data Architecture Description
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.2 Develop Baseline Application Architecture Description
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.2 Develop Baseline Technology Architecture Description

Baseline Application Architecture Description

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.2 Develop Baseline Application Architecture Description

Baseline Data Architecture Description

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.2 Develop Baseline Data Architecture Description

Baseline Description

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.2 Developing the Baseline Description

baseline first

• 18. Applying Iteration to the ADM
  • 18.4 Approaches to Architecture Development

Baseline Technology Architecture Description

• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.2 Develop Baseline Technology Architecture Description

basic

• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
    • 4.2.2 Basic Structure
• 31. Architectural Artifacts
  • 31.1 Basic Concepts
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • 33.3.1 Basic Principles

basis

• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.2 Basis of an Internal Architecture Practice

be

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.6 Identify Types of Requirement to be Collected
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.5 Identify Types of Requirement to be Collected
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.5 Identify Types of Requirement to be Collected
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.5 Identify Types of Requirement to be Collected

benefit

• 1. Introduction
  • 1.3 Executive Overview
    • What are the benefits of an Enterprise Architecture?
    • Who would benefit from using the TOGAF standard?
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 2: Maximize Benefit to the Enterprise
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
    • Benefits Diagram
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.3 Operational Benefits
• 46. Architecture Skills Framework
  • 46.3 Goals/Rationale
    • 46.3.2 Specific Benefits

Benefits diagram

• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
    • Benefits Diagram

between

• 18. Applying Iteration to the ADM
  • 18.5 Iteration Considerations
    • 18.5.1 Iteration between ADM Cycles
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.2 Contract between Architecture Design and Development Partners
    • 43.2.3 Contract between Architecting Function and Business Users

block

• 2. Core Concepts
  • 2.5 Deliverables, Artifacts, and Building Blocks
• 3. Definitions
  • 3.8 Architecture Building Block (ABB)
  • 3.23 Building Block
  • 3.70 Solution Building Block (SBB)
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.1 Architecture Building Blocks
    • 32.2.19 Solution Building Blocks
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks
    • 33.2.4 Solution Building Blocks

board

• 37. Architecture Repository
  • 37.9 External Repositories
    • 37.9.3 Architecture Board Approvals
• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board
    • 41.3.2 Size of the Board
    • 41.3.3 Board Structure

Board-Level

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.2 Architecture Governance as a Board-Level Responsibility

boundaries

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts

boundaryless

• 3. Definitions
  • 3.22 Boundaryless Information FlowTM

Boundaryless Information Flow

• 3. Definitions
  • 3.22 Boundaryless Information FlowTM

BPMN

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

breadth

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.1 Breadth
• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

breadth, enterprise

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.1 Breadth

BTEP

• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)

BTEP, Readiness Rating Scheme

• 26. Business Transformation Readiness Assessment
  • 26.4 Assess Readiness Factors
    • 26.4.2 Readiness Factor Rating

building

• 2. Core Concepts
  • 2.5 Deliverables, Artifacts, and Building Blocks
• 3. Definitions
  • 3.8 Architecture Building Block (ABB)
  • 3.23 Building Block
  • 3.70 Solution Building Block (SBB)
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.1 Architecture Building Blocks
    • 32.2.19 Solution Building Blocks
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks
    • 33.2.4 Solution Building Blocks

building block

• 3. Definitions
  • 3.23 Building Block
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept
• 33. Building Blocks

building blocks, characteristics

• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.2 Generic Characteristics

building blocks, design

• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • 33.3.1 Basic Principles
      • 33.3.1.2 Building Block Design

business

• 3. Definitions
  • 3.24 Business Architecture
  • 3.25 Business Capability
  • 3.26 Business Function
  • 3.27 Business Governance
  • 3.28 Business Model
  • 3.29 Business Service
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 6.3.5 Assess Readiness for Business Transformation
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks
    • 7.3.2 Develop Baseline Business Architecture Description
    • 7.3.3 Develop Target Business Architecture Description
    • 7.3.8 Finalize the Business Architecture
  • 7.5 Approach
    • 7.5.3 Applying Business Capabilities

Business Architecture

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
• 3. Definitions
  • 3.24 Business Architecture
• 7. Phase B: Business Architecture

business capabilities

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.3 Applying Business Capabilities

Business Capabilities catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Capabilities Catalog

business capability

• 3. Definitions
  • 3.25 Business Capability
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Business Capability map

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Business Capability Map
  • 31.6.3 Phase B: Business Architecture
    • Business Capability Map

business capability mapping

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

Business Continuity Plan

• 27. Risk Management
  • 27.5 Risk Mitigation and Residual Risk Assessment

business drivers

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.9 Business Principles, Business Goals, and Business Drivers

Business Footprint diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Footprint Diagram

business function

• 3. Definitions
  • 3.26 Business Function

business goals

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.9 Business Principles, Business Goals, and Business Drivers

business governance

• 3. Definitions
  • 3.27 Business Governance

Business Interaction matrix

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Interaction Matrix

business model

• 3. Definitions
  • 3.28 Business Model

Business Model diagram

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Business Model Diagram

business modeling

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

business planning

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

business principles

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.4 Principles
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.9 Business Principles, Business Goals, and Business Drivers

business principles, examples

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles

business process model

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

Business Process Modeling Notation

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

business scenarios

• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
      • 16.5.3.1 Business Scenarios
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.8 Architecture Vision

business service

• 3. Definitions
  • 3.29 Business Service
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Business Service/Function catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Service/Function Catalog

Business Service/Information diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Service/Information Diagram

Business Standards

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

business system

• A. Glossary of Supplementary Definitions
  • A.3 Business System

Business Transformation Readiness Assessment

• 26. Business Transformation Readiness Assessment

Business Use-Case diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Use-Case Diagram

by

• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase

c

• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
  • 31.6.5 Phase C: Application Architecture
• 40. Establishing an Architecture Capability
  • 40.4 Phase C: Data Architecture
  • 40.5 Phase C: Application Architecture

Calendar

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

candidate

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.5 Define Candidate Roadmap Components
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.5 Define Candidate Roadmap Components
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.5 Define Candidate Roadmap Components

capabilities

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.4 Evaluate Capabilities
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.3 Applying Business Capabilities
• 28. Capability-Based Planning
  • 28.4 Capabilities in an Enterprise Architecture Context
• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Capabilities Catalog

capability

• 2. Core Concepts
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 3. Definitions
  • 3.25 Business Capability
  • 3.30 Capability
  • 3.31 Capability Architecture
  • 3.32 Capability Increment
• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
    • 28.3.1 Capability Dimensions
    • 28.3.2 Capability Increments
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Business Capability Map
  • 31.6.3 Phase B: Business Architecture
    • Business Capability Map
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.10 Capability Assessment
• 40. Establishing an Architecture Capability
• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)

Capability Architecture

• 3. Definitions
  • 3.31 Capability Architecture
• 19. Applying the ADM Across the Architecture Landscape
  • 19.2 Architecture Landscape
• 37. Architecture Repository
  • 37.2 Architecture Landscape

Capability Architecture Requirements

• 37. Architecture Repository
  • 37.6 The Architecture Requirements Repository
    • 37.6.2 Contents of the Architecture Requirements Repository

Capability Assessment

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.10 Capability Assessment
• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

Capability-Based

• 28. Capability-Based Planning
  • 28.2 Capability-Based Planning Paradigm
  • 28.3 Concept of Capability-Based Planning

capability-based planning

• 28. Capability-Based Planning

capability dimensions

• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
    • 28.3.1 Capability Dimensions

capability increment

• 3. Definitions
  • 3.32 Capability Increment
• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
    • 28.3.2 Capability Increments

Capability Maturity Model

• 45. Architecture Maturity Models
  • 45.1 Overview

Capability/Organization

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Capability/Organization Matrix

Capability/Organization matrix

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Capability/Organization Matrix

catalog

• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept
    • 31.6.1 Preliminary Phase
      • Principles Catalog
    • 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
    • 31.6.4 Phase C: Data Architecture
      • Data Entity/Data Component Catalog
    • 31.6.5 Phase C: Application Architecture
      • Application Portfolio Catalog
      • Interface Catalog
    • 31.6.6 Phase D: Technology Architecture
      • Technology Standards Catalog
      • Technology Portfolio Catalog
    • 31.6.8 Requirements Management
      • Requirements Catalog
• A. Glossary of Supplementary Definitions
  • A.4 Catalog

catalog of application building blocks

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks

catalogs

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.2 Identify Required Catalogs of Application Building Blocks
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept

catalogs, building blocks

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Catalogs of Business Building Blocks

Catalyst

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

categories

• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.3 Categories of Skills

certification

• 46. Architecture Skills Framework
  • 46.3 Goals/Rationale
    • 46.3.1 Certification of Enterprise Architects

chain

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Value Chain Diagram

change

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.4 Provide Analysis for Architecture Change Management
    • 15.3.5 Develop Change Requirements to Meet Performance Targets
    • 15.3.7 Activate the Process to Implement Change
  • 15.5 Approach
    • 15.5.1 Drivers for Change
    • 15.5.2 Enterprise Architecture Change Management Process

change management

• 15. Phase H: Architecture Change Management

change management process

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

Change Request

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.11 Change Request

characteristics

• 20. Architecture Principles
  • 20.2 Characteristics of Architecture Principles
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.2 Generic Characteristics
    • 33.2.3 Architecture Building Blocks
      • 33.2.3.1 Characteristics
    • 33.2.4 Solution Building Blocks
      • 33.2.4.1 Characteristics
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.2 Nature of Governance
      • 44.1.2.2 Characteristics of Governance
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.1 Architecture Governance Characteristics
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect

characterization

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.2 Characterization in Terms of the Enterprise Continuum

checklist

• 42. Architecture Compliance
  • 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.4 Information Management Checklists
    • 42.5.5 Security Checklist
    • 42.5.6 System Management Checklist
    • 42.5.7 System Engineering/Overall Architecture Checklists
    • 42.5.8 System Engineering/Methods & Tools Checklist

classes

• 18. Applying Iteration to the ADM
  • 18.3 Classes of Architecture Engagement

classification

• 27. Risk Management
  • 27.2 Risk Classification
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

classify

• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.2 Classify Stakeholder Positions

class model

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

client

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.3 Client
• A. Glossary of Supplementary Definitions
  • A.5 Client

close

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation

CMM

• 45. Architecture Maturity Models
  • 45.1 Overview

CMMI

• 32. Architecture Deliverables
  • 32.1 Introduction
• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

COBIT

• 4. Introduction to Part II
  • 4.4 Architecture Governance
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT
• A. Glossary of Supplementary Definitions
  • A.6 COBIT

COBIT framework

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.1 General

collected

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.6 Identify Types of Requirement to be Collected
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.5 Identify Types of Requirement to be Collected
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.5 Identify Types of Requirement to be Collected
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.5 Identify Types of Requirement to be Collected

common

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 5: Common Use Applications
    • 20.6.2 Data Principles
      • Principle 14: Common Vocabulary and Data Definitions
• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Common Systems Architectures
    • 35.4.2 Solutions Continuum
      • Common Systems Solutions
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.5 Common Services

Common Systems Architectures

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Common Systems Architectures

Common Systems Solutions

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Common Systems Solutions

communication

• 3. Definitions
  • 3.33 Communications and Stakeholder Management
• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Communication Diagram
  • 31.6.6 Phase D: Technology Architecture
    • Network and Communications Diagram
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.12 Communications Plan

communications management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 3. Definitions
  • 3.33 Communications and Stakeholder Management

Communications Plan

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.12 Communications Plan

complete

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.6 Complete the Implementation and Migration Plan
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

compliance

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.4 Perform Enterprise Architecture Compliance Reviews
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 7: Compliance with Law
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.13 Compliance Assessment
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Compliance Assessments
• 42. Architecture Compliance
  • 42.2 Terminology: The Meaning of Architecture Compliance
  • 42.3 Architecture Compliance Reviews
  • 42.4 Architecture Compliance Review Process
  • 42.5 Architecture Compliance Review Checklists
  • 42.6 Architecture Compliance Review Guidelines
    • 42.6.2 Conducting Architecture Compliance Reviews

Compliance Assessment

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.13 Compliance Assessment
• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

component

• 3. Definitions
  • 3.4 Application Component
  • 3.78 Technology Component
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.5 Define Candidate Roadmap Components
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.5 Define Candidate Roadmap Components
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.5 Define Candidate Roadmap Components
• 20. Architecture Principles
  • 20.3 Components of Architecture Principles
• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Data Component Catalog
• A. Glossary of Supplementary Definitions
  • A.32 Logical Application Component
  • A.33 Logical Data Component
  • A.34 Logical Technology Component
  • A.42 Physical Application Component
  • A.43 Physical Data Component
  • A.44 Physical Technology Component

Computing/Hardware

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Networked Computing/Hardware Diagram

concept

• 2. Core Concepts
• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts

conceptual

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Conceptual Data Diagram
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure

Conceptual Data diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Conceptual Data Diagram

concern

• 3. Definitions
  • 3.34 Concern
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
• 21. Stakeholder Management
  • 21.2 Approach to Stakeholder Management
• 31. Architectural Artifacts
  • 31.1 Basic Concepts

conclusion

• 18. Applying Iteration to the ADM
  • 18.6 Conclusions
• 26. Business Transformation Readiness Assessment
  • 26.7 Conclusion
• 31. Architectural Artifacts
  • 31.5 Conclusions
• 45. Architecture Maturity Models
  • 45.5 Conclusions
• 46. Architecture Skills Framework
  • 46.7 Conclusions

conditions

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.1 Conditions of Use

conditions of use

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.1 Conditions of Use

conduct

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.7 Conduct Formal Stakeholder Review
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.7 Conduct Formal Stakeholder Review
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.7 Conduct Formal Stakeholder Review
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
• 27. Risk Management
  • 27.6 Conduct Residual Risk Assessment

conducting

• 42. Architecture Compliance
  • 42.6 Architecture Compliance Review Guidelines
    • 42.6.2 Conducting Architecture Compliance Reviews

configuration

• A. Glossary of Supplementary Definitions
  • A.7 Configuration Management

configuration management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• A. Glossary of Supplementary Definitions
  • A.7 Configuration Management

confirm

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.2 Confirm Governance and Support Frameworks
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.7 Confirm Readiness and Risk for Business Transformation
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management

considerations

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
• 18. Applying Iteration to the ADM
  • 18.5 Iteration Considerations

consolidate

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
    • 12.3.5 Consolidate and Reconcile Interoperability Requirements

consolidated

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions
• 24. Migration Planning Techniques
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix

consolidation

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.5 Infrastructure Consolidation Extensions

constituents

• 35. Enterprise Continuum
  • 35.3 Constituents of the Enterprise Continuum

constraints

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.2 Determine Business Constraints for Implementation

content

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.2 Content of a Pattern
• 29. Introduction to Part IV
  • 29.2 Content Metamodel
  • 29.3 Content Framework and the TOGAF ADM
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content

content framework, and the TOGAF ADM

• 29. Introduction to Part IV
  • 29.3 Content Framework and the TOGAF ADM

content metamodel

• 29. Introduction to Part IV
  • 29.2 Content Metamodel
• 30. Content Metamodel

content metamodel attributes

• 30. Content Metamodel
  • 30.6 Content Metamodel Attributes

content metamodel, detail

• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail

content metamodel entities

• 30. Content Metamodel
  • 30.5 Content Metamodel Entities

content metamodel, extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions

content metamodel, vision and concepts

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts

contents

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log
  • 37.6 The Architecture Requirements Repository
    • 37.6.2 Contents of the Architecture Requirements Repository
• 43. Architecture Contracts
  • 43.2 Contents

content tailoring

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

context

• 2. Core Concepts
  • 2.2 What is Architecture in the Context of the TOGAF Standard?
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.2 Organizational Context
• 28. Capability-Based Planning
  • 28.4 Capabilities in an Enterprise Architecture Context
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
    • Project Context Diagram

continuity

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 4: Business Continuity

continuum

• 2. Core Concepts
  • 2.6 Enterprise Continuum
• 3. Definitions
  • 3.9 Architecture Continuum
  • 3.39 Enterprise Continuum
  • 3.71 Solutions Continuum
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.2 Patterns and the Architecture Continuum
• 35. Enterprise Continuum
  • 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
    • 35.4.2 Solutions Continuum

contract

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.2 Architecture Contract
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Contract Documentation Management
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.2 Contract between Architecture Design and Development Partners
    • 43.2.3 Contract between Architecting Function and Business Users
• A. Glossary of Supplementary Definitions
  • A.8 Contract

Contract/Measure

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Contract/Measure Catalog

Contract/Measure catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Contract/Measure Catalog

contracts

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts
• 43. Architecture Contracts

control

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 20: Control Technical Diversity
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Business Control
• A. Glossary of Supplementary Definitions
  • A.9 Control

core

• 2. Core Concepts
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content
      • Core Metamodel Entities

core concepts

• 2. Core Concepts

core content metamodel

• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail
    • 30.3.1 Core Content Metamodel

core content metamodel, concepts

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts

corporate

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes
• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.2 Elements of an Effective Architecture Governance Strategy
      • 44.3.2.1 Architecture Governance and Corporate Politics

corporate governance

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise

cost

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.2 How Much Does the TOGAF Standard Cost?

Cost/Benefit

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

COTS

• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
      • 16.5.3.2 Requirements Tools
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles
      • Principle 16: Technology Independence
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • 33.3.1 Basic Principles
      • 33.3.1.2 Building Block Design
• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.1 Purpose
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.6 COTS (where applicable)

course

• 3. Definitions
  • 3.35 Course of Action

course of action

• 3. Definitions
  • 3.35 Course of Action
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

create

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.9 Create the Architecture Definition Document
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.9 Create the Architecture Definition Document
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.9 Create the Architecture Definition Document
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.9 Create the Architecture Definition Document
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures

create architecture models

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process

creating

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision

creation

• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.2 Architecture View Creation Process

CRUD

• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept

CxO

• A. Glossary of Supplementary Definitions
  • A.10 CxO

cycle

• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles
  • 18.5 Iteration Considerations
    • 18.5.1 Iteration between ADM Cycles
    • 18.5.2 Iteration within an ADM Cycle

d

• 11. Phase D: Technology Architecture
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
• 40. Establishing an Architecture Capability
  • 40.6 Phase D: Technology Architecture

data

• 3. Definitions
  • 3.36 Data Architecture
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks
    • 9.3.2 Develop Baseline Data Architecture Description
    • 9.3.3 Develop Target Data Architecture Description
    • 9.3.8 Finalize the Data Architecture
  • 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

Data Architecture

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
• 3. Definitions
  • 3.36 Data Architecture
• 9. Phase C: Information Systems Architectures - Data Architecture

database

• A. Glossary of Supplementary Definitions
  • A.14 Database
  • A.15 Database Management System

database management system

• A. Glossary of Supplementary Definitions
  • A.15 Database Management System

data building blocks

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.2 Identify Required Catalogs of Data Building Blocks

data dictionary

• A. Glossary of Supplementary Definitions
  • A.11 Data Dictionary

Data Dissemination diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Dissemination Diagram

data element

• A. Glossary of Supplementary Definitions
  • A.12 Data Element

data entity

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities
• A. Glossary of Supplementary Definitions
  • A.13 Data Entity

Data Entity/Business Function matrix

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Business Function Matrix

Data Entity/Data Component catalog

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Data Component Catalog

data extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.4 Data Extensions

data governance

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.3 Data Governance

Data Lifecycle diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Lifecycle Diagram

data management

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.1 Data Management

data migration

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.2 Data Migration

Data Migration diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Migration Diagram

data principles, examples

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles

Data Security diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Security Diagram

Data Standards

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

deal

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?

Decision Log

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

decomposition

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Functional Decomposition Diagram
    • Organization Decomposition Diagram
  • 31.6.6 Phase D: Technology Architecture
    • Platform Decomposition Diagram
• A. Glossary of Supplementary Definitions
  • A.20 Functional Decomposition

deduction

• 24. Migration Planning Techniques
  • 24.1 Implementation Factor Assessment & Deduction Matrix

define

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.6 Define Scope
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.5 Define Candidate Roadmap Components
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.5 Define Candidate Roadmap Components
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.5 Define Candidate Roadmap Components

defined

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 3: Defined

defining

• 25. Interoperability Requirements
  • 25.2 Defining Interoperability

definition

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.9 Create the Architecture Definition Document
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.9 Create the Architecture Definition Document
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.9 Create the Architecture Definition Document
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.9 Create the Architecture Definition Document
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
• 24. Migration Planning Techniques
  • 24.3 Architecture Definition Increments Table
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.3 Architecture Definition Document
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.2 Data Definition

definitional

• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.1 Definitional Rigor

definitions

• 3. Definitions
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 14: Common Vocabulary and Data Definitions
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
• A. Glossary of Supplementary Definitions

Degrees of Interoperability

• 25. Interoperability Requirements
  • 25.4 Refining Interoperability

deliverable

• 2. Core Concepts
  • 2.5 Deliverables, Artifacts, and Building Blocks
• 3. Definitions
  • 3.37 Deliverable
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.4 Tailor Engagement Deliverables
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions

dependencies

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.6 Refine and Validate Dependencies
• 24. Migration Planning Techniques
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix

deploy

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.2 Deploy Monitoring Tools

deployment

• 14. Phase G: Implementation Governance
  • 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

Deployment Repository

• 37. Architecture Repository
  • 37.1 Overview

depth

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.2 Depth
• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

depth, enterprise

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.2 Depth

descriptions

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions

design

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.1 Architecture Patterns and Design Patterns
• 33. Building Blocks
  • 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
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.2 Contract between Architecture Design and Development Partners

design pattern

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.1 Architecture Patterns and Design Patterns

designs

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.1 Skills and Experience in Producing Designs

detail

• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail

Detailed Design Repository

• 37. Architecture Repository
  • 37.1 Overview

determine

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.2 Determine Business Constraints for Implementation
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.3 Determine Stakeholder Management Approach
• 26. Business Transformation Readiness Assessment
  • 26.2 Determine Readiness Factors

Determine/Confirm

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes

determining

• 25. Interoperability Requirements
  • 25.5 Determining Interoperability Requirements

develop

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.8 Develop Architecture Vision
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.2 Develop Baseline Business Architecture Description
    • 7.3.3 Develop Target Business Architecture Description
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.2 Develop Baseline Data Architecture Description
    • 9.3.3 Develop Target Data Architecture Description
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.2 Develop Baseline Application Architecture Description
    • 10.3.3 Develop Target Application Architecture Description
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.2 Develop Baseline Technology Architecture Description
    • 11.3.3 Develop Target Technology Architecture Description
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.5 Develop Change Requirements to Meet Performance Targets

developing

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.2 Developing the Baseline Description
• 19. Applying the ADM Across the Architecture Landscape
  • 19.4 Developing Architectures at Different Levels
• 20. Architecture Principles
  • 20.4 Developing Architecture Principles
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM

development

• 1. Introduction
  • 1.3 Executive Overview
    • What specifically would prompt the development of an Enterprise Architecture?
• 2. Core Concepts
  • 2.4 Architecture Development Method
• 3. Definitions
  • 3.10 Architecture Development Method (ADM)
• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management
    • 14.3.3 Guide Development of Solutions Deployment
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.2 Requirements Development
• 17. Introduction to Part III
  • 17.2 Techniques for Architecture Development
• 18. Applying Iteration to the ADM
  • 18.4 Approaches to Architecture Development
• 38. Tools for Architecture Development
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.2 Contract between Architecture Design and Development Partners
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 2: Under Development

diagram

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Required Diagrams
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.4 Identify Required Diagrams
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.4 Identify Required Diagrams
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.4 Identify Required Diagrams
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept
    • 31.6.2 Phase A: Architecture Vision
      • Value Chain Diagram
      • Solution Concept Diagram
      • Business Model Diagram
    • 31.6.3 Phase B: Business Architecture
      • 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
    • 31.6.4 Phase C: Data Architecture
      • 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 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
      • 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

dictionary

• A. Glossary of Supplementary Definitions
  • A.11 Data Dictionary

different

• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
• 19. Applying the ADM Across the Architecture Landscape
  • 19.4 Developing Architectures at Different Levels

dimensions

• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
    • 28.3.1 Capability Dimensions

direction

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Architecture Strategy and Direction Documentation

disciplines

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

dispensation

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Dispensations
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Dispensation

dispute

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Dispute Resolution

dissemination

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Dissemination Diagram

distribution

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Software Distribution Diagram

diversity

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 20: Control Technical Diversity

DoC

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework

document

• 1. Introduction
  • 1.1 Structure of this Document
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.9 Create the Architecture Definition Document
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.9 Create the Architecture Definition Document
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.9 Create the Architecture Definition Document
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.9 Create the Architecture Definition Document
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.3 Architecture Definition Document

documentation

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Architecture Strategy and Direction Documentation
      • Contract Documentation Management

does

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.2 How Much Does the TOGAF Standard Cost?
• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?

domain

• 3. Definitions
  • 3.11 Architecture Domain
• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.4 Architecture Domains
• A. Glossary of Supplementary Definitions
  • A.24 Information Domain

downloads

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.3 Downloads

driver

• A. Glossary of Supplementary Definitions
  • A.16 Driver

Driver/Goal/Objective

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Driver/Goal/Objective Catalog

Driver/Goal/Objective catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Driver/Goal/Objective Catalog

drivers

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.1 Drivers for Change
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.9 Business Principles, Business Goals, and Business Drivers

drivers for change

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.1 Drivers for Change

e

• 12. Phase E: Opportunities & Solutions
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
• 40. Establishing an Architecture Capability
  • 40.7 Phase E: Opportunities & Solutions

each

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.2 Assign a Business Value to Each Work Package

EAP

• 8. Phase C: Information Systems Architectures
  • 8.2 Approach

Ease-of-Use

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles
      • Principle 17: Ease-of-Use

effective

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.2 Elements of an Effective Architecture Governance Strategy

elaborate

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles

element

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.2 Elements of an Effective Architecture Governance Strategy
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.2 Elements of the ACMM
• A. Glossary of Supplementary Definitions
  • A.12 Data Element

emerging

• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.1 Emerging Technologies

emerging technologies

• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.1 Emerging Technologies

enablement

• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)

end

• A. Glossary of Supplementary Definitions
  • A.17 End User

end user

• A. Glossary of Supplementary Definitions
  • A.17 End User

Energistics

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.2 Architecture Repository
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Industry Architectures

engagement

• 18. Applying Iteration to the ADM
  • 18.3 Classes of Architecture Engagement
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.4 Tailor Engagement Deliverables

engineering

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Software Engineering Diagram

Engineering/Methods

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.8 System Engineering/Methods & Tools Checklist

Engineering/Overall

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists

enterprise

• 1. Introduction
  • 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?
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
• 2. Core Concepts
  • 2.6 Enterprise Continuum
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
• 3. Definitions
  • 3.38 Enterprise
  • 3.39 Enterprise Continuum
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.1 Reference Materials External to the Enterprise
  • 5.3 Steps
    • 5.3.1 Scope the Enterprise Organizations Impacted
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization
  • 5.5 Approach
    • 5.5.1 Enterprise
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.1 Reference Materials External to the Enterprise
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.1 Reference Materials External to the Enterprise
  • 14.3 Steps
    • 14.3.4 Perform Enterprise Architecture Compliance Reviews
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.1 Reference Materials External to the Enterprise
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process
• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 2: Maximize Benefit to the Enterprise
• 25. Interoperability Requirements
  • 25.3 Enterprise Operating Model
• 28. Capability-Based Planning
  • 28.4 Capabilities in an Enterprise Architecture Context
• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.2 Architecture Views and Architecture Viewpoints in Enterprise Architecture
    • 31.6.5 Phase C: Application Architecture
      • Enterprise Manageability Diagram
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.16 Organizational Model for Enterprise Architecture
• 35. Enterprise Continuum
  • 35.2 Enterprise Continuum and Architecture Re-Use
  • 35.3 Constituents of the Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
  • 35.5 The Enterprise Continuum and the ADM
  • 35.6 The Enterprise Continuum and Your Organization
    • 35.6.2 Your Enterprise

Enterprise Architect

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.2 Characterization in Terms of the Enterprise Continuum

Enterprise Architect, key characteristics

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.1 Skills and Experience in Producing Designs

Enterprise Architect, role of

• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.1 Overview

Enterprise Architecture

• 1. Introduction
  • 1.3 Executive Overview
    • What is an enterprise?

Enterprise Continuum

• 2. Core Concepts
  • 2.6 Enterprise Continuum
• 3. Definitions
  • 3.39 Enterprise Continuum
• 34. Introduction to Part V
• 35. Enterprise Continuum
• 38. Tools for Architecture Development
  • 38.1 Overview

Enterprise Continuum and Tools

• 1. Introduction
  • 1.1 Structure of this Document

Enterprise Manageability diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Enterprise Manageability Diagram

enterprise operating model

• 25. Interoperability Requirements
  • 25.3 Enterprise Operating Model

enterprise principles

• 20. Architecture Principles
  • 20.1 Introduction

Enterprise Repository

• 37. Architecture Repository
  • 37.1 Overview
  • 37.8 The Enterprise Repository

Enterprise Resource Planning system

• A. Glossary of Supplementary Definitions
  • A.18 Enterprise Resource Planning (ERP) System

entities

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities
  • 30.5 Content Metamodel Entities

entity

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• A. Glossary of Supplementary Definitions
  • A.13 Data Entity

Entity/Business

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Business Function Matrix

Entity/Data

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Data Component Catalog

environment

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Environment Management
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.7 Legal Environment

Environment diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Environments and Locations Diagram

environment management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

environments

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Environments and Locations Diagram

ERP

• A. Glossary of Supplementary Definitions
  • A.18 Enterprise Resource Planning (ERP) System

establish

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization
    • 5.3.4 Identify and Establish Architecture Principles
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.1 Establish the Architecture Project
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.1 Establish Value Realization Process

establishing

• 2. Core Concepts
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 40. Establishing an Architecture Capability

estimate

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

eTOM

• 37. Architecture Repository
  • 37.3 Reference Library
    • 37.3.1 Overview

evaluate

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.4 Evaluate Capabilities

evaluation

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

event

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Event Diagram
• A. Glossary of Supplementary Definitions
  • A.19 Event

Event diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Event Diagram

everybody's

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 3: Information Management is Everybody's Business

evolution

• 24. Migration Planning Techniques
  • 24.4 Transition Architecture State Evolution Table

example

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
• 23. Gap Analysis
  • 23.3 Example
• 31. Architectural Artifacts
  • 31.1 Basic Concepts
    • 31.1.1 Simple Example of an Architecture Viewpoint and Architecture View
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.1 Example of Architecture Views and Architecture Viewpoints
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels

execution

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.3 Method-Driven Approach to Execution

executive

• 1. Introduction
  • 1.3 Executive Overview

experience

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.1 Skills and Experience in Producing Designs
      • 46.6.3.4 Full Project Scope Experience
      • 46.6.3.7 Skills and Experience in One or More Industries

extension

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions
      • Required Extensions to the Core Metamodel

extensive

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

external

• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.1 Reference Materials External to the Enterprise
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.1 Reference Materials External to the Enterprise
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.1 Reference Materials External to the Enterprise
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.1 Reference Materials External to the Enterprise
• 37. Architecture Repository
  • 37.9 External Repositories
    • 37.9.1 External Reference Models
    • 37.9.2 External Standards

f

• 13. Phase F: Migration Planning
• 40. Establishing an Architecture Capability
  • 40.8 Phase F: Migration Planning

factor

• 24. Migration Planning Techniques
  • 24.1 Implementation Factor Assessment & Deduction Matrix
• 26. Business Transformation Readiness Assessment
  • 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

Federal Enterprise Architecture Business Reference Model

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository

few

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

finalize

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.8 Finalize the Business Architecture
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.8 Finalize the Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.8 Finalize the Application Architecture
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.8 Finalize the Technology Architecture

financial management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

flow

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Process Flow Diagram

FlowTM

• 3. Definitions
  • 3.22 Boundaryless Information FlowTM

footnotes

• 1. Introduction
  • 1.5 Why Join The Open Group?
    • Footnotes
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
    • Footnotes
• 18. Applying Iteration to the ADM
  • 18.6 Conclusions
    • Footnotes
• 25. Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions
    • Footnotes
• 26. Business Transformation Readiness Assessment
  • 26.7 Conclusion
    • Footnotes
• 30. Content Metamodel
  • 30.7 Metamodel Relationships
    • Footnotes
• 31. Architectural Artifacts
  • Footnotes
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • Footnotes
• 45. Architecture Maturity Models
  • 45.5 Conclusions
    • Footnotes

footprint

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Footprint Diagram

formal

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.7 Conduct Formal Stakeholder Review
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.7 Conduct Formal Stakeholder Review
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.7 Conduct Formal Stakeholder Review

formal stakeholder review

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.7 Conduct Formal Stakeholder Review
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.7 Conduct Formal Stakeholder Review
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.7 Conduct Formal Stakeholder Review

formulate

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.8 Formulate Implementation and Migration Strategy

foundation

• 3. Definitions
  • 3.40 Foundation Architecture
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.2 The ADM and the Foundation Architecture
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Foundation Architecture
    • 35.4.2 Solutions Continuum
      • Foundation Solutions

Foundation Architecture

• 3. Definitions
  • 3.40 Foundation Architecture
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Foundation Architecture

Foundation Solutions

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Foundation Solutions

framework

• 1. Introduction
  • 1.3 Executive Overview
    • What is an architecture framework?
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
• 2. Core Concepts
  • 2.10 Using the TOGAF Standard with Other Frameworks
• 3. Definitions
  • 3.12 Architecture Framework
  • 3.41 Framework
• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.2 Confirm Governance and Support Frameworks
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles
• 29. Introduction to Part IV
  • 29.3 Content Framework and the TOGAF ADM
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.21 Tailored Architecture Framework
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
    • 44.2.2 Architecture Governance Framework - Organizational Structure

framework(s

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

frameworks

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.5 Management Frameworks
    • 5.5.6 Relating the Management Frameworks

full

• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail
    • 30.3.2 Full Content Metamodel
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.4 Full Project Scope Experience

full content metamodel

• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail
    • 30.3.2 Full Content Metamodel

function

• 3. Definitions
  • 3.26 Business Function
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities
• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Entity/Business Function Matrix
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.3 Contract between Architecting Function and Business Users

functional

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Functional Decomposition Diagram
• A. Glossary of Supplementary Definitions
  • A.20 Functional Decomposition

functional decomposition

• A. Glossary of Supplementary Definitions
  • A.20 Functional Decomposition

Functional Decomposition diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Functional Decomposition Diagram

functions

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions

g

• 14. Phase G: Implementation Governance
• 27. Risk Management
  • 27.7 Risk Monitoring and Governance (Phase G)
• 40. Establishing an Architecture Capability
  • 40.9 Phase G: Implementation Governance

gap

• 3. Definitions
  • 3.42 Gap
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.4 Perform Gap Analysis
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.4 Perform Gap Analysis
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.4 Perform Gap Analysis
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
• 23. Gap Analysis

gap analysis

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.4 Perform Gap Analysis
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.4 Perform Gap Analysis
• 23. Gap Analysis

gaps

• 24. Migration Planning Techniques
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix

general

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.1 General
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.1 General
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.1 General
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.1 General Guidelines
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.1 General
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.1 General
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.5 IT General Knowledge Skills

generic

• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.2 Generic Characteristics
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.2 Nature of Governance
      • 44.1.2.1 Governance: A Generic Perspective
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.1 Generic Skills
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.1 Generic Role

glossary

• A. Glossary of Supplementary Definitions

goal

• A. Glossary of Supplementary Definitions
  • A.21 Goal

Goal/Objective/Service

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Goal/Objective/Service Diagram

Goal/Objective/Service diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Goal/Objective/Service Diagram

goals

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.9 Business Principles, Business Goals, and Business Drivers

Goals/Rationale

• 46. Architecture Skills Framework
  • 46.3 Goals/Rationale

GOTS

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles
      • Principle 16: Technology Independence

governance

• 3. Definitions
  • 3.13 Architecture Governance
  • 3.27 Business Governance
  • 3.43 Governance
• 4. Introduction to Part II
  • 4.4 Architecture Governance
• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.2 Confirm Governance and Support Frameworks
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.3 Data Governance
• 14. Phase G: Implementation Governance
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.6 Manage Governance Process
• 27. Risk Management
  • 27.7 Risk Monitoring and Governance (Phase G)
• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.15 Implementation Governance Model
• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

governance, characteristics

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.2 Nature of Governance
      • 44.1.2.2 Characteristics of Governance

governance extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions

Governance Log

• 2. Core Concepts
  • 2.7 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview
  • 37.5 Governance Log

Governance Log, contents of

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

granularity

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts

group

• 1. Introduction
  • 1.5 Why Join The Open Group?
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.9 Identify and Group Major Work Packages

guide

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.3 Guide Development of Solutions Deployment

guideline

• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.3 ADM and Supporting Guidelines and Techniques
• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.3 Guidelines for Maintenance versus Architecture Redesign
• 17. Introduction to Part III
  • 17.1 Guidelines for Adapting the ADM Process
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.1 General Guidelines
• 42. Architecture Compliance
  • 42.6 Architecture Compliance Review Guidelines
• A. Glossary of Supplementary Definitions
  • A.22 Guideline

guidelines, for adapting the ADM

• 17. Introduction to Part III
  • 17.1 Guidelines for Adapting the ADM Process

h

• 15. Phase H: Architecture Change Management
• 40. Establishing an Architecture Capability
  • 40.10 Phase H: Architecture Change Management

hardware

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.1 Hardware and Operating System Checklist
• A. Glossary of Supplementary Definitions
  • A.23 Hardware

Hillside Group

• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

hosting

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.4 Hosting, Data Types, and Sharing

how

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.2 How Much Does the TOGAF Standard Cost?

ICAM

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

ICOM

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

IDEF

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

identification

• 27. Risk Management
  • 27.3 Risk Identification

identify

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.4 Identify and Establish Architecture Principles
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.9 Identify and Group Major Work Packages
    • 12.3.10 Identify Transition Architectures
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.2 Identify Deployment Resources and Skills
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.1 Identify Stakeholders

idiom

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.1 Architecture Patterns and Design Patterns

if

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

II

• 4. Introduction to Part II

III

• 17. Introduction to Part III

III-RM

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Common Systems Architectures

impact

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.18 Requirements Impact Assessment

impacted

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.1 Scope the Enterprise Organizations Impacted

impacts

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.6 Resolve Impacts Across the Architecture Landscape
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.6 Resolve Impacts Across the Architecture Landscape
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.6 Resolve Impacts Across the Architecture Landscape

implement

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.5 Implement Business and IT Operations
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.7 Activate the Process to Implement Change

implementation

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.2 Determine Business Constraints for Implementation
    • 12.3.8 Formulate Implementation and Migration Strategy
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 13.3.6 Complete the Implementation and Migration Plan
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation

Implementation and Migration Plan

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.14 Implementation and Migration Plan

implementation governance

• 14. Phase G: Implementation Governance

Implementation Governance Model

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.15 Implementation Governance Model

in

• 2. Core Concepts
  • 2.2 What is Architecture in the Context of the TOGAF Standard?
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
• 28. Capability-Based Planning
  • 28.4 Capabilities in an Enterprise Architecture Context
• 30. Content Metamodel
  • 30.3 Content Metamodel in Detail
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.2 Architecture Views and Architecture Viewpoints in Enterprise Architecture
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • 33.3.1 Basic Principles
      • 33.3.1.1 Building Blocks in Architecture Design
    • 33.3.2 Building Block Specification Process in the ADM
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
• 38. Tools for Architecture Development
  • 38.2 Issues in Tool Standardization
• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 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.7 Skills and Experience in One or More Industries

including

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles

increment

• 3. Definitions
  • 3.32 Capability Increment

incremental change

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

increments

• 24. Migration Planning Techniques
  • 24.3 Architecture Definition Increments Table
• 28. Capability-Based Planning
  • 28.3 Concept of Capability-Based Planning
    • 28.3.2 Capability Increments

independence

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles
      • Principle 16: Technology Independence

indicator

• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

industries

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.7 Skills and Experience in One or More Industries

industry

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Industry Architectures
    • 35.4.2 Solutions Continuum
      • Industry Solutions

Industry Architectures

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Industry Architectures

Industry Solutions

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Industry Solutions

information

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
• 3. Definitions
  • 3.22 Boundaryless Information FlowTM
  • 3.44 Information
  • 3.45 Information System Service
  • 3.46 Information Technology (IT)
  • 3.73 Standards Information Base (SIB)
• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 3: Information Management is Everybody's Business
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

information domains

• A. Glossary of Supplementary Definitions
  • A.24 Information Domain

information exchange matrix

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

information system

• A. Glossary of Supplementary Definitions
  • A.25 Information System (IS)

Information Systems Architecture

• 8. Phase C: Information Systems Architectures

information system service

• 3. Definitions
  • 3.45 Information System Service

information technology

• 3. Definitions
  • 3.46 Information Technology (IT)

infrastructure

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.5 Infrastructure Consolidation Extensions
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.3 Applications Checklists
      • 42.5.3.1 Infrastructure (Enterprise Productivity) Applications

infrastructure consolidation extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.5 Infrastructure Consolidation Extensions

initial

• 27. Risk Management
  • 27.4 Initial Risk Assessment
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 1: Initial

initial risk assessment

• 27. Risk Management
  • 27.4 Initial Risk Assessment

inputs

• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.2 Non-Architectural Inputs
    • 5.2.3 Architectural Inputs

integration

• 4. Introduction to Part II
  • 4.6 Architecture Integration
• 36. Architecture Partitioning
  • 36.3 Integration
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.3 Applications Checklists
      • 42.5.3.3 Application Integration Approach
• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)

intellectual

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 9: Protection of Intellectual Property

interaction

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Interaction Matrix
  • 31.6.5 Phase C: Application Architecture
    • Application Interaction Matrix
• A. Glossary of Supplementary Definitions
  • A.26 Interaction
  • A.27 Interaction Model

interaction model

• A. Glossary of Supplementary Definitions
  • A.27 Interaction Model

interactions

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan

interface

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Interface Catalog
• A. Glossary of Supplementary Definitions
  • A.28 Interface

Interface catalog

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Interface Catalog

internal

• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.2 Basis of an Internal Architecture Practice

interoperability

• 3. Definitions
  • 3.47 Interoperability
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.5 Consolidate and Reconcile Interoperability Requirements
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 21: Interoperability
• 25. Interoperability Requirements
  • 25.2 Defining Interoperability
  • 25.4 Refining Interoperability
  • 25.5 Determining Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions

interoperability, categories

• 25. Interoperability Requirements
  • 25.2 Defining Interoperability

interoperability, refining

• 25. Interoperability Requirements
  • 25.4 Refining Interoperability

interoperability, requirements

• 25. Interoperability Requirements

interoperable

• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description

IPD-CMM

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

is

• 1. Introduction
  • 1.3 Executive Overview
    • What is an enterprise?
    • Why is an Enterprise Architecture needed?
    • What is an architecture framework?
• 2. Core Concepts
  • 2.1 What is the TOGAF Standard?
  • 2.2 What is Architecture in the Context of the TOGAF Standard?
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 3: Information Management is Everybody's Business
    • 20.6.2 Data Principles
      • Principle 10: Data is an Asset
      • Principle 11: Data is Shared
      • Principle 12: Data is Accessible
• A. Glossary of Supplementary Definitions
  • A.25 Information System (IS)

ISACF

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT

ISO/IEC/IEEE 42010:2011

• 2. Core Concepts
  • 2.2 What is Architecture in the Context of the TOGAF Standard?

issues

• 38. Tools for Architecture Development
  • 38.2 Issues in Tool Standardization

IT

• 3. Definitions
  • 3.46 Information Technology (IT)
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.5 Implement Business and IT Operations
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 8: IT Responsibility
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT

IT4IT Reference Architecture

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.5 Approach
    • 10.5.1 Architecture Repository
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Foundation Solutions
• 37. Architecture Repository
  • 37.3 Reference Library
    • 37.3.1 Overview
  • 37.7 Solutions Landscape

iteration

• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles
  • 18.5 Iteration Considerations
    • 18.5.1 Iteration between ADM Cycles
    • 18.5.2 Iteration within an ADM Cycle

iteration cycles

• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles

iteration of the ADM

• 18. Applying Iteration to the ADM

IT governance

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
    • 44.1.4 IT Governance

IT Governance Institute

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.4 IT Governance
      • 44.1.4.1 An IT Controls Framework - COBIT

ITIL

• 4. Introduction to Part II
  • 4.4 Architecture Governance
• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Foundation Solutions

IV

• 29. Introduction to Part IV
  • 29.4 Structure of Part IV

Java

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.3 Application Principles
      • Principle 16: Technology Independence

join

• 1. Introduction
  • 1.5 Why Join The Open Group?

key

• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
    • 4.2.1 Key Points
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.1 Determine/Confirm Key Corporate Change Attributes
• 44. 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
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.2 Key Areas
  • 44.3 Architecture Governance in Practice
    • 44.3.1 Architecture Governance - Key Success Factors
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

Key Performance Indicator

• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

kind

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
• 3. Definitions
  • 3.53 Model Kind

knowledge

• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.5 IT General Knowledge Skills

KPI

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs
• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

landscape

• 3. Definitions
  • 3.14 Architecture Landscape
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.6 Resolve Impacts Across the Architecture Landscape
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.6 Resolve Impacts Across the Architecture Landscape
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.6 Resolve Impacts Across the Architecture Landscape
• 19. Applying the ADM Across the Architecture Landscape
  • 19.2 Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise

language

• 31. Architectural Artifacts
  • 31.3 Views, Tools, and Languages
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description

law

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 7: Compliance with Law

leadership

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.5 Leadership

learned

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

legal

• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.7 Legal Environment

lessons

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

lessons learned process

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.1 Drivers for Change

level

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts
• 19. Applying the ADM Across the Architecture Landscape
  • 19.4 Developing Architectures at Different Levels
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 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

library

• 1. Introduction
  • 1.2 Structure of the TOGAF Library
• 3. Definitions
  • 3.84 Viewpoint Library
• 37. Architecture Repository
  • 37.3 Reference Library

lifecycle

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Product Lifecycle Diagram
  • 31.6.4 Phase C: Data Architecture
    • Data Lifecycle Diagram
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.3 Standards Lifecycle
• A. Glossary of Supplementary Definitions
  • A.30 Lifecycle

location

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Location Catalog
  • 31.6.5 Phase C: Application Architecture
    • Application and User Location Diagram
• A. Glossary of Supplementary Definitions
  • A.31 Location

Location catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Location Catalog

Location diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Environments and Locations Diagram

locations

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Environments and Locations Diagram

log

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

logical

• 3. Definitions
  • 3.48 Logical
• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Logical Data Diagram
• A. Glossary of Supplementary Definitions
  • A.32 Logical Application Component
  • A.33 Logical Data Component
  • A.34 Logical Technology Component

logical application component

• A. Glossary of Supplementary Definitions
  • A.32 Logical Application Component

logical data component

• A. Glossary of Supplementary Definitions
  • A.33 Logical Data Component

Logical Data diagram

• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Logical Data Diagram

logical technology component

• A. Glossary of Supplementary Definitions
  • A.34 Logical Technology Component

maintaining

• 2. Core Concepts
  • 2.8 Establishing and Maintaining an Enterprise Architecture Capability

maintenance

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.3 Guidelines for Maintenance versus Architecture Redesign

major

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.9 Identify and Group Major Work Packages

manage

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.3 Manage Risks
    • 15.3.6 Manage Governance Process

manageability

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Enterprise Manageability Diagram

managed

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 4: Managed

management

• 3. Definitions
  • 3.33 Communications and Stakeholder Management
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.5 Management Frameworks
    • 5.5.6 Relating the Management Frameworks
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.1 Data Management
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.4 Provide Analysis for Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

management frameworks

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

managing

• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)

Managing Successful Programs

• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)

map

• 3. Definitions
  • 3.55 Organization Map
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.5 Applying the Organization Map
• 21. Stakeholder Management
  • 21.4 Template Stakeholder Map
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Stakeholder Map Matrix
    • Business Capability Map
    • Value Stream Map
  • 31.6.3 Phase B: Business Architecture
    • Business Capability Map
    • Value Stream Map
    • Organization Map

marketing

• 26. Business Transformation Readiness Assessment
  • 26.6 Marketing the Implementation Plan

materials

• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.1 Reference Materials External to the Enterprise
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.1 Reference Materials External to the Enterprise
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.1 Reference Materials External to the Enterprise
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.1 Reference Materials External to the Enterprise

matrices

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.4 Identify Required Matrices
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.3 Identify Required Matrices
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.3 Identify Required Matrices
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.3 Identify Required Matrices
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept

matrix

• 24. Migration Planning Techniques
  • 24.1 Implementation Factor Assessment & Deduction Matrix
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix
• 31. Architectural Artifacts
  • 31.6 Architectural Artifacts by ADM Phase
    • Catalog, Matrix, and Diagram Concept
    • 31.6.2 Phase A: Architecture Vision
      • Stakeholder Map Matrix
    • 31.6.3 Phase B: Business Architecture
      • Business Interaction Matrix
      • Actor/Role Matrix
      • Value Stream/Capability Matrix
      • Strategy/Capability Matrix
      • Capability/Organization Matrix
    • 31.6.4 Phase C: Data Architecture
      • Data Entity/Business Function Matrix
      • Application/Data Matrix
    • 31.6.5 Phase C: Application Architecture
      • Application/Organization Matrix
      • Role/Application Matrix
      • Application/Function Matrix
      • Application Interaction Matrix
    • 31.6.6 Phase D: Technology Architecture
      • Application/Technology Matrix
• A. Glossary of Supplementary Definitions
  • A.36 Matrix

maturity

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
  • 45.4 Capability Maturity Models Integration (CMMI)

maturity model

• 26. Business Transformation Readiness Assessment
  • 26.3 Present Readiness Factors
• 45. Architecture Maturity Models

maximize

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 2: Maximize Benefit to the Enterprise

MDA

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools

meaning

• 42. Architecture Compliance
  • 42.2 Terminology: The Meaning of Architecture Compliance

measure

• A. Glossary of Supplementary Definitions
  • A.37 Measure

measured

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 5: Measured

meet

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.5 Develop Change Requirements to Meet Performance Targets

meeting

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Minutes of Previous Meeting
      • Schedule of Meetings

metadata

• 3. Definitions
  • 3.49 Metadata

metamodel

• 3. Definitions
  • 3.50 Metamodel
• 29. Introduction to Part IV
  • 29.2 Content Metamodel
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

metamodel relationships

• 30. Content Metamodel
  • 30.7 Metamodel Relationships

metaview

• A. Glossary of Supplementary Definitions
  • A.38 Metaview

method

• 2. Core Concepts
  • 2.4 Architecture Development Method
• 3. Definitions
  • 3.10 Architecture Development Method (ADM)
  • 3.51 Method
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.6 Access Method
• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.2 SCAMPI Method

Method-Driven

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.3 Method-Driven Approach to Execution

methods

• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.2 Business Skills & Methods

middleware

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.2 Software Services and Middleware Checklist

migration

• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.1 Key Considerations for Data Architecture
      • 9.5.1.2 Data Migration
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.8 Formulate Implementation and Migration Strategy
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
    • 13.3.6 Complete the Implementation and Migration Plan

Migration Planning

• 13. Phase F: Migration Planning
• 26. Business Transformation Readiness Assessment
  • 26.5 Readiness and Migration Planning

minutes

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Minutes of Previous Meeting

mitigation

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 27. Risk Management
  • 27.5 Risk Mitigation and Residual Risk Assessment

model

• 3. Definitions
  • 3.15 Architecture Model
  • 3.28 Business Model
  • 3.52 Modeling
  • 3.53 Model Kind
  • 3.59 Reference Model (RM)
• 25. Interoperability Requirements
  • 25.3 Enterprise Operating Model
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Business Model Diagram
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.15 Implementation Governance Model
    • 32.2.16 Organizational Model for Enterprise Architecture
• A. Glossary of Supplementary Definitions
  • A.27 Interaction Model

Model-Driven Architecture

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools

modeling

• 3. Definitions
  • 3.52 Modeling
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process
• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.3 Process Modeling Extensions

modeling process

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

model kind

• 3. Definitions
  • 3.53 Model Kind
• 31. Architectural Artifacts
  • 31.1 Basic Concepts

models

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
• 37. Architecture Repository
  • 37.9 External Repositories
    • 37.9.1 External Reference Models
• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)

monitoring

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.2 Deploy Monitoring Tools
• 27. Risk Management
  • 27.7 Risk Monitoring and Governance (Phase G)
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Monitoring and Reporting

more

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.7 Skills and Experience in One or More Industries

motivation

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.6 Motivation Extensions

motivation extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.6 Motivation Extensions

MSP

• 32. Architecture Deliverables
  • 32.1 Introduction
• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)

much

• 1. Introduction
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.2 How Much Does the TOGAF Standard Cost?

nature

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.2 Nature of Governance

need

• 31. Architectural Artifacts
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description
• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework

needed

• 1. Introduction
  • 1.3 Executive Overview
    • Why is an Enterprise Architecture needed?

needline

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

network

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Network and Communications Diagram

Network and Communications diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Network and Communications Diagram

networked

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Networked Computing/Hardware Diagram

Networked Computing/Hardware diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Networked Computing/Hardware Diagram

node connectivity diagram

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

Non-Architectural

• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.2 Non-Architectural Inputs
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.2 Non-Architectural Inputs
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.2 Non-Architectural Inputs
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.2 Non-Architectural Inputs
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.2 Non-Architectural Inputs
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.2 Non-Architectural Inputs
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.2 Non-Architectural Inputs
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.2 Non-Architectural Inputs
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.2 Non-Architectural Inputs
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.2 Non-Architectural Inputs

none

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 0: None

objective

• 3. Definitions
  • 3.54 Objective
• 5. Preliminary Phase
  • 5.1 Objectives
• 6. Phase A: Architecture Vision
  • 6.1 Objectives
• 7. Phase B: Business Architecture
  • 7.1 Objectives
• 8. Phase C: Information Systems Architectures
  • 8.1 Objectives
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.1 Objectives
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.1 Objectives
• 11. Phase D: Technology Architecture
  • 11.1 Objectives
• 12. Phase E: Opportunities & Solutions
  • 12.1 Objectives
• 13. Phase F: Migration Planning
  • 13.1 Objectives
• 14. Phase G: Implementation Governance
  • 14.1 Objectives
• 15. Phase H: Architecture Change Management
  • 15.1 Objectives
• 16. ADM Architecture Requirements Management
  • 16.1 Objectives

Object Management Forum

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository

Object Management Group

• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.5 Approach
    • 10.5.1 Architecture Repository

OLA

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Compliance Assessments
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Compliance

OMG

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques
    • 7.5.7 Architecture Repository
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
  • 10.5 Approach
    • 10.5.1 Architecture Repository
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content

one

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines
      • 46.6.3.7 Skills and Experience in One or More Industries

open

• 1. Introduction
  • 1.5 Why Join The Open Group?
• A. Glossary of Supplementary Definitions
  • A.39 Open System

open system

• A. Glossary of Supplementary Definitions
  • A.39 Open System

operating

• 25. Interoperability Requirements
  • 25.3 Enterprise Operating Model
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.1 Hardware and Operating System Checklist

operation

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board

operational

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.3 Operational Benefits
• A. Glossary of Supplementary Definitions
  • A.40 Operational Governance

operational governance

• A. Glossary of Supplementary Definitions
  • A.40 Operational Governance

operational-level agreement

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Compliance Assessments
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Compliance

operations

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.5 Implement Business and IT Operations

operations management

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

opportunities

• 12. Phase E: Opportunities & Solutions
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
• 40. Establishing an Architecture Capability
  • 40.7 Phase E: Opportunities & Solutions

Opportunities & Solutions

• 12. Phase E: Opportunities & Solutions

organization

• 3. Definitions
  • 3.55 Organization Map
• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.5 Applying the Organization Map
• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Organization Decomposition Diagram
    • Organization Map
• 35. Enterprise Continuum
  • 35.6 The Enterprise Continuum and Your Organization

Organization/Actor

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Organization/Actor Catalog

Organization/Actor catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Organization/Actor Catalog

organizational

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.2 Organizational Context
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.16 Organizational Model for Enterprise Architecture
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.2 Architecture Governance Framework - Organizational Structure

Organizational Model

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.16 Organizational Model for Enterprise Architecture

Organization Decomposition diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Organization Decomposition Diagram

organization map

• 3. Definitions
  • 3.55 Organization Map
• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.5 Applying the Organization Map
• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Organization Map

organization mapping

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

organizations

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.1 Scope the Enterprise Organizations Impacted

Organization-Specific

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Organization-Specific Architectures
    • 35.4.2 Solutions Continuum
      • Organization-Specific Solutions

Organization-Specific Architectures

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Organization-Specific Architectures

Organization-Specific Solutions

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Organization-Specific Solutions

organization unit

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

organizing

• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise

orientation

• 3. Definitions
  • 3.66 Service Orientation
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 6: Service Orientation

outputs

• 5. Preliminary Phase
  • 5.4 Outputs
• 6. Phase A: Architecture Vision
  • 6.4 Outputs
• 7. Phase B: Business Architecture
  • 7.4 Outputs
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.4 Outputs
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.4 Outputs
• 11. Phase D: Technology Architecture
  • 11.4 Outputs
• 12. Phase E: Opportunities & Solutions
  • 12.4 Outputs
• 13. Phase F: Migration Planning
  • 13.4 Outputs
• 14. Phase G: Implementation Governance
  • 14.4 Outputs
• 15. Phase H: Architecture Change Management
  • 15.4 Outputs
• 16. ADM Architecture Requirements Management
  • 16.4 Outputs

overall

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process

overview

• 1. Introduction
  • 1.3 Executive Overview
• 4. Introduction to Part II
  • 4.1 ADM Overview
• 18. Applying Iteration to the ADM
  • 18.1 Overview
• 19. Applying the ADM Across the Architecture Landscape
  • 19.1 Overview
• 25. Interoperability Requirements
  • 25.1 Overview
• 28. Capability-Based Planning
  • 28.1 Overview
• 29. Introduction to Part IV
  • 29.1 Overview
• 30. Content Metamodel
  • 30.1 Overview
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.2 Overview of the Content Metamodel
• 31. Architectural Artifacts
  • 31.3 Views, Tools, and Languages
    • 31.3.1 Overview
• 33. Building Blocks
  • 33.1 Overview
  • 33.2 Introduction to Building Blocks
    • 33.2.1 Overview
• 35. Enterprise Continuum
  • 35.1 Overview
• 36. Architecture Partitioning
  • 36.1 Overview
• 37. Architecture Repository
  • 37.1 Overview
  • 37.3 Reference Library
    • 37.3.1 Overview
  • 37.4 Standards Information Base
    • 37.4.1 Overview
  • 37.5 Governance Log
    • 37.5.1 Overview
  • 37.6 The Architecture Requirements Repository
    • 37.6.1 Overview
• 38. Tools for Architecture Development
  • 38.1 Overview
• 39. Introduction to Part VI
  • 39.1 Overview
• 40. Establishing an Architecture Capability
  • 40.1 Overview
• 42. Architecture Compliance
  • 42.4 Architecture Compliance Review Process
    • 42.4.1 Overview
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.5 Architecture Governance: Overview
  • 44.2 Architecture Governance Framework
    • 44.2.2 Architecture Governance Framework - Organizational Structure
      • 44.2.2.1 Overview
• 45. Architecture Maturity Models
  • 45.1 Overview
  • 45.3 US DoC ACMM Framework
    • 45.3.1 Overview
• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.1 Overview

package

• 3. Definitions
  • 3.85 Work Package
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.2 Assign a Business Value to Each Work Package

packaged

• A. Glossary of Supplementary Definitions
  • A.41 Packaged Services

packaged services

• A. Glossary of Supplementary Definitions
  • A.41 Packaged Services

packages

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.9 Identify and Group Major Work Packages

paradigm

• 28. Capability-Based Planning
  • 28.2 Capability-Based Planning Paradigm

part

• 4. Introduction to Part II
• 17. Introduction to Part III
• 29. Introduction to Part IV
  • 29.4 Structure of Part IV

partitioned

• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures

partitioning

• 36. Architecture Partitioning

partners

• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.2 Contract between Architecture Design and Development Partners

pattern

• 3. Definitions
  • 3.56 Pattern
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.2 Content of a Pattern
  • 22.2 Some Pattern Resources

pattern resources

• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

patterns

• 22. Architecture Patterns
  • 22.1 Introduction
    • 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

patterns-discussion FAQ

• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

patterns home page

• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

P-CMM

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

perform

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.4 Perform Gap Analysis
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.4 Perform Gap Analysis
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.4 Perform Gap Analysis
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.4 Perform Enterprise Architecture Compliance Reviews
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation

performance

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.5 Develop Change Requirements to Meet Performance Targets
• A. Glossary of Supplementary Definitions
  • A.29 Key Performance Indicator (KPI)

performance management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

performance measurement

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

period

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.3 Time Period
• A. Glossary of Supplementary Definitions
  • A.62 Time Period

personal

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.6 Personal and Professional Skills

personnel

• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.3 Governance and Personnel Scenarios

perspective

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.2 Nature of Governance
      • 44.1.2.1 Governance: A Generic Perspective

phase

• 5. Preliminary Phase
• 6. Phase A: Architecture Vision
• 7. Phase B: Business Architecture
• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
• 11. Phase D: Technology Architecture
• 12. Phase E: Opportunities & Solutions
• 13. Phase F: Migration Planning
• 14. Phase G: Implementation Governance
• 15. Phase H: Architecture Change Management
• 27. Risk Management
  • 27.7 Risk Monitoring and Governance (Phase G)
• 31. Architectural Artifacts
  • 31.6.1 Preliminary Phase
  • 31.6.2 Phase A: Architecture Vision
  • 31.6.3 Phase B: Business Architecture
  • 31.6.4 Phase C: Data Architecture
  • 31.6.5 Phase C: Application Architecture
  • 31.6.6 Phase D: Technology Architecture
  • 31.6.7 Phase E: Opportunities and Solutions

Phase A

• 6. Phase A: Architecture Vision

Phase B

• 7. Phase B: Business Architecture

Phase C

• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture

Phase D

• 11. Phase D: Technology Architecture

Phase E

• 12. Phase E: Opportunities & Solutions

Phase F

• 13. Phase F: Migration Planning

Phase G

• 14. Phase G: Implementation Governance

Phase H

• 15. Phase H: Architecture Change Management

phases

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

physical

• 3. Definitions
  • 3.57 Physical
• A. Glossary of Supplementary Definitions
  • A.42 Physical Application Component
  • A.43 Physical Data Component
  • A.44 Physical Technology Component

physical application component

• A. Glossary of Supplementary Definitions
  • A.42 Physical Application Component

physical data component

• A. Glossary of Supplementary Definitions
  • A.43 Physical Data Component

physical technology component

• A. Glossary of Supplementary Definitions
  • A.44 Physical Technology Component

plan

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 13.3.6 Complete the Implementation and Migration Plan
• 26. Business Transformation Readiness Assessment
  • 26.6 Marketing the Implementation Plan
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.12 Communications Plan
    • 32.2.14 Implementation and Migration Plan

planning

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 13. Phase F: Migration Planning
• 24. Migration Planning Techniques
• 26. Business Transformation Readiness Assessment
  • 26.5 Readiness and Migration Planning
• 28. Capability-Based Planning
  • 28.2 Capability-Based Planning Paradigm
  • 28.3 Concept of Capability-Based Planning

platform

• 3. Definitions
  • 3.5 Application Platform
• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Platform Decomposition Diagram

Platform Decomposition diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Platform Decomposition Diagram

PMBOK

• 32. Architecture Deliverables
  • 32.1 Introduction

points

• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
    • 4.2.1 Key Points

policy

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Policy Management and Take-On

politics

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.2 Elements of an Effective Architecture Governance Strategy
      • 44.3.2.1 Architecture Governance and Corporate Politics

portability

• A. Glossary of Supplementary Definitions
  • A.45 Portability

portfolio

• 3. Definitions
  • 3.68 Service Portfolio
• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application Portfolio Catalog
  • 31.6.6 Phase D: Technology Architecture
    • Technology Portfolio Catalog
• A. Glossary of Supplementary Definitions
  • A.46 Portfolio

portfolio management

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

positions

• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.2 Classify Stakeholder Positions

Post-Implementation

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation

potential

• 25. Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions

practice

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.2 Basis of an Internal Architecture Practice

preliminary

• 5. Preliminary Phase
• 31. Architectural Artifacts
  • 31.6.1 Preliminary Phase
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures
    • 36.2.1 Activities within the Preliminary Phase

Preliminary Phase

• 5. Preliminary Phase

preparation

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.2 Preparation

present

• 26. Business Transformation Readiness Assessment
  • 26.3 Present Readiness Factors

previous

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Minutes of Previous Meeting

primacy

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 1: Primacy of Principles

PRINCE2

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process
• 32. Architecture Deliverables
  • 32.1 Introduction
• A. Glossary of Supplementary Definitions
  • A.47 PRINCE2

principle

• 3. Definitions
  • 3.16 Architecture Principle
  • 3.58 Principle
• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.4 Identify and Establish Architecture Principles
  • 5.5 Approach
    • 5.5.4 Principles
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
• 20. Architecture Principles
  • 20.2 Characteristics of Architecture Principles
  • 20.3 Components of Architecture Principles
  • 20.4 Developing Architecture Principles
    • 20.4.1 Qualities of Principles

Principles catalog

• 31. Architectural Artifacts
  • 31.6.1 Preliminary Phase
    • Principles Catalog

priorities

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management

prioritize

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

process

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.1 Determine Overall Modeling Process
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.1 Determine Overall Modeling Process
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.1 Determine Overall Modeling Process
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.1 Establish Value Realization Process
    • 15.3.6 Manage Governance Process
    • 15.3.7 Activate the Process to Implement Change
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process
• 17. Introduction to Part III
  • 17.1 Guidelines for Adapting the ADM Process
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.3 Process Modeling Extensions
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
    • 31.2.2 Architecture View Creation Process
    • 31.6.3 Phase B: Business Architecture
      • Process Flow Diagram
• 33. Building Blocks
  • 33.3 Building Blocks and the ADM
    • 33.3.2 Building Block Specification Process in the ADM
• 42. Architecture Compliance
  • 42.4 Architecture Compliance Review Process
• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
• A. Glossary of Supplementary Definitions
  • A.48 Process

Process/Application

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Process/Application Realization Diagram

Process/Application Realization diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Process/Application Realization Diagram

processes

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • 44.2.1.2 Key Architecture Governance Processes

Process/Event/Control/Product

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Process/Event/Control/Product Catalog

Process/Event/Control/Product catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Process/Event/Control/Product Catalog

Process Flow diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Process Flow Diagram

processing

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Processing Diagram

Processing diagram

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Processing Diagram

process modeling

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

process modeling extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.3 Process Modeling Extensions

Processors/Servers/Clients

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.2 Processors/Servers/Clients

process status

• 4. Introduction to Part II
  • 4.4 Architecture Governance

process tailoring

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

producing

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.1 Skills and Experience in Producing Designs

product

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Product Lifecycle Diagram
• A. Glossary of Supplementary Definitions
  • A.49 Product

productivity

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.3 Applications Checklists
      • 42.5.3.1 Infrastructure (Enterprise Productivity) Applications

Product Lifecycle diagram

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Product Lifecycle Diagram

Product Line Architecture

• 4. Introduction to Part II
  • 4.3 Adapting the ADM

professional

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.6 Personal and Professional Skills

proficiency

• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.4 Proficiency Levels

profile

• A. Glossary of Supplementary Definitions
  • A.50 Profile

profiling

• A. Glossary of Supplementary Definitions
  • A.51 Profiling

program

• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.4 Program or Project Management Skills
• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)
  • A.52 Program

project

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.1 Establish the Architecture Project
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
    • Project Context Diagram
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.4 Program or Project Management Skills
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.4 Full Project Scope Experience
• A. Glossary of Supplementary Definitions
  • A.53 Project

Project Context diagram

• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
    • Project Context Diagram

project management

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

Project Portfolio

• 37. Architecture Repository
  • 37.5 Governance Log
    • 37.5.2 Contents of the Governance Log

projects

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

prompt

• 1. Introduction
  • 1.3 Executive Overview
    • What specifically would prompt the development of an Enterprise Architecture?

property

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 9: Protection of Intellectual Property

propositions

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs

protection

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 9: Protection of Intellectual Property

provide

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.4 Provide Analysis for Architecture Change Management

purpose

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions
      • Purpose
    • 30.4.2 Services Extensions
      • Purpose
    • 30.4.3 Process Modeling Extensions
      • Purpose
    • 30.4.4 Data Extensions
      • Purpose
    • 30.4.5 Infrastructure Consolidation Extensions
      • Purpose
    • 30.4.6 Motivation Extensions
      • Purpose
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.2 Architecture Contract
      • Purpose
    • 32.2.3 Architecture Definition Document
      • Purpose
    • 32.2.4 Architecture Principles
      • Purpose
    • 32.2.5 Architecture Repository
      • Purpose
    • 32.2.6 Architecture Requirements Specification
      • Purpose
    • 32.2.7 Architecture Roadmap
      • Purpose
    • 32.2.8 Architecture Vision
      • Purpose
    • 32.2.9 Business Principles, Business Goals, and Business Drivers
      • Purpose
    • 32.2.10 Capability Assessment
      • Purpose
    • 32.2.11 Change Request
      • Purpose
    • 32.2.12 Communications Plan
      • Purpose
    • 32.2.13 Compliance Assessment
      • Purpose
    • 32.2.14 Implementation and Migration Plan
      • Purpose
    • 32.2.15 Implementation Governance Model
      • Purpose
    • 32.2.16 Organizational Model for Enterprise Architecture
      • Purpose
    • 32.2.17 Request for Architecture Work
      • Purpose
    • 32.2.18 Requirements Impact Assessment
      • Purpose
    • 32.2.20 Statement of Architecture Work
      • Purpose
    • 32.2.21 Tailored Architecture Framework
      • Purpose
• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.1 Purpose

qualities

• 20. Architecture Principles
  • 20.4 Developing Architecture Principles
    • 20.4.1 Qualities of Principles

quality

• A. Glossary of Supplementary Definitions
  • A.58 Service Quality

quality management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

rating

• 26. Business Transformation Readiness Assessment
  • 26.4 Assess Readiness Factors
    • 26.4.2 Readiness Factor Rating

readiness

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.5 Assess Readiness for Business Transformation
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.7 Confirm Readiness and Risk for Business Transformation
• 26. Business Transformation Readiness Assessment
  • 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

readiness factors

• 26. Business Transformation Readiness Assessment
  • 26.2 Determine Readiness Factors

readiness planning

• 26. Business Transformation Readiness Assessment
  • 26.5 Readiness and Migration Planning

realization

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.1 Establish Value Realization Process
• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Process/Application Realization Diagram

re-architecting change

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

recency

• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise

reconcile

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.5 Consolidate and Reconcile Interoperability Requirements

reconciling

• 25. Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions

redesign

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.3 Guidelines for Maintenance versus Architecture Redesign

reference

• 3. Definitions
  • 3.59 Reference Model (RM)
• 5. Preliminary Phase
  • 5.2 Inputs
    • 5.2.1 Reference Materials External to the Enterprise
• 6. Phase A: Architecture Vision
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase B: Business Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
• 12. Phase E: Opportunities & Solutions
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
• 13. Phase F: Migration Planning
  • 13.2 Inputs
    • 13.2.1 Reference Materials External to the Enterprise
• 14. Phase G: Implementation Governance
  • 14.2 Inputs
    • 14.2.1 Reference Materials External to the Enterprise
• 15. Phase H: Architecture Change Management
  • 15.2 Inputs
    • 15.2.1 Reference Materials External to the Enterprise
• 37. Architecture Repository
  • 37.3 Reference Library
  • 37.9 External Repositories
    • 37.9.1 External Reference Models

reference data

• 4. Introduction to Part II
  • 4.4 Architecture Governance

Reference Library

• 2. Core Concepts
  • 2.7 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview
  • 37.3 Reference Library

reference models

• 3. Definitions
  • 3.59 Reference Model (RM)
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools

refine

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.6 Refine and Validate Dependencies

refining

• 25. Interoperability Requirements
  • 25.4 Refining Interoperability

related

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions

relating

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.6 Relating the Management Frameworks

relationship

• 30. Content Metamodel
  • 30.7 Metamodel Relationships
• 35. Enterprise Continuum
  • 35.6 The Enterprise Continuum and Your Organization
    • 35.6.1 Relationships
• 43. Architecture Contracts
  • 43.3 Relationship to Architecture Governance

reporting

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Monitoring and Reporting

repositories

• 37. Architecture Repository
  • 37.9 External Repositories

repository

• 2. Core Concepts
  • 2.7 Architecture Repository
• 3. Definitions
  • 3.60 Repository
• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.5 Approach
    • 9.5.2 Architecture Repository
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.5 Approach
    • 10.5.1 Architecture Repository
• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.2 Architecture Repository
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.5 Architecture Repository
• 37. Architecture Repository
  • 37.6 The Architecture Requirements Repository
    • 37.6.2 Contents of the Architecture Requirements Repository

request

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.11 Change Request
    • 32.2.17 Request for Architecture Work

Request for Architecture Work

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.1 General
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.17 Request for Architecture Work

requests

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Requests for Change

required

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 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
• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.1 Governance Extensions
      • Required Extensions to the Core Metamodel
    • 30.4.2 Services Extensions
      • Required Extensions to the Core Metamodel
    • 30.4.3 Process Modeling Extensions
      • Required Extensions to the Core Metamodel
    • 30.4.4 Data Extensions
      • Required Extensions to the Core Metamodel
    • 30.4.5 Infrastructure Consolidation Extensions
      • Required Extensions to the Core Metamodel
    • 30.4.6 Motivation Extensions
      • Required Extensions to the Core Metamodel

requirement

• 3. Definitions
  • 3.61 Requirement
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.6 Identify Types of Requirement to be Collected
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.5 Identify Types of Requirement to be Collected
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.5 Identify Types of Requirement to be Collected
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.5 Identify Types of Requirement to be Collected

Requirement for Architecture Work

• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.3 Requirements for Architecture Work

requirements

• 3. Definitions
  • 3.61 Requirement
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.3 Requirements for Architecture Work
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.5 Identify Types of Requirement to be Collected
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.5 Identify Types of Requirement to be Collected
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions
    • 12.3.5 Consolidate and Reconcile Interoperability Requirements
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.5 Develop Change Requirements to Meet Performance Targets
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.2 Requirements Development
    • 16.5.3 Resources
      • 16.5.3.2 Requirements Tools

Requirements-Based

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 18: Requirements-Based Change

Requirements catalog

• 31. Architectural Artifacts
  • 31.6.8 Requirements Management
    • Requirements Catalog

Requirements Impact Assessment

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.18 Requirements Impact Assessment

requirements tools

• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
      • 16.5.3.2 Requirements Tools

residual

• 27. Risk Management
  • 27.5 Risk Mitigation and Residual Risk Assessment
  • 27.6 Conduct Residual Risk Assessment

residual risk assessment

• 27. Risk Management
  • 27.6 Conduct Residual Risk Assessment

resolution

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Dispute Resolution

resolve

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.6 Resolve Impacts Across the Architecture Landscape
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.6 Resolve Impacts Across the Architecture Landscape
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.6 Resolve Impacts Across the Architecture Landscape

resource

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• A. Glossary of Supplementary Definitions
  • A.18 Enterprise Resource Planning (ERP) System

resource management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

resources

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.2 Identify Deployment Resources and Skills
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

responsibilities

• 41. Architecture Board
  • 41.2 Responsibilities

responsibility

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 8: IT Responsibility
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.5 Architecture Governance: Overview
      • 44.1.5.2 Architecture Governance as a Board-Level Responsibility

responsive

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 19: Responsive Change Management

results

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

Re-Use

• 35. Enterprise Continuum
  • 35.2 Enterprise Continuum and Architecture Re-Use

review

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.7 Conduct Formal Stakeholder Review
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.7 Conduct Formal Stakeholder Review
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.7 Conduct Formal Stakeholder Review
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
    • 12.3.4 Review Consolidated Requirements Across Related Business Functions
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.4 Perform Enterprise Architecture Compliance Reviews
    • 14.3.6 Perform Post-Implementation Review and Close the Implementation
• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
  • 42.4 Architecture Compliance Review Process
  • 42.5 Architecture Compliance Review Checklists
  • 42.6 Architecture Compliance Review Guidelines
    • 42.6.2 Conducting Architecture Compliance Reviews

rigor

• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
    • 46.2.1 Definitional Rigor

risk

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.7 Confirm Readiness and Risk for Business Transformation
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
• 27. Risk Management
  • 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)

risk assessment

• 27. Risk Management
  • 27.4 Initial Risk Assessment

risk classification

• 27. Risk Management
  • 27.2 Risk Classification

risk identification

• 27. Risk Management
  • 27.3 Risk Identification

risk management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 27. Risk Management
• A. Glossary of Supplementary Definitions
  • A.54 Risk Management

risk management, best practice

• 27. Risk Management
  • 27.4 Initial Risk Assessment

Risk Management Plan

• 27. Risk Management
  • 27.3 Risk Identification

risk monitoring

• 27. Risk Management
  • 27.7 Risk Monitoring and Governance (Phase G)

risks

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.3 Manage Risks
• 26. Business Transformation Readiness Assessment
  • 26.4 Assess Readiness Factors
    • 26.4.3 Readiness Factor Risks & Actions

RM

• 3. Definitions
  • 3.59 Reference Model (RM)

roadmap

• 3. Definitions
  • 3.62 Roadmap
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.5 Define Candidate Roadmap Components
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.5 Define Candidate Roadmap Components
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.5 Define Candidate Roadmap Components
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.7 Architecture Roadmap

roadmap components

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.5 Define Candidate Roadmap Components
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.5 Define Candidate Roadmap Components

role

• 3. Definitions
  • 3.63 Role
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities
• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Role Catalog
• 41. Architecture Board
  • 41.1 Role
• 43. Architecture Contracts
  • 43.1 Role
• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
  • 46.5 Enterprise Architecture Role and Skill Definitions
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.1 Generic Role

Role/Application

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Role/Application Matrix

Role/Application matrix

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Role/Application Matrix

Role catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Role Catalog

roles

• 42. Architecture Compliance
  • 42.4 Architecture Compliance Review Process
    • 42.4.2 Roles
• 46. Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.2 TOGAF Roles

SA-CMM

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

sample

• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.1 Identify Stakeholders
      • 21.3.1.1 Sample Stakeholder Analysis

SANS Institute

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 9: Protection of Intellectual Property

SBB

• 3. Definitions
  • 3.70 Solution Building Block (SBB)
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.1 Background
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.19 Solution Building Blocks
• 33. Building Blocks
  • 33.1 Overview
  • 33.2 Introduction to Building Blocks
    • 33.2.4 Solution Building Blocks

scalability

• A. Glossary of Supplementary Definitions
  • A.55 Scalability

SCAMPI

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.2 SCAMPI Method

scenarios

• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
      • 16.5.3.1 Business Scenarios
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.4 Patterns and Business Scenarios
• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.3 Governance and Personnel Scenarios

schedule

• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Schedule of Meetings

scope

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.1 Scope the Enterprise Organizations Impacted
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.6 Define Scope
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.1 Confirm Scope and Priorities for Deployment with Development Management
• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.4 Full Project Scope Experience

scoping

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture

scoping the architecture

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture

SE-CMM

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

secure

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval

security

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 15: Data Security
• 31. Architectural Artifacts
  • 31.6.4 Phase C: Data Architecture
    • Data Security Diagram
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.5 Security Checklist
• A. Glossary of Supplementary Definitions
  • A.56 Security

Security/Protection

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.3 Security/Protection

segment

• 3. Definitions
  • 3.64 Segment Architecture

segment architect

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.2 Characterization in Terms of the Enterprise Continuum

Segment Architecture

• 3. Definitions
  • 3.64 Segment Architecture
• 19. Applying the ADM Across the Architecture Landscape
  • 19.2 Architecture Landscape
• 37. Architecture Repository
  • 37.2 Architecture Landscape

Segment Architecture Requirements

• 37. Architecture Repository
  • 37.6 The Architecture Requirements Repository
    • 37.6.2 Contents of the Architecture Requirements Repository

SEI

• 45. Architecture Maturity Models
  • 45.2 Background

select

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.6 Select Services

selected

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

server

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.4 Application Server
      • 42.5.7.5 Data Server
• A. Glossary of Supplementary Definitions
  • A.57 Server

service

• 3. Definitions
  • 3.29 Business Service
  • 3.45 Information System Service
  • 3.65 Service
  • 3.66 Service Orientation
  • 3.68 Service Portfolio
  • 3.79 Technology Service
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Service Granularity Level, Boundaries, and Contracts
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 6: Service Orientation
• A. Glossary of Supplementary Definitions
  • A.58 Service Quality

Service/Function

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Service/Function Catalog

Service/Information

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Service/Information Diagram

service-level agreement

• 41. Architecture Board
  • 41.2 Responsibilities
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.3 Contract between Architecting Function and Business Users
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Compliance

service management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity

Service Management Repository

• 37. Architecture Repository
  • 37.1 Overview

service orientation

• 3. Definitions
  • 3.66 Service Orientation

Service-Oriented

• 3. Definitions
  • 3.67 Service-Oriented Architecture (SOA)

Service-Oriented Architecture

• 3. Definitions
  • 3.67 Service-Oriented Architecture (SOA)

service portfolio

• 3. Definitions
  • 3.68 Service Portfolio

service qualities

• A. Glossary of Supplementary Definitions
  • A.58 Service Quality

services

• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.6 Select Services
• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.2 Services Extensions
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.2 Software Services and Middleware Checklist
    • 42.5.4 Information Management Checklists
      • 42.5.4.5 Common Services
• A. Glossary of Supplementary Definitions
  • A.41 Packaged Services

services extensions

• 30. Content Metamodel
  • 30.4 Content Metamodel Extensions
    • 30.4.2 Services Extensions

set

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles

setting

• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board

shared

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 11: Data is Shared

sharing

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.4 Hosting, Data Types, and Sharing

SIB

• 2. Core Concepts
  • 2.7 Architecture Repository
• 3. Definitions
  • 3.73 Standards Information Base (SIB)
• 37. Architecture Repository
  • 37.1 Overview

SID

• 37. Architecture Repository
  • 37.3 Reference Library
    • 37.3.1 Overview

simple

• 31. Architectural Artifacts
  • 31.1 Basic Concepts
    • 31.1.1 Simple Example of an Architecture Viewpoint and Architecture View

simplification change

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.2 Enterprise Architecture Change Management Process

size

• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board
    • 41.3.2 Size of the Board

skill

• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.2 Identify Deployment Resources and Skills
• 46. Architecture Skills Framework
  • 46.2 Need for an Enterprise Architecture Skills Framework
  • 46.4 Enterprise Architecture Role and Skill Categories
    • 46.4.3 Categories of Skills

SLA

• 41. Architecture Board
  • 41.2 Responsibilities
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.3 Contract between Architecting Function and Business Users
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Compliance

SMART

• 25. Interoperability Requirements
  • 25.4 Refining Interoperability
• 31. Architectural Artifacts
  • 31.1 Basic Concepts
• A. Glossary of Supplementary Definitions
  • A.59 SMART

SOA

• 3. Definitions
  • 3.67 Service-Oriented Architecture (SOA)

software

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Software Engineering Diagram
    • Software Distribution Diagram
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.2 Software Services and Middleware Checklist
• A. Glossary of Supplementary Definitions
  • A.1 Application Software

Software Distribution diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Software Distribution Diagram

Software Engineering diagram

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Software Engineering Diagram

solution

• 3. Definitions
  • 3.69 Solution Architecture
  • 3.70 Solution Building Block (SBB)
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Solution Concept Diagram
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.19 Solution Building Blocks
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.4 Solution Building Blocks

Solution Architect

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.2 Characterization in Terms of the Enterprise Continuum

Solution Architecture

• 3. Definitions
  • 3.69 Solution Architecture

solution building block

• 3. Definitions
  • 3.70 Solution Building Block (SBB)
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.4 Solution Building Blocks

Solution Concept diagram

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Solution Concept Diagram

solutions

• 3. Definitions
  • 3.71 Solutions Continuum
• 12. Phase E: Opportunities & Solutions
• 14. Phase G: Implementation Governance
  • 14.3 Steps
    • 14.3.3 Guide Development of Solutions Deployment
• 24. Migration Planning Techniques
  • 24.2 Consolidated Gaps, Solutions, & Dependencies Matrix
• 25. Interoperability Requirements
  • 25.6 Reconciling Interoperability Requirements with Potential Solutions
• 31. Architectural Artifacts
  • 31.6.7 Phase E: Opportunities and Solutions
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum
      • Foundation Solutions
      • Common Systems Solutions
      • Industry Solutions
      • Organization-Specific Solutions

Solutions Continuum

• 2. Core Concepts
  • 2.6 Enterprise Continuum
• 3. Definitions
  • 3.71 Solutions Continuum
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.4 Solution Building Blocks
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.2 Solutions Continuum

Solutions Landscape

• 2. Core Concepts
  • 2.7 Architecture Repository
• 37. Architecture Repository
  • 37.1 Overview
  • 37.7 Solutions Landscape

some

• 22. Architecture Patterns
  • 22.2 Some Pattern Resources

specific

• 46. Architecture Skills Framework
  • 46.3 Goals/Rationale
    • 46.3.2 Specific Benefits

specifically

• 1. Introduction
  • 1.3 Executive Overview
    • What specifically would prompt the development of an Enterprise Architecture?

specification

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.6 Architecture Requirements Specification
• 33. Building Blocks
  • 33.2 Introduction to Building Blocks
    • 33.2.3 Architecture Building Blocks
      • 33.2.3.2 Specification Content
    • 33.2.4 Solution Building Blocks
      • 33.2.4.2 Specification Content
  • 33.3 Building Blocks and the ADM
    • 33.3.2 Building Block Specification Process in the ADM

SPEM

• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core and Extension Content

stages

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Stages Catalog

stakeholder

• 3. Definitions
  • 3.33 Communications and Stakeholder Management
  • 3.72 Stakeholder
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.7 Conduct Formal Stakeholder Review
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.7 Conduct Formal Stakeholder Review
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.7 Conduct Formal Stakeholder Review
• 21. Stakeholder Management
  • 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

stakeholder management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• 3. Definitions
  • 3.33 Communications and Stakeholder Management
• 21. Stakeholder Management

stakeholder management, process steps

• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process

Stakeholder Map matrix

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Stakeholder Map Matrix

stakeholders

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.2 Identify Stakeholders, Concerns, and Business Requirements
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.1 Identify Stakeholders

standard

• 1. Introduction
  • 1.3 Executive Overview
    • 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.2 How Much Does the TOGAF Standard Cost?

standardization

• 38. Tools for Architecture Development
  • 38.2 Issues in Tool Standardization

standards

• 3. Definitions
  • 3.73 Standards Information Base (SIB)
• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Technology Standards Catalog
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.3 Standards Lifecycle
    • 37.4.4 Standards Classification within the Standards Information Base

standards, classification

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

Standards Information Base

• 2. Core Concepts
  • 2.7 Architecture Repository
• 3. Definitions
  • 3.73 Standards Information Base (SIB)
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

standards, lifecycle

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.3 Standards Lifecycle

standards, types of

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.2 Types of Standard

state

• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
• 24. Migration Planning Techniques
  • 24.4 Transition Architecture State Evolution Table

statement

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.20 Statement of Architecture Work
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.1 Statement of Architecture Work

Statement of Architecture Work

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.20 Statement of Architecture Work
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.1 Statement of Architecture Work

steps

• 5. Preliminary Phase
  • 5.3 Steps
• 6. Phase A: Architecture Vision
  • 6.3 Steps
• 7. Phase B: Business Architecture
  • 7.3 Steps
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
• 11. Phase D: Technology Architecture
  • 11.3 Steps
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
• 13. Phase F: Migration Planning
  • 13.3 Steps
• 14. Phase G: Implementation Governance
  • 14.3 Steps
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
• 16. ADM Architecture Requirements Management
  • 16.3 Steps
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
• 23. Gap Analysis
  • 23.2 Suggested Steps
• 42. Architecture Compliance
  • 42.4 Architecture Compliance Review Process
    • 42.4.3 Steps

steward

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 13: Data Trustee

strategic

• 3. Definitions
  • 3.74 Strategic Architecture

Strategic Architecture

• 3. Definitions
  • 3.74 Strategic Architecture
• 19. Applying the ADM Across the Architecture Landscape
  • 19.2 Architecture Landscape
• 37. Architecture Repository
  • 37.2 Architecture Landscape

Strategic Architecture Requirements

• 37. Architecture Repository
  • 37.6 The Architecture Requirements Repository
    • 37.6.2 Contents of the Architecture Requirements Repository

strategy

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.8 Formulate Implementation and Migration Strategy
• 41. Architecture Board
  • 41.4 Operation of the Architecture Board
    • 41.4.3 Agenda
      • Architecture Strategy and Direction Documentation
• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.2 Elements of an Effective Architecture Governance Strategy

Strategy/Capability

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Strategy/Capability Matrix

Strategy/Capability matrix

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Strategy/Capability Matrix

stream

• 3. Definitions
  • 3.81 Value Stream
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Value Stream Map
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Catalog
    • Value Stream Stages Catalog
    • Value Stream Map

Stream/Capability

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Value Stream/Capability Matrix

streams

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.4 Applying Value Streams

structure

• 1. Introduction
  • 1.1 Structure of this Document
  • 1.2 Structure of the TOGAF Library
• 4. Introduction to Part II
  • 4.2 Architecture Development Cycle
    • 4.2.2 Basic Structure
• 29. Introduction to Part IV
  • 29.4 Structure of Part IV
• 34. Introduction to Part V
  • 34.2 Structure of Part V
• 39. Introduction to Part VI
  • 39.2 Structure of Part VI
• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board
    • 41.3.3 Board Structure
• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
    • 44.2.2 Architecture Governance Framework - Organizational Structure

structured analysis

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

style

• 3. Definitions
  • 3.6 Architectural Style
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles

success

• 44. Architecture Governance
  • 44.3 Architecture Governance in Practice
    • 44.3.1 Architecture Governance - Key Success Factors

successful

• A. Glossary of Supplementary Definitions
  • A.35 Managing Successful Programs (MSP)

suggested

• 23. Gap Analysis
  • 23.2 Suggested Steps

summary

• 4. Introduction to Part II
  • 4.7 Summary
• 27. Risk Management
  • 27.8 Summary
• 28. Capability-Based Planning
  • 28.5 Summary

supplementary

• A. Glossary of Supplementary Definitions

supplier

• A. Glossary of Supplementary Definitions
  • A.60 Supplier Management

supplier management

• 2. Core Concepts
  • 2.9 Establishing the Architecture Capability as an Operational Entity
• A. Glossary of Supplementary Definitions
  • A.60 Supplier Management

support

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.2 Confirm Governance and Support Frameworks

supporting

• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.3 ADM and Supporting Guidelines and Techniques

SW-CMM

• 45. Architecture Maturity Models
  • 45.4 Capability Maturity Models Integration (CMMI)
    • 45.4.1 Introduction

system

• 3. Definitions
  • 3.45 Information System Service
• 8. Phase C: Information Systems Architectures
• 9. Phase C: Information Systems Architectures - Data Architecture
• 10. Phase C: Information Systems Architectures - Application Architecture
• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Common Systems Architectures
    • 35.4.2 Solutions Continuum
      • Common Systems Solutions
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.1 Hardware and Operating System Checklist
    • 42.5.6 System Management Checklist
    • 42.5.7 System Engineering/Overall Architecture Checklists
    • 42.5.8 System Engineering/Methods & Tools Checklist
• A. Glossary of Supplementary Definitions
  • A.3 Business System
  • A.15 Database Management System
  • A.18 Enterprise Resource Planning (ERP) System
  • A.25 Information System (IS)
  • A.39 Open System
  • A.61 System

table

• 24. Migration Planning Techniques
  • 24.3 Architecture Definition Increments Table
  • 24.4 Transition Architecture State Evolution Table

TAFIM

• 1. Introduction

tailor

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
• 21. Stakeholder Management
  • 21.3 Steps in the Stakeholder Management Process
    • 21.3.4 Tailor Engagement Deliverables

tailored

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.21 Tailored Architecture Framework

Tailored Architecture Framework

• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.21 Tailored Architecture Framework

tailoring

• 42. Architecture Compliance
  • 42.6 Architecture Compliance Review Guidelines
    • 42.6.1 Tailoring the Checklists

Take-On

• 44. Architecture Governance
  • 44.2 Architecture Governance Framework
    • 44.2.1 Architecture Governance Framework - Conceptual Structure
      • Policy Management and Take-On

target

• 3. Definitions
  • 3.75 Target Architecture
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.3 Develop Target Business Architecture Description
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.3 Develop Target Data Architecture Description
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.3 Develop Target Application Architecture Description
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.3 Develop Target Technology Architecture Description

Target Architecture

• 3. Definitions
  • 3.75 Target Architecture

Target Architecture Description

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.3 Time Period

target first

• 18. Applying Iteration to the ADM
  • 18.4 Approaches to Architecture Development

targets

• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.5 Develop Change Requirements to Meet Performance Targets

taxonomy

• 3. Definitions
  • 3.76 Taxonomy of Architecture Views

taxonomy of architecture views

• 3. Definitions
  • 3.76 Taxonomy of Architecture Views

team

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.3 Define and Establish Enterprise Architecture Team and Organization

technical

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles
      • Principle 20: Control Technical Diversity
• 46. Architecture Skills Framework
  • 46.5 Enterprise Architecture Role and Skill Definitions
    • 46.5.6 Technical IT Skills
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.3 Key Characteristics of an Enterprise Architect
      • 46.6.3.2 Extensive Technical Breadth, with Technical Depth in One or a Few Disciplines

technique

• 4. Introduction to Part II
  • 4.1 ADM Overview
    • 4.1.3 ADM and Supporting Guidelines and Techniques
• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques
• 17. Introduction to Part III
  • 17.2 Techniques for Architecture Development
• 24. Migration Planning Techniques
  • 24.5 Business Value Assessment Technique

technologies

• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.1 Emerging Technologies

technology

• 3. Definitions
  • 3.46 Information Technology (IT)
  • 3.77 Technology Architecture
  • 3.78 Technology Component
  • 3.79 Technology Service
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks
    • 11.3.2 Develop Baseline Technology Architecture Description
    • 11.3.3 Develop Target Technology Architecture Description
    • 11.3.8 Finalize the Technology Architecture

Technology Architecture

• 2. Core Concepts
  • 2.3 What Kind of Architecture Does the TOGAF Standard Deal With?
• 3. Definitions
  • 3.77 Technology Architecture
• 11. Phase D: Technology Architecture

technology building blocks

• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.2 Identify Required Catalogs of Technology Building Blocks

technology component

• 3. Definitions
  • 3.78 Technology Component
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

technology governance

• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise
    • 44.1.3 Technology Governance

Technology Portfolio catalog

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Technology Portfolio Catalog

technology principles, examples

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.4 Technology Principles

technology service

• 3. Definitions
  • 3.79 Technology Service
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Technology Standards

• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base

Technology Standards catalog

• 31. Architectural Artifacts
  • 31.6.6 Phase D: Technology Architecture
    • Technology Standards Catalog

template

• 21. Stakeholder Management
  • 21.4 Template Stakeholder Map

terminology

• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
• 42. Architecture Compliance
  • 42.2 Terminology: The Meaning of Architecture Compliance

terminology tailoring

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

terms

• 46. Architecture Skills Framework
  • 46.6 Generic Role and Skills of the Enterprise Architect
    • 46.6.2 Characterization in Terms of the Enterprise Continuum

this

• 1. Introduction
  • 1.1 Structure of this Document

through

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

time

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.3 Time Period
• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise
• A. Glossary of Supplementary Definitions
  • A.62 Time Period

time period

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.3 Time Period
• A. Glossary of Supplementary Definitions
  • A.62 Time Period

time period, enterprise

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture

timing

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• 42. Architecture Compliance
  • 42.3 Architecture Compliance Reviews
    • 42.3.2 Timing

TM Forum

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.7 Architecture Repository
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.5 Approach
    • 10.5.1 Architecture Repository
• 11. Phase D: Technology Architecture
  • 11.5 Approach
    • 11.5.2 Architecture Repository
• 37. Architecture Repository
  • 37.3 Reference Library
    • 37.3.1 Overview

TOGAF

• 1. Introduction
  • 1.2 Structure of the TOGAF Library
  • 1.3 Executive Overview
    • 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.2 How Much Does the TOGAF Standard Cost?

TOGAF ADM

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
• 32. Architecture Deliverables
• 35. Enterprise Continuum
  • 35.5 The Enterprise Continuum and the ADM

TOGAF Library

• 1. Introduction
  • 1.2 Structure of the TOGAF Library

TOGAF TRM

• 35. Enterprise Continuum
  • 35.4 Enterprise Continuum in Detail
    • 35.4.1 Architecture Continuum
      • Foundation Architecture

tool

• 5. Preliminary Phase
  • 5.3 Steps
    • 5.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.2 Deploy Monitoring Tools
• 16. ADM Architecture Requirements Management
  • 16.5 Approach
    • 16.5.3 Resources
      • 16.5.3.2 Requirements Tools
• 31. Architectural Artifacts
  • 31.3 Views, Tools, and Languages
  • 31.4 Architecture Views and Architecture Viewpoints
    • 31.4.3 Need for a Common Language and Interoperable Tools for Architecture Description
• 38. Tools for Architecture Development
  • 38.2 Issues in Tool Standardization

transaction

• A. Glossary of Supplementary Definitions
  • A.63 Transaction

transformation

• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.5 Assess Readiness for Business Transformation
    • 6.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.7 Confirm Readiness and Risk for Business Transformation
• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)

transformation readiness assessment

• 26. Business Transformation Readiness Assessment
  • 26.1 Introduction
    • 26.1.1 Business Transformation Enablement Program (BTEP)

transition

• 3. Definitions
  • 3.80 Transition Architecture
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.10 Identify Transition Architectures
• 24. Migration Planning Techniques
  • 24.4 Transition Architecture State Evolution Table

Transition Architecture

• 3. Definitions
  • 3.80 Transition Architecture

Transition Architecture Description

• 4. Introduction to Part II
  • 4.5 Scoping the Architecture
    • 4.5.3 Time Period

Transition Planning

• 18. Applying Iteration to the ADM
  • 18.2 Iteration Cycles

triggers

• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board
    • 41.3.1 Triggers

trustee

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 13: Data Trustee

types

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.6 Identify Types of Requirement to be Collected
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
      • 9.3.1.5 Identify Types of Requirement to be Collected
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
      • 10.3.1.5 Identify Types of Requirement to be Collected
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
      • 11.3.1.5 Identify Types of Requirement to be Collected
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.2 Types of Standard
• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.4 Hosting, Data Types, and Sharing

UML

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

under

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework
    • 45.3.3 Example: Enterprise Architecture Process Maturity Levels
      • Level 2: Under Development

understand

• 19. Applying the ADM Across the Architecture Landscape
  • 19.3 Organizing the Architecture Landscape to Understand the State of the Enterprise

up

• 41. Architecture Board
  • 41.3 Setting Up the Architecture Board

update

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document

US

• 45. Architecture Maturity Models
  • 45.3 US DoC ACMM Framework

US DoD

• 1. Introduction

use

• 1. Introduction
  • 1.3 Executive Overview
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
  • 1.4 Information on Using the TOGAF Standard
    • 1.4.1 Conditions of Use
• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.1 Business Principles
      • Principle 5: Common Use Applications

Use-Case

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Business Use-Case Diagram
  • 31.6.5 Phase C: Application Architecture
    • Application Use-Case Diagram
• A. Glossary of Supplementary Definitions
  • A.64 Use-Case

use-case analysis

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

use-case model

• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.6 Applying Modeling Techniques

user

• 31. Architectural Artifacts
  • 31.6.5 Phase C: Application Architecture
    • Application and User Location Diagram
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.3 Contract between Architecting Function and Business Users
• A. Glossary of Supplementary Definitions
  • A.17 End User
  • A.65 User

using

• 1. Introduction
  • 1.3 Executive Overview
    • Who would benefit from using the TOGAF standard?
  • 1.4 Information on Using the TOGAF Standard
• 2. Core Concepts
  • 2.10 Using the TOGAF Standard with Other Frameworks
• 17. Introduction to Part III
  • 17.3 Using the TOGAF Framework with Different Architectural Styles

v

• 34. Introduction to Part V
  • 34.2 Structure of Part V

validate

• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.6 Refine and Validate Dependencies

validation

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

value

• 3. Definitions
  • 3.81 Value Stream
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.9 Define the Target Architecture Value Propositions and KPIs
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.4 Applying Value Streams
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.2 Assign a Business Value to Each Work Package
• 15. Phase H: Architecture Change Management
  • 15.3 Steps
    • 15.3.1 Establish Value Realization Process
• 24. Migration Planning Techniques
  • 24.5 Business Value Assessment Technique
• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Value Chain Diagram
    • Value Stream Map
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Catalog
    • Value Stream Stages Catalog
    • Value Stream/Capability Matrix
    • Value Stream Map

Value Chain diagram

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Value Chain Diagram

values

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.4 Information Management Checklists
      • 42.5.4.1 Data Values

value stream

• 3. Definitions
  • 3.81 Value Stream
• 30. Content Metamodel
  • 30.2 Content Metamodel Vision and Concepts
    • 30.2.1 Core Content Metamodel Concepts
      • Core Metamodel Entities

Value Stream/Capability matrix

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Value Stream/Capability Matrix

Value Stream catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Catalog

Value Stream map

• 31. Architectural Artifacts
  • 31.6.2 Phase A: Architecture Vision
    • Value Stream Map
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Map

value stream mapping

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process

value streams

• 6. Phase A: Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision
• 7. Phase B: Business Architecture
  • 7.5 Approach
    • 7.5.4 Applying Value Streams

Value Stream Stages catalog

• 31. Architectural Artifacts
  • 31.6.3 Phase B: Business Architecture
    • Value Stream Stages Catalog

vehicle

• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

versus

• 15. Phase H: Architecture Change Management
  • 15.5 Approach
    • 15.5.3 Guidelines for Maintenance versus Architecture Redesign

VI

• 39. Introduction to Part VI
  • 39.2 Structure of Part VI

view

• 3. Definitions
  • 3.17 Architecture View
  • 3.82 View
• 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.2 Architecture View Creation Process

viewpoint

• 3. Definitions
  • 3.18 Architecture Viewpoint
  • 3.83 Viewpoint
  • 3.84 Viewpoint Library
• 31. Architectural Artifacts
  • 31.1 Basic Concepts
    • 31.1.1 Simple Example of an Architecture Viewpoint and Architecture View

viewpoint library

• 3. Definitions
  • 3.84 Viewpoint Library

viewpoints

• 7. Phase B: Business Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase C: Information Systems Architectures - Data Architecture
  • 9.3 Steps
    • 9.3.1 Select Reference Models, Viewpoints, and Tools
• 10. Phase C: Information Systems Architectures - Application Architecture
  • 10.3 Steps
    • 10.3.1 Select Reference Models, Viewpoints, and Tools
• 11. Phase D: Technology Architecture
  • 11.3 Steps
    • 11.3.1 Select Reference Models, Viewpoints, and Tools
• 31. Architectural Artifacts
  • 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

views

• 3. Definitions
  • 3.76 Taxonomy of Architecture Views
• 22. Architecture Patterns
  • 22.1 Introduction
    • 22.1.3 Terminology
      • 22.1.3.3 Patterns and Views
• 31. Architectural Artifacts
  • 31.2 Developing Architecture Views in the ADM
  • 31.3 Views, Tools, and Languages
  • 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

vision

• 3. Definitions
  • 3.19 Architecture Vision
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.8 Develop Architecture Vision
  • 6.5 Approach
    • 6.5.2 Creating the Architecture Vision

vocabulary

• 20. Architecture Principles
  • 20.6 Example Set of Architecture Principles
    • 20.6.2 Data Principles
      • Principle 14: Common Vocabulary and Data Definitions

what

• 1. Introduction
  • 1.3 Executive Overview
    • What is an enterprise?
    • What are the benefits of an Enterprise Architecture?
    • What specifically would prompt the development of an Enterprise Architecture?
    • What is an architecture framework?
• 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?

where

• 42. Architecture Compliance
  • 42.5 Architecture Compliance Review Checklists
    • 42.5.7 System Engineering/Overall Architecture Checklists
      • 42.5.7.6 COTS (where applicable)

who

• 1. Introduction
  • 1.3 Executive Overview
    • Who would benefit from using the TOGAF standard?

why

• 1. Introduction
  • 1.3 Executive Overview
    • Why is an Enterprise Architecture needed?
    • Why use the TOGAF standard as a framework for Enterprise Architecture?
  • 1.5 Why Join The Open Group?

within

• 18. Applying Iteration to the ADM
  • 18.5 Iteration Considerations
    • 18.5.2 Iteration within an ADM Cycle
• 36. Architecture Partitioning
  • 36.2 Applying Classification to Create Partitioned Architectures
    • 36.2.1 Activities within the Preliminary Phase
• 37. Architecture Repository
  • 37.4 Standards Information Base
    • 37.4.4 Standards Classification within the Standards Information Base
• 44. Architecture Governance
  • 44.1 Introduction
    • 44.1.1 Levels of Governance within the Enterprise

work

• 3. Definitions
  • 3.85 Work Package
• 5. Preliminary Phase
  • 5.5 Approach
    • 5.5.3 Requirements for Architecture Work
• 6. Phase A: Architecture Vision
  • 6.3 Steps
    • 6.3.11 Develop Statement of Architecture Work; Secure Approval
• 12. Phase E: Opportunities & Solutions
  • 12.3 Steps
    • 12.3.9 Identify and Group Major Work Packages
• 13. Phase F: Migration Planning
  • 13.3 Steps
    • 13.3.2 Assign a Business Value to Each Work Package
• 32. Architecture Deliverables
  • 32.2 Deliverable Descriptions
    • 32.2.17 Request for Architecture Work
    • 32.2.20 Statement of Architecture Work
• 43. Architecture Contracts
  • 43.2 Contents
    • 43.2.1 Statement of Architecture Work

work package

• 3. Definitions
  • 3.85 Work Package

would

• 1. Introduction
  • 1.3 Executive Overview
    • What specifically would prompt the development of an Enterprise Architecture?
    • Who would benefit from using the TOGAF standard?

your

• 35. Enterprise Continuum
  • 35.6 The Enterprise Continuum and Your Organization
    • 35.6.2 Your Enterprise

Zachman Framework

• 4. Introduction to Part II
  • 4.3 Adapting the ADM