TOGAF Certification Series 6: TOGAF® 9 Certified

 

 

Chapter 2 Preliminary Phase

  • The objectives of the Preliminary Phase are to:
    • Determine the Architecture Capability desired by the organization:
      • Review the organizational context for conducting enterprise architecture
      • Identify and scope the elements of the enterprise organizations affected by the Architecture Capability
      • Identify the established frameworks, methods, and processes that intersect with the Architecture Capability
      • Establish a Capability Maturity target
    • Establish the Architecture Capability:
      • Define and establish the Organizational Model for Enterprise Architecture
      • Define and establish the detailed process and resources for architecture governance
      • Select and implement tools that support the Architecture Capability
      • Define the architecture principles
  • An Architecture Framework is a tool for assisting in the acceptance, production, use, and maintenance of architectures

 

Chapter 3 Phase A: Architecture Vision

  • The objectives of Phase A: Architecture Vision are to:
    • Develop a high-level aspirational vision of the capabilities and business value to be delivered as a result of the proposed enterprise architecture
    • Obtain approval for a Statement of Architecture Work that defines a program of works to develop and deploy the architecture outlined in the Architecture Vision
  • Phase A consists of the following steps:
    • 1. Establish the architecture project
    • 2. Identify stakeholders, concerns, and business requirements
    • 3. Confirm and elaborate business goals, business drivers, and constraints
    • 4. Evaluate business capabilities
    • 5. Assess readiness for business transformation
    • 6. Define scope
    • 7. Confirm and elaborate architecture principles, including business principles
    • 8. Develop Architecture Vision
    • 9. Define the Target Architecture value propositions and KPIs
    • 10. Identify the business transformation risks and mitigation activities
    • 11. Develop Statement of Architecture Work; secure approval

  • The outputs of this phase are:
    • Statement of Architecture Work
    • Refined statements of business principles, business goals, and business drivers
    • Architecture principles
    • Capability assessment
    • Tailored Architecture Framework
    • Architecture Vision, including:
      • Problem description
      • Objective of the Statement of Architecture Work
      • Summary views
      • Business scenario (optional)
      • Refined key high-level stakeholder requirements
    • Draft Architecture Definition Document (see Section 4.5.1), including (when in scope):
      • Baseline Business Architecture (high-level)
      • Baseline Data Architecture (high-level)
      • Baseline Application Architecture (high-level)
      • Baseline Technology Architecture (high-level)
      • Target Business Architecture (high-level)
      • Target Data Architecture (high-level)
      • Target Application Architecture (high-level)
      • Target Technology Architecture (high-level)
    • Communications Plan
    • Additional content populating the Architecture Repository

Chapter 4 Phase B: Business Architecture

  • The objectives of Phase B: Business Architecture are to:
    • Develop the Target Business Architecture that describes how the enterprise needs to operate to achieve the business goals, and respond to the strategic drivers set out in the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns
    • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Business Architectures
  • Phase B consists of the following steps:
    • 1. Select reference models, viewpoints, and tools
    • 2. Develop Baseline Business Architecture Description
    • 3. Develop Target Business Architecture Description
    • 4. Perform Gap Analysis
    • 5. Define candidate roadmap components
    • 6. Resolve impacts across the Architecture Landscape
    • 7. Conduct formal stakeholder review
    • 8. Finalize the Business Architecture
    • 9. Create the Architecture Definition Document

 

Chapter 5 Phase C: Information Systems Architectures

  • The objectives of Phase C: Information Systems Architectures are to:
    • Develop the Target Information Systems (Data and Application) Architectures, describing how the enterprise’s Information Systems Architecture will enable the Business Architecture and the Architecture Vision, in a way that addresses the Request for Architecture Work and stakeholder concerns
    • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Information Systems (Data and Application) Architectures

 

Chapter 6 Phase C: Data Architecture

  • The objectives of the Data Architecture part of Phase C are to:
    • Develop the Target Data Architecture that enables the Business Architecture and the Architecture Vision, while addressing the Request for Architecture Work and stakeholder concerns
    • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Data Architectures
  • Data Architecture consists of the following steps:
    • 1. Select reference models, viewpoints, and tools
    • 2. Develop Baseline Data Architecture Description
    • 3. Develop Target Data Architecture Description
    • 4. Perform Gap Analysis
    • 5. Define candidate roadmap components
    • 6. Resolve impacts across the Architecture Landscape
    • 7. Conduct formal stakeholder review
    • 8. Finalize the Data Architecture
    • 9. Create Architecture Definition Document

Chapter 7 Phase C: Application Architecture

  • The objectives of the Application Architecture part of Phase C are to:
    • Develop the Target Application Architecture that enables the Business Architecture and the Architecture Vision, while addressing the Request for Architecture Work and stakeholder concerns
    • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Application Architectures
  • Phase C: Application Architecture consists of the following steps:
    • 1. Select reference models, viewpoints, and tools
    • 2. Develop Baseline Application Architecture Description
    • 3. Develop Target Application Architecture Description
    • 4. Perform Gap Analysis
    • 5. Define candidate roadmap components
    • 6. Resolve impacts across the Architecture Landscape
    • 7. Conduct formal stakeholder review
    • 8. Finalize the Application Architecture
    • 9. Create Architecture Definition Document

Chapter 8 Phase D: Technology Architecture

  • The objectives of Phase D: Technology Architecture are to:
    • Develop the Target Technology Architecture that enables the logical and physical application and data components and the Architecture Vision, addressing the Request for Architecture Work and stakeholder concerns
    • Identify candidate Architecture Roadmap components based upon gaps between the Baseline and Target Technology Architectures
  • Phase D consists of the following steps:
    • 1. Select reference models, viewpoints, and tools
    • 2. Develop Baseline Technology Architecture Description
    • 3. Develop Target Technology Architecture Description
    • 4. Perform Gap Analysis
    • 5. Define candidate roadmap components
    • 6. Resolve impacts across the Architecture Landscape
    • 7. Conduct formal stakeholder review
    • 8. Finalize the Technology Architecture
    • 9. Create Architecture Definition Document
  • Components of the Architecture Definition Document: The topics that should be addressed in the Architecture Definition Document related to Technology Architecture are as follows:
    • Baseline Technology Architecture, if appropriate
    • Target Technology Architecture, including:
      • Technology components and their relationships to information systems
      • Technology platforms and their decomposition, showing the combinations of technology required to realize a particular technology “stack”
      • Environments and locations with a grouping of the required technology into computing environments (e.g., development, production)
      • Expected processing load and distribution of load across technology components
      • Physical (network) communications
      • Hardware and network specifications
    • Views corresponding to the selected viewpoints addressing key stakeholder concerns.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s