INDEX

across

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.6 Resolve Impacts Across the Architecture Landscape
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.6 Resolve Impacts Across the Architecture Landscape
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.6 Resolve Impacts Across the Architecture Landscape
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions

activate

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.7 Activate the Process to Implement Change

activities

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities

activity model

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

adapting

• 1. Introduction
  • 1.3 Adapting the ADM

ADM

• 1. Introduction
• 1.1 ADM Overview
• 1.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 1.1.2 The ADM and the Foundation Architecture
• 1.1.3 ADM and Supporting Guidelines and Techniques

• 1.3 Adapting the ADM

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.5 Management Frameworks
• 12. Phase H: Architecture Change Management
  • 12.5 Approach
• 13. ADM Architecture Requirements Management

ADM guidelines and techniques

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.3 ADM and Supporting Guidelines and Techniques

ADM, Requirements Management

• 13. ADM Architecture Requirements Management

alternatives

• 1. Introduction
  • 1.6 Architecture Alternatives

amp

• 9. Phase E: Opportunities & Solutions
• 9.3 Steps
  • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan

analysis

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.4 Perform Gap Analysis
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.4 Perform Gap Analysis
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.4 Perform Gap Analysis
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.4 Provide Analysis for Architecture Change Management

any

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

application

• 7. Phase C: Information Systems Architectures — Application Architecture
• 7.3 Steps
  • 7.3.1 Select Reference Models, Viewpoints, and Tools
    • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
  • 7.3.2 Develop Baseline Application Architecture Description
  • 7.3.3 Develop Target Application Architecture Description
  • 7.3.8 Finalize the Application Architecture

Application Architecture

• 7. Phase C: Information Systems Architectures — Application Architecture

application building blocks

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks

applying

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.3 Applying Business Capabilities
    • 4.5.4 Applying Value Streams
    • 4.5.5 Applying the Organization Map
    • 4.5.6 Applying Information Maps
    • 4.5.7 Applying Modeling Techniques

approach

• 2. Preliminary Phase
  • 2.5 Approach
• 3. Phase A: Architecture Vision
  • 3.5 Approach
• 4. Phase B: Business Architecture
  • 4.5 Approach
• 5. Phase C: Information Systems Architectures
  • 5.2 Approach
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.5 Approach
• 8. Phase D: Technology Architecture
  • 8.5 Approach
• 9. Phase E: Opportunities & Solutions
  • 9.5 Approach
• 10. Phase F: Migration Planning
  • 10.5 Approach
• 11. Phase G: Implementation Governance
  • 11.5 Approach
• 12. Phase H: Architecture Change Management
  • 12.5 Approach
• 13. ADM Architecture Requirements Management
  • 13.5 Approach

approval

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.11 Develop Statement of Architecture Work; Secure Approval

architectural

• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.3 Architectural Inputs
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.3 Architectural Inputs
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.3 Architectural Inputs
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.3 Architectural Inputs
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
    • 7.2.3 Architectural Inputs
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.3 Architectural Inputs
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.3 Architectural Inputs
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.3 Architectural Inputs
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.3 Architectural Inputs
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.3 Architectural Inputs

architecture

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.1 The ADM, Enterprise Continuum, and Architecture Repository
    • 1.1.2 The ADM and the Foundation Architecture
  • 1.2 Architecture Development Cycle
  • 1.4 Architecture Governance
  • 1.5 Scoping the Architecture
  • 1.5.4 Architecture Domains
• 1.6 Architecture Alternatives
• 1.7 Architecture Integration

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization
    • 2.3.4 Identify and Establish Architecture Principles
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
  • 2.5 Approach
    • 2.5.3 Requirements for Architecture Work
• 3. Phase A: Architecture Vision
• 3.3 Steps
  • 3.3.1 Establish the Architecture Project
  • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
  • 3.3.8 Develop Architecture Vision
  • 3.3.9 Define the Target Architecture Value Propositions and KPIs
  • 3.3.11 Develop Statement of Architecture Work; Secure Approval
• 3.5 Approach
  • 3.5.2 Creating the Architecture Vision

• 4. Phase B: Business Architecture
• 4.3 Steps
  • 4.3.2 Develop Baseline Business Architecture Description
  • 4.3.3 Develop Target Business Architecture Description
  • 4.3.6 Resolve Impacts Across the Architecture Landscape
  • 4.3.8 Finalize the Business Architecture
  • 4.3.9 Create/Update the Architecture Definition Document
• 4.5 Approach
  • 4.5.8 Architecture Repository

• 6. Phase C: Information Systems Architectures — Data Architecture
• 6.3 Steps
  • 6.3.2 Develop Baseline Data Architecture Description
  • 6.3.3 Develop Target Data Architecture Description
  • 6.3.6 Resolve Impacts Across the Architecture Landscape
  • 6.3.8 Finalize the Data Architecture
  • 6.3.9 Create/Update the Architecture Definition Document
• 6.5 Approach
  • 6.5.2 Key Considerations for Data Architecture
  • 6.5.3 Architecture Repository

• 7. Phase C: Information Systems Architectures — Application Architecture
• 7.3 Steps
  • 7.3.2 Develop Baseline Application Architecture Description
  • 7.3.3 Develop Target Application Architecture Description
  • 7.3.6 Resolve Impacts Across the Architecture Landscape
  • 7.3.8 Finalize the Application Architecture
  • 7.3.9 Create/Update the Architecture Definition Document
• 7.5 Approach
  • 7.5.1 Architecture Repository

• 8. Phase D: Technology Architecture
• 8.3 Steps
  • 8.3.2 Develop Baseline Technology Architecture Description
  • 8.3.3 Develop Target Technology Architecture Description
  • 8.3.6 Resolve Impacts Across the Architecture Landscape
  • 8.3.8 Finalize the Technology Architecture
  • 8.3.9 Create/Update the Architecture Definition Document
• 8.5 Approach
  • 8.5.2 Architecture Repository

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.4 Perform Enterprise Architecture Compliance Reviews
• 12. Phase H: Architecture Change Management
• 12.3 Steps
  • 12.3.4 Provide Analysis for Architecture Change Management
• 12.5 Approach
  • 12.5.2 Enterprise Architecture Change Management Process
  • 12.5.3 Guidelines for Maintenance versus Architecture Redesign

• 13. ADM Architecture Requirements Management

Architecture Board

• 1. Introduction
  • 1.4 Architecture Governance

architecture change management

• 12. Phase H: Architecture Change Management

Architecture Development Method

• 1. Introduction

architecture domain

• 1. Introduction
  • 1.5 Scoping the Architecture
  • 1.5.4 Architecture Domains

Architecture Governance

• 1. Introduction
  • 1.4 Architecture Governance
• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.4 Principles
• 11. Phase G: Implementation Governance
  • 11.5 Approach

architecture integration

• 1. Introduction
  • 1.7 Architecture Integration

architecture models

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.1 Determine Overall Modeling Process

architecture partition

• 1. Introduction
  • 1.5 Scoping the Architecture

Architecture Principles

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.4 Principles

Architecture Report

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.9 Create/Update the Architecture Definition Document

Architecture Repository

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.8 Architecture Repository
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.3 Architecture Repository
• 8. Phase D: Technology Architecture
  • 8.5 Approach
    • 8.5.2 Architecture Repository

Architecture Vision

• 1. Introduction
  • 1.3 Adapting the ADM
• 3. Phase A: Architecture Vision

architecture, scoping

• 1. Introduction
  • 1.5 Scoping the Architecture

Architecture/Business

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

architectures

• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.10 Identify Transition Architectures

assess

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.5 Assess Readiness for Business Transformation

assessment

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

assign

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package

attributes

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.1 Determine/Confirm Key Corporate Change Attributes

audit information

• 1. Introduction
  • 1.4 Architecture Governance

Availability/Delivery

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

b

• 4. Phase B: Business Architecture
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

Balanced Scorecard technique

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques

baseline

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.2 Develop Baseline Business Architecture Description
  • 4.5 Approach
    • 4.5.2 Developing the Baseline Description
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.2 Develop Baseline Data Architecture Description
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.2 Develop Baseline Application Architecture Description
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.2 Develop Baseline Technology Architecture Description

Baseline Application Architecture Description

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.2 Develop Baseline Application Architecture Description

Baseline Data Architecture Description

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.2 Develop Baseline Data Architecture Description

Baseline Description

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.2 Developing the Baseline Description

Baseline Technology Architecture Description

• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.2 Develop Baseline Technology Architecture Description

basic

• 1. Introduction
  • 1.2 Architecture Development Cycle
    • 1.2.2 Basic Structure

be

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.5 Identify Types of Requirement to be Collected
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.5 Identify Types of Requirement to be Collected

blocks

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks

BPMN

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

breadth

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.1 Breadth

breadth, enterprise

• 1. Introduction
  • 1.5 Scoping the Architecture
  • 1.5.1 Breadth

building

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks

business

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.2 Identify Stakeholders, Concerns, and Business Requirements
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 3.3.5 Assess Readiness for Business Transformation
    • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 4. Phase B: Business Architecture
• 4.3 Steps
  • 4.3.1 Select Reference Models, Viewpoints, and Tools
    • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
  • 4.3.2 Develop Baseline Business Architecture Description
  • 4.3.3 Develop Target Business Architecture Description
  • 4.3.8 Finalize the Business Architecture
• 4.5 Approach
  • 4.5.3 Applying Business Capabilities

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.2 Determine Business Constraints for Implementation
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions
    • 9.3.7 Confirm Readiness and Risk for Business Transformation
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.5 Implement Business and IT Operations
• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.1 Business Scenarios

Business Architecture

• 4. Phase B: Business Architecture

business capabilities

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.2 Creating the Architecture Vision
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.3 Applying Business Capabilities

business capability mapping

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

business planning

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

business principles

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.4 Principles

business process model

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

Business Process Modeling Notation

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

business scenarios

• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.1 Business Scenarios

c

• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture

candidate

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.5 Define Candidate Roadmap Components
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.5 Define Candidate Roadmap Components
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.5 Define Candidate Roadmap Components

capabilities

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.4 Evaluate Capabilities
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.3 Applying Business Capabilities

catalog

• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks

catalog of application building blocks

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks

catalogs

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks

catalogs, building blocks

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks

Catalyst

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

change

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.1 Determine/Confirm Key Corporate Change Attributes
• 12. Phase H: Architecture Change Management
• 12.3 Steps
  • 12.3.4 Provide Analysis for Architecture Change Management
  • 12.3.5 Develop Change Requirements to Meet Performance Targets
  • 12.3.7 Activate the Process to Implement Change
• 12.5 Approach
  • 12.5.1 Drivers for Change
  • 12.5.2 Enterprise Architecture Change Management Process

change management

• 12. Phase H: Architecture Change Management

change management process

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

class model

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

close

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.6 Perform Post-Implementation Review and Close the Implementation

COBIT

• 1. Introduction
  • 1.4 Architecture Governance

collected

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.5 Identify Types of Requirement to be Collected
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.5 Identify Types of Requirement to be Collected

complete

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.6 Complete the Implementation and Migration Plan
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

compliance

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.4 Perform Enterprise Architecture Compliance Reviews

components

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.5 Define Candidate Roadmap Components
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.5 Define Candidate Roadmap Components
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.5 Define Candidate Roadmap Components

concerns

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.2 Identify Stakeholders, Concerns, and Business Requirements

conduct

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.7 Conduct Formal Stakeholder Review
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.7 Conduct Formal Stakeholder Review
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.7 Conduct Formal Stakeholder Review
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

confirm

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.2 Confirm Governance and Support Frameworks
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.7 Confirm Readiness and Risk for Business Transformation
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management

considerations

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture

consolidate

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
    • 9.3.5 Consolidate and Reconcile Interoperability Requirements

consolidated

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions

constraints

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.2 Determine Business Constraints for Implementation

content tailoring

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

context

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.2 Organizational Context

continuum

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.1 The ADM, Enterprise Continuum, and Architecture Repository

corporate

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.1 Determine/Confirm Key Corporate Change Attributes

Cost/Benefit

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

COTS

• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.2 Requirements Tools

create

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan

create architecture models

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.1 Determine Overall Modeling Process

Create/Update

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.9 Create/Update the Architecture Definition Document
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.9 Create/Update the Architecture Definition Document
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.9 Create/Update the Architecture Definition Document
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.9 Create/Update the Architecture Definition Document

creating

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.2 Creating the Architecture Vision

cycle

• 1. Introduction
  • 1.2 Architecture Development Cycle
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

d

• 8. Phase D: Technology Architecture
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

data

• 6. Phase C: Information Systems Architectures — Data Architecture
• 6.3 Steps
  • 6.3.1 Select Reference Models, Viewpoints, and Tools
    • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
  • 6.3.2 Develop Baseline Data Architecture Description
  • 6.3.3 Develop Target Data Architecture Description
  • 6.3.8 Finalize the Data Architecture
• 6.5 Approach
  • 6.5.1 Data Structure
  • 6.5.2 Key Considerations for Data Architecture
  • 6.5.2.1 Data Management
  • 6.5.2.2 Data Migration
  • 6.5.2.3 Data Governance

Data Architecture

• 6. Phase C: Information Systems Architectures — Data Architecture

data building blocks

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks

data entity

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.1 Data Structure

data governance

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.3 Data Governance

data management

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.1 Data Management

data migration

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.2 Data Migration

data structure

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.1 Data Structure

define

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.6 Define Scope
    • 3.3.9 Define the Target Architecture Value Propositions and KPIs
• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.5 Define Candidate Roadmap Components
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.5 Define Candidate Roadmap Components
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.5 Define Candidate Roadmap Components

definition

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.9 Create/Update the Architecture Definition Document
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.9 Create/Update the Architecture Definition Document
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.9 Create/Update the Architecture Definition Document
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.9 Create/Update the Architecture Definition Document
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document

dependencies

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.6 Refine and Validate Dependencies

deploy

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.2 Deploy Monitoring Tools

deployment

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management
    • 11.3.2 Identify Deployment Resources and Skills
    • 11.3.3 Guide Development of Solutions Deployment

depth

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.2 Depth

depth, enterprise

• 1. Introduction
  • 1.5 Scoping the Architecture
  • 1.5.2 Depth

determine

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.1 Determine Overall Modeling Process
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.1 Determine Overall Modeling Process
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.2 Determine Business Constraints for Implementation

Determine/Confirm

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.1 Determine/Confirm Key Corporate Change Attributes

develop

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.8 Develop Architecture Vision
    • 3.3.11 Develop Statement of Architecture Work; Secure Approval
• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.2 Develop Baseline Business Architecture Description
    • 4.3.3 Develop Target Business Architecture Description
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.2 Develop Baseline Data Architecture Description
    • 6.3.3 Develop Target Data Architecture Description
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.2 Develop Baseline Application Architecture Description
    • 7.3.3 Develop Target Application Architecture Description
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.2 Develop Baseline Technology Architecture Description
    • 8.3.3 Develop Target Technology Architecture Description
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.5 Develop Change Requirements to Meet Performance Targets

developing

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.2 Developing the Baseline Description

development

• 1. Introduction
  • 1.2 Architecture Development Cycle
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management
    • 11.3.3 Guide Development of Solutions Deployment
• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.2 Requirements Development

diagrams

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.4 Identify Required Diagrams
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.4 Identify Required Diagrams
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.4 Identify Required Diagrams
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.4 Identify Required Diagrams

document

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.9 Create/Update the Architecture Definition Document
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.9 Create/Update the Architecture Definition Document
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.9 Create/Update the Architecture Definition Document
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.9 Create/Update the Architecture Definition Document
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

domains

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.4 Architecture Domains

drivers

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.1 Drivers for Change

drivers for change

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.1 Drivers for Change

e

• 9. Phase E: Opportunities & Solutions

each

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package

EAP

• 5. Phase C: Information Systems Architectures
  • 5.2 Approach

elaborate

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints
    • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles

emerging

• 8. Phase D: Technology Architecture
  • 8.5 Approach
    • 8.5.1 Emerging Technologies

emerging technologies

• 8. Phase D: Technology Architecture
  • 8.5 Approach
    • 8.5.1 Emerging Technologies

enterprise

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.1 Reference Materials External to the Enterprise
  • 2.3 Steps
    • 2.3.1 Scope the Enterprise Organizations Impacted
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization
  • 2.5 Approach
    • 2.5.1 Enterprise
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.1 Reference Materials External to the Enterprise
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.1 Reference Materials External to the Enterprise
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.1 Reference Materials External to the Enterprise
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
  • 11.3 Steps
    • 11.3.4 Perform Enterprise Architecture Compliance Reviews
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

establish

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization
    • 2.3.4 Identify and Establish Architecture Principles
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.1 Establish the Architecture Project
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.1 Establish Value Realization Process

estimate

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

evaluate

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.4 Evaluate Capabilities

evaluation

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

external

• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.1 Reference Materials External to the Enterprise
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.1 Reference Materials External to the Enterprise
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.1 Reference Materials External to the Enterprise
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.1 Reference Materials External to the Enterprise
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise

f

• 10. Phase F: Migration Planning

finalize

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.8 Finalize the Business Architecture
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.8 Finalize the Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.8 Finalize the Application Architecture
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.8 Finalize the Technology Architecture

formal

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.7 Conduct Formal Stakeholder Review
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.7 Conduct Formal Stakeholder Review
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.7 Conduct Formal Stakeholder Review

formal stakeholder review

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.7 Conduct Formal Stakeholder Review
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.7 Conduct Formal Stakeholder Review
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.7 Conduct Formal Stakeholder Review

formulate

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.8 Formulate Implementation and Migration Strategy

foundation

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.2 The ADM and the Foundation Architecture

framework

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan

framework(s

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

frameworks

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.2 Confirm Governance and Support Frameworks
  • 2.5 Approach
    • 2.5.5 Management Frameworks
    • 2.5.6 Relating the Management Frameworks

functions

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions

g

• 11. Phase G: Implementation Governance

gap

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.4 Perform Gap Analysis
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.4 Perform Gap Analysis
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.4 Perform Gap Analysis
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

gap analysis

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.4 Perform Gap Analysis

general

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.1 General
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.1 General
• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.1 General

goals

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints

governance

• 1. Introduction
  • 1.4 Architecture Governance
• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.2 Confirm Governance and Support Frameworks
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.3 Data Governance
• 11. Phase G: Implementation Governance
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.6 Manage Governance Process

group

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.9 Identify and Group Major Work Packages

guide

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.3 Guide Development of Solutions Deployment

guidelines

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.3 ADM and Supporting Guidelines and Techniques
• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.3 Guidelines for Maintenance versus Architecture Redesign

h

• 12. Phase H: Architecture Change Management

ICAM

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

ICOM

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

IDEF

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

identify

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.4 Identify and Establish Architecture Principles
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.2 Identify Stakeholders, Concerns, and Business Requirements
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
      • 4.3.1.3 Identify Required Matrices
      • 4.3.1.4 Identify Required Diagrams
      • 4.3.1.5 Identify Types of Requirement to be Collected
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
      • 6.3.1.3 Identify Required Matrices
      • 6.3.1.4 Identify Required Diagrams
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
      • 7.3.1.3 Identify Required Matrices
      • 7.3.1.4 Identify Required Diagrams
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks
      • 8.3.1.3 Identify Required Matrices
      • 8.3.1.4 Identify Required Diagrams
      • 8.3.1.5 Identify Types of Requirement to be Collected
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.9 Identify and Group Major Work Packages
    • 9.3.10 Identify Transition Architectures
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.2 Identify Deployment Resources and Skills

if

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

impacted

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.1 Scope the Enterprise Organizations Impacted

impacts

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.6 Resolve Impacts Across the Architecture Landscape
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.6 Resolve Impacts Across the Architecture Landscape
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.6 Resolve Impacts Across the Architecture Landscape

implement

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.5 Implement Business and IT Operations
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.7 Activate the Process to Implement Change

implementation

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.2 Determine Business Constraints for Implementation
    • 9.3.8 Formulate Implementation and Migration Strategy
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 10.3.6 Complete the Implementation and Migration Plan
• 11. Phase G: Implementation Governance
• 11.3 Steps
  • 11.3.6 Perform Post-Implementation Review and Close the Implementation

implementation governance

• 11. Phase G: Implementation Governance

in

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
      • 2.3.6.1 Issues in Tools Standardization

including

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles

incremental change

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

Industry Architectures

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.8 Architecture Repository

information

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.6 Applying Information Maps
• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture

information mapping

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process
  • 4.5 Approach
    • 4.5.6 Applying Information Maps

Information Systems Architecture

• 5. Phase C: Information Systems Architectures

inputs

• 2. Preliminary Phase
  • 2.2 Inputs
  • 2.2.2 Non-Architectural Inputs
  • 2.2.3 Architectural Inputs

• 3. Phase A: Architecture Vision
  • 3.2 Inputs
  • 3.2.2 Non-Architectural Inputs
  • 3.2.3 Architectural Inputs

• 4. Phase B: Business Architecture
  • 4.2 Inputs
  • 4.2.2 Non-Architectural Inputs
  • 4.2.3 Architectural Inputs

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
  • 6.2.2 Non-Architectural Inputs
  • 6.2.3 Architectural Inputs

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
  • 7.2.2 Non-Architectural Inputs
  • 7.2.3 Architectural Inputs

• 8. Phase D: Technology Architecture
  • 8.2 Inputs
  • 8.2.2 Non-Architectural Inputs
  • 8.2.3 Architectural Inputs

• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
  • 9.2.2 Non-Architectural Inputs
  • 9.2.3 Architectural Inputs

• 10. Phase F: Migration Planning
  • 10.2 Inputs
  • 10.2.2 Non-Architectural Inputs
  • 10.2.3 Architectural Inputs

• 11. Phase G: Implementation Governance
  • 11.2 Inputs
  • 11.2.2 Non-Architectural Inputs
  • 11.2.3 Architectural Inputs

• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
  • 12.2.2 Non-Architectural Inputs
  • 12.2.3 Architectural Inputs

• 13. ADM Architecture Requirements Management
  • 13.2 Inputs

integration

• 1. Introduction
  • 1.7 Architecture Integration

interactions

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan

interoperability

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.5 Consolidate and Reconcile Interoperability Requirements

issues

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
      • 2.3.6.1 Issues in Tools Standardization

IT

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.5 Implement Business and IT Operations

ITIL

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

key

• 1. Introduction
  • 1.2 Architecture Development Cycle
    • 1.2.1 Key Points
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.1 Determine/Confirm Key Corporate Change Attributes

KPIs

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.9 Define the Target Architecture Value Propositions and KPIs

landscape

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.6 Resolve Impacts Across the Architecture Landscape
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.6 Resolve Impacts Across the Architecture Landscape
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.6 Resolve Impacts Across the Architecture Landscape

learned

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

lessons

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.7 Complete the Architecture Development Cycle and Document Lessons Learned

lessons learned process

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.1 Drivers for Change

logical data component

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.1 Data Structure

logical data model

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

maintenance

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.3 Guidelines for Maintenance versus Architecture Redesign

major

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.9 Identify and Group Major Work Packages

manage

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.3 Manage Risks
    • 12.3.6 Manage Governance Process

management

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.5 Management Frameworks
    • 2.5.6 Relating the Management Frameworks
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.1 Data Management
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management
• 12. Phase H: Architecture Change Management
• 12.3 Steps
  • 12.3.4 Provide Analysis for Architecture Change Management
• 12.5 Approach
  • 12.5.2 Enterprise Architecture Change Management Process

• 13. ADM Architecture Requirements Management

management frameworks

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

map

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.5 Applying the Organization Map
    • 4.5.6 Applying Information Maps

materials

• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.1 Reference Materials External to the Enterprise
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.1 Reference Materials External to the Enterprise
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.1 Reference Materials External to the Enterprise
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
    • 7.2.1 Reference Materials External to the Enterprise
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.1 Reference Materials External to the Enterprise
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise

matrices

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.3 Identify Required Matrices
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.3 Identify Required Matrices
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.3 Identify Required Matrices
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.3 Identify Required Matrices

maturity

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

MDA

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools

mdash

• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture

meet

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.5 Develop Change Requirements to Meet Performance Targets

method

• 1. Introduction
  • 1.6 Architecture Alternatives
    • 1.6.1 Method

migration

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.2 Key Considerations for Data Architecture
      • 6.5.2.2 Data Migration
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.8 Formulate Implementation and Migration Strategy
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 10. Phase F: Migration Planning
• 10.3 Steps
  • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
  • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
  • 10.3.6 Complete the Implementation and Migration Plan

Migration Planning

• 10. Phase F: Migration Planning

mitigation

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities

Model-Driven Architecture

• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools

modeling

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.1 Determine Overall Modeling Process
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.1 Determine Overall Modeling Process

modeling process

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

modeling techniques

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

models

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools

monitoring

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.2 Deploy Monitoring Tools

NASCIO

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation

Non-Architectural

• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.2 Non-Architectural Inputs
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.2 Non-Architectural Inputs
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.2 Non-Architectural Inputs
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.2 Non-Architectural Inputs
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.2 Inputs
    • 7.2.2 Non-Architectural Inputs
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.2 Non-Architectural Inputs
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.2 Non-Architectural Inputs
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.2 Non-Architectural Inputs
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.2 Non-Architectural Inputs
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.2 Non-Architectural Inputs

objectives

• 2. Preliminary Phase
  • 2.1 Objectives
• 3. Phase A: Architecture Vision
  • 3.1 Objectives
• 4. Phase B: Business Architecture
  • 4.1 Objectives
• 5. Phase C: Information Systems Architectures
  • 5.1 Objectives
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.1 Objectives
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.1 Objectives
• 8. Phase D: Technology Architecture
  • 8.1 Objectives
• 9. Phase E: Opportunities & Solutions
  • 9.1 Objectives
• 10. Phase F: Migration Planning
  • 10.1 Objectives
• 11. Phase G: Implementation Governance
  • 11.1 Objectives
• 12. Phase H: Architecture Change Management
  • 12.1 Objectives
• 13. ADM Architecture Requirements Management
  • 13.1 Objectives

OMG

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools

operations

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.5 Implement Business and IT Operations

operations management

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

opportunities

• 9. Phase E: Opportunities & Solutions

Opportunities & Solutions

• 9. Phase E: Opportunities & Solutions

organization

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.5 Applying the Organization Map

organization map

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.2 Creating the Architecture Vision
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.5 Applying the Organization Map

organization mapping

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

organizational

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.2 Organizational Context

organizations

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.1 Scope the Enterprise Organizations Impacted

outputs

• 2. Preliminary Phase
  • 2.4 Outputs
• 3. Phase A: Architecture Vision
  • 3.4 Outputs
• 4. Phase B: Business Architecture
  • 4.4 Outputs
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.4 Outputs
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.4 Outputs
• 8. Phase D: Technology Architecture
  • 8.4 Outputs
• 9. Phase E: Opportunities & Solutions
  • 9.4 Outputs
• 10. Phase F: Migration Planning
  • 10.4 Outputs
• 11. Phase G: Implementation Governance
  • 11.4 Outputs
• 12. Phase H: Architecture Change Management
  • 12.4 Outputs
• 13. ADM Architecture Requirements Management
  • 13.4 Outputs

overall

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.1 Determine Overall Modeling Process
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.1 Determine Overall Modeling Process

overview

• 1. Introduction
  • 1.1 ADM Overview

package

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.9 Identify and Group Major Work Packages
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package

perform

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.4 Perform Gap Analysis
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.4 Perform Gap Analysis
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.4 Perform Gap Analysis
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.4 Perform Gap Analysis
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.4 Perform Enterprise Architecture Compliance Reviews
    • 11.3.6 Perform Post-Implementation Review and Close the Implementation

performance

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.5 Develop Change Requirements to Meet Performance Targets

period

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.3 Time Period

phase

• 2. Preliminary Phase
• 3. Phase A: Architecture Vision
• 4. Phase B: Business Architecture
• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture
• 8. Phase D: Technology Architecture
• 9. Phase E: Opportunities & Solutions
• 10. Phase F: Migration Planning
• 11. Phase G: Implementation Governance
• 12. Phase H: Architecture Change Management

Phase A

• 3. Phase A: Architecture Vision

Phase B

• 4. Phase B: Business Architecture

Phase C

• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture

Phase D

• 8. Phase D: Technology Architecture

Phase E

• 9. Phase E: Opportunities & Solutions

Phase F

• 10. Phase F: Migration Planning

Phase G

• 11. Phase G: Implementation Governance

Phase H

• 12. Phase H: Architecture Change Management

phases

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

physical data component

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.1 Data Structure

plan

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.1 Confirm Management Framework Interactions for the Implementation and Migration Plan
    • 10.3.6 Complete the Implementation and Migration Plan

planning

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.7 Planning for Enterprise Architecture/Business Change Maturity Evaluation
• 10. Phase F: Migration Planning

points

• 1. Introduction
  • 1.2 Architecture Development Cycle
    • 1.2.1 Key Points

portfolio management

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

Post-Implementation

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.6 Perform Post-Implementation Review and Close the Implementation

preliminary

• 2. Preliminary Phase

Preliminary Phase

• 2. Preliminary Phase

PRINCE2

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

principles

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.4 Identify and Establish Architecture Principles
  • 2.5 Approach
    • 2.5.4 Principles
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.7 Confirm and Elaborate Architecture Principles, including Business Principles

priorities

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management

prioritize

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

process

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.1 Determine Overall Modeling Process
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.1 Determine Overall Modeling Process
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.1 Determine Overall Modeling Process
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.1 Establish Value Realization Process
    • 12.3.6 Manage Governance Process
    • 12.3.7 Activate the Process to Implement Change
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

process modeling

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

process status

• 1. Introduction
  • 1.4 Architecture Governance

process tailoring

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

Product Line Architecture

• 1. Introduction
  • 1.3 Adapting the ADM

project

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.1 Establish the Architecture Project
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

project management

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

projects

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

propositions

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.9 Define the Target Architecture Value Propositions and KPIs

provide

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.4 Provide Analysis for Architecture Change Management

re-architecting change

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

readiness

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.5 Assess Readiness for Business Transformation
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.7 Confirm Readiness and Risk for Business Transformation

realization

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.1 Establish Value Realization Process

reconcile

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.5 Consolidate and Reconcile Interoperability Requirements

redesign

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.3 Guidelines for Maintenance versus Architecture Redesign

reference

• 2. Preliminary Phase
  • 2.2 Inputs
    • 2.2.1 Reference Materials External to the Enterprise
• 3. Phase A: Architecture Vision
  • 3.2 Inputs
    • 3.2.1 Reference Materials External to the Enterprise
• 4. Phase B: Business Architecture
  • 4.2 Inputs
    • 4.2.1 Reference Materials External to the Enterprise
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.2 Inputs
    • 6.2.1 Reference Materials External to the Enterprise
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application 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
• 8. Phase D: Technology Architecture
  • 8.2 Inputs
    • 8.2.1 Reference Materials External to the Enterprise
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
• 9. Phase E: Opportunities & Solutions
  • 9.2 Inputs
    • 9.2.1 Reference Materials External to the Enterprise
• 10. Phase F: Migration Planning
  • 10.2 Inputs
    • 10.2.1 Reference Materials External to the Enterprise
• 11. Phase G: Implementation Governance
  • 11.2 Inputs
    • 11.2.1 Reference Materials External to the Enterprise
• 12. Phase H: Architecture Change Management
  • 12.2 Inputs
    • 12.2.1 Reference Materials External to the Enterprise

reference data

• 1. Introduction
  • 1.4 Architecture Governance

reference models

• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools

refine

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.6 Refine and Validate Dependencies

related

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions

relating

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.6 Relating the Management Frameworks

repository

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.1 The ADM, Enterprise Continuum, and Architecture Repository
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.8 Architecture Repository
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.3 Architecture Repository
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.5 Approach
    • 7.5.1 Architecture Repository
• 8. Phase D: Technology Architecture
  • 8.5 Approach
    • 8.5.2 Architecture Repository

Request for Architecture Work

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.1 General

required

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.2 Identify Required Catalogs of Business Building Blocks
      • 4.3.1.3 Identify Required Matrices
      • 4.3.1.4 Identify Required Diagrams
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.2 Identify Required Catalogs of Data Building Blocks
      • 6.3.1.3 Identify Required Matrices
      • 6.3.1.4 Identify Required Diagrams
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.2 Identify Required Catalogs of Application Building Blocks
      • 7.3.1.3 Identify Required Matrices
      • 7.3.1.4 Identify Required Diagrams
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks
      • 8.3.1.3 Identify Required Matrices
      • 8.3.1.4 Identify Required Diagrams

requirement

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.5 Identify Types of Requirement to be Collected
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.5 Identify Types of Requirement to be Collected

Requirement for Architecture Work

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.3 Requirements for Architecture Work

requirements

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.3 Requirements for Architecture Work
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.2 Identify Stakeholders, Concerns, and Business Requirements
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions
    • 9.3.5 Consolidate and Reconcile Interoperability Requirements
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.5 Develop Change Requirements to Meet Performance Targets
• 13. ADM Architecture Requirements Management
• 13.5 Approach
  • 13.5.2 Requirements Development
  • 13.5.3 Resources
    • 13.5.3.2 Requirements Tools

requirements tools

• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.2 Requirements Tools

resolve

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.6 Resolve Impacts Across the Architecture Landscape
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.6 Resolve Impacts Across the Architecture Landscape
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.6 Resolve Impacts Across the Architecture Landscape
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.6 Resolve Impacts Across the Architecture Landscape

resource

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.2 Identify Deployment Resources and Skills
• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources

results

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D

review

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.7 Conduct Formal Stakeholder Review
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.7 Conduct Formal Stakeholder Review
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.7 Conduct Formal Stakeholder Review
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.3 Review and Consolidate Gap Analysis Results from Phases B to D
    • 9.3.4 Review Consolidated Requirements Across Related Business Functions
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.4 Perform Enterprise Architecture Compliance Reviews
    • 11.3.6 Perform Post-Implementation Review and Close the Implementation

risk

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.7 Confirm Readiness and Risk for Business Transformation
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.3 Manage Risks

roadmap

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.5 Define Candidate Roadmap Components
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.5 Define Candidate Roadmap Components
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.5 Define Candidate Roadmap Components
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.11 Create the Architecture Roadmap & Implementation and Migration Plan
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document

roadmap components

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.5 Define Candidate Roadmap Components
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.5 Define Candidate Roadmap Components
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.5 Define Candidate Roadmap Components

scenarios

• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.1 Business Scenarios

scope

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.1 Scope the Enterprise Organizations Impacted
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.6 Define Scope
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.1 Confirm Scope and Priorities for Deployment with Development Management

scoping

• 1. Introduction
  • 1.5 Scoping the Architecture

scoping the architecture

• 1. Introduction
  • 1.5 Scoping the Architecture

secure

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.11 Develop Statement of Architecture Work; Secure Approval

select

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
    • 8.3.1.6 Select Services

selected

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

services

• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.6 Select Services

simplification change

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.2 Enterprise Architecture Change Management Process

skills

• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.2 Identify Deployment Resources and Skills

SOA

• 1. Introduction
  • 1.7 Architecture Integration

solutions

• 9. Phase E: Opportunities & Solutions
• 11. Phase G: Implementation Governance
  • 11.3 Steps
    • 11.3.3 Guide Development of Solutions Deployment

stakeholder

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.2 Identify Stakeholders, Concerns, and Business Requirements
• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.7 Conduct Formal Stakeholder Review
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.7 Conduct Formal Stakeholder Review
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.7 Conduct Formal Stakeholder Review
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.7 Conduct Formal Stakeholder Review

standardization

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
      • 2.3.6.1 Issues in Tools Standardization

statement

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.11 Develop Statement of Architecture Work; Secure Approval

Statement of Architecture Work

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.2 Creating the Architecture Vision

steps

• 2. Preliminary Phase
  • 2.3 Steps
• 3. Phase A: Architecture Vision
  • 3.3 Steps
• 4. Phase B: Business Architecture
  • 4.3 Steps
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
• 8. Phase D: Technology Architecture
  • 8.3 Steps
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
• 10. Phase F: Migration Planning
  • 10.3 Steps
• 11. Phase G: Implementation Governance
  • 11.3 Steps
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
• 13. ADM Architecture Requirements Management
  • 13.3 Steps

strategy

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.8 Formulate Implementation and Migration Strategy

streams

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.4 Applying Value Streams

structure

• 1. Introduction
  • 1.2 Architecture Development Cycle
    • 1.2.2 Basic Structure
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.5 Approach
    • 6.5.1 Data Structure

structured analysis

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

summary

• 1. Introduction
  • 1.8 Summary

support

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.2 Confirm Governance and Support Frameworks

supporting

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.3 ADM and Supporting Guidelines and Techniques

systems

• 5. Phase C: Information Systems Architectures
• 6. Phase C: Information Systems Architectures — Data Architecture
• 7. Phase C: Information Systems Architectures — Application Architecture

tailor

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

target

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.9 Define the Target Architecture Value Propositions and KPIs
• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.3 Develop Target Business Architecture Description
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.3 Develop Target Data Architecture Description
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.3 Develop Target Application Architecture Description
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.3 Develop Target Technology Architecture Description

Target Architecture Description

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.3 Time Period

targets

• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.5 Develop Change Requirements to Meet Performance Targets

team

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.3 Define and Establish Enterprise Architecture Team and Organization

techniques

• 1. Introduction
  • 1.1 ADM Overview
    • 1.1.3 ADM and Supporting Guidelines and Techniques
• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

technologies

• 8. Phase D: Technology Architecture
  • 8.5 Approach
    • 8.5.1 Emerging Technologies

technology

• 8. Phase D: Technology Architecture
• 8.3 Steps
  • 8.3.1 Select Reference Models, Viewpoints, and Tools
    • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks
  • 8.3.2 Develop Baseline Technology Architecture Description
  • 8.3.3 Develop Target Technology Architecture Description
  • 8.3.8 Finalize the Technology Architecture

Technology Architecture

• 8. Phase D: Technology Architecture

technology building blocks

• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.2 Identify Required Catalogs of Technology Building Blocks

terminology tailoring

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

through

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

time

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.3 Time Period

time period

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.3 Time Period

time period, enterprise

• 1. Introduction
  • 1.5 Scoping the Architecture

timings

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

TOGAF

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.5 Tailor the TOGAF Framework and, if any, Other Selected Architecture Framework(s)

TOGAF ADM

• 12. Phase H: Architecture Change Management
  • 12.5 Approach

tools

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
    • 2.3.6.1 Issues in Tools Standardization

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.2 Deploy Monitoring Tools
• 13. ADM Architecture Requirements Management
  • 13.5 Approach
    • 13.5.3 Resources
      • 13.5.3.2 Requirements Tools

tools standardization

• 2. Preliminary Phase
  • 2.3 Steps
    • 2.3.6 Develop a Strategy and Implementation Plan for Tools and Techniques
      • 2.3.6.1 Issues in Tools Standardization

transformation

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.5 Assess Readiness for Business Transformation
    • 3.3.10 Identify the Business Transformation Risks and Mitigation Activities
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.7 Confirm Readiness and Risk for Business Transformation

transition

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.10 Identify Transition Architectures

Transition Architecture Description

• 1. Introduction
  • 1.5 Scoping the Architecture
    • 1.5.3 Time Period

types

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.5 Identify Types of Requirement to be Collected
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
      • 6.3.1.5 Identify Types of Requirement to be Collected
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
      • 7.3.1.5 Identify Types of Requirement to be Collected
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools
      • 8.3.1.5 Identify Types of Requirement to be Collected

UML

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

update

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.5 Confirm Architecture Roadmap and Update Architecture Definition Document

use-case analysis

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

use-case model

• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.7 Applying Modeling Techniques

validate

• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.6 Refine and Validate Dependencies

validation

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.4 Prioritize the Migration Projects through the Conduct of a Cost/Benefit Assessment and Risk Validation

value

• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.9 Define the Target Architecture Value Propositions and KPIs
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.4 Applying Value Streams
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package
• 12. Phase H: Architecture Change Management
  • 12.3 Steps
    • 12.3.1 Establish Value Realization Process

value stream mapping

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
      • 4.3.1.1 Determine Overall Modeling Process

value streams

• 3. Phase A: Architecture Vision
  • 3.5 Approach
    • 3.5.2 Creating the Architecture Vision
• 4. Phase B: Business Architecture
  • 4.5 Approach
    • 4.5.4 Applying Value Streams

vehicle

• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.3 Estimate Resource Requirements, Project Timings, and Availability/Delivery Vehicle

versus

• 12. Phase H: Architecture Change Management
  • 12.5 Approach
    • 12.5.3 Guidelines for Maintenance versus Architecture Redesign

viewpoints

• 4. Phase B: Business Architecture
  • 4.3 Steps
    • 4.3.1 Select Reference Models, Viewpoints, and Tools
• 6. Phase C: Information Systems Architectures — Data Architecture
  • 6.3 Steps
    • 6.3.1 Select Reference Models, Viewpoints, and Tools
• 7. Phase C: Information Systems Architectures — Application Architecture
  • 7.3 Steps
    • 7.3.1 Select Reference Models, Viewpoints, and Tools
• 8. Phase D: Technology Architecture
  • 8.3 Steps
    • 8.3.1 Select Reference Models, Viewpoints, and Tools

vision

• 3. Phase A: Architecture Vision
• 3.3 Steps
  • 3.3.8 Develop Architecture Vision
• 3.5 Approach
  • 3.5.2 Creating the Architecture Vision

work

• 2. Preliminary Phase
  • 2.5 Approach
    • 2.5.3 Requirements for Architecture Work
• 3. Phase A: Architecture Vision
  • 3.3 Steps
    • 3.3.11 Develop Statement of Architecture Work; Secure Approval
• 9. Phase E: Opportunities & Solutions
  • 9.3 Steps
    • 9.3.9 Identify and Group Major Work Packages
• 10. Phase F: Migration Planning
  • 10.3 Steps
    • 10.3.2 Assign a Business Value to Each Work Package

Zachman Framework

• 1. Introduction
  • 1.3 Adapting the ADM

return to top of page