TOGAF Learning Outcome: Core Concepts

TOGAF Learning Outcome: Core Concepts

The Candidate must be able to define and explain the following core concepts:
1. The ADM: phase names and the purpose of each phase (high-level)

ADM consists of following phases:

• Preliminary Phase
  Describes the preparation and initiation activities required to create an architecture capability including customization of TOGAF & definition of Architecture principles
• Phase A – Architecture Vision
  Describes initial phase of Architecture Development Cycle. It includes information about
  • defining scope of architecture development initiative,
  • identifying the stakeholders,
  • creating Architecture Vision, and
  • obtaining approval to proceed with architecture development.
• Phase B – Business Architecture
  Describes the development of business architecture to support agreed architecture vision.
• Phase C – Information Systems Architecture
  Describes development of information systems architectures (Data & Application) to support agreed architecture vision.
• Phase D – Technology Architecture
  Describes development of technology architecture to support agreed architecture vision.
• Phase E – Opportunities and Solutions
  In this phase, initial implementation planning is conducted and delivery vehicles for the architecture defined in previous phases are identified.
• Phase F – Migration Planning
  This phase addresses how to move from the Baseline architecture to Target architecture by finalizing a detailed implementation and migration plan.
• Phase G – Implementation Governance
  This phase provides an architecture oversight of the implementation.
• Phase H – Architecture Change Management
  Establishes procedures for managing change to the new architecture.
• Requirements Management
  Examines process for managing architecture requirements throughout the ADM.

2. The Architecture Content Framework: deliverables, artifacts, and building blocks

• Deliverable
  A work product that is contractually specified, formally reviewed, agreed and signed off by stakeholders.

• Artifact
  An architectural work product that describes an aspect of the architecture.Artifacts can be diagrams, matrices or catalogs.

• Building Block
  It represents a potentially re-usable component of business, IT or architectural capability that can be combined with other building blocks to deliver architectures and solutions.

3. The Enterprise Continuum

The Enterprise Continuum is a view of the architecture repository that provides methods for classifying architecture and solution artifacts as they evolve from Foundation architectures to Organization-specific architectures.
4. The Architecture Repository

An architecture repository stores different classes of architectural output at different levels of abstraction, created by ADM.

5. How to establish and maintain an enterprise Architecture Capability

In order to carry out architectural activity effectively in an enterprise, it is important to put in place appropriate business capability for architecture through organization structures, roles, responsibilities, skills and processes. Below diagram shows an overview of TOGAF architecture capability.

6. Establishing the Architecture Capability as an operational entity

Central to the notion of operating an ongoing architecture is the execution of well defined and effective governance, whereby all significant architecture activity is controlled and aligned within a single framework. To this end, an enterprise architecture practice should establish capabilities in following areas:

• Financial management
• Performance management
• Service management
• Risk management
• Resource management
• Communications and stakeholder management
• Quality management
• Supplier management
• Configuration management
• Environment management

7. How to use TOGAF with other frameworks

TOGAF is a generic framework and is intended to be used in a wide variety of environments. It provides a flexible and extensible content framework that underpins a set of generic architecture deliverables.

TOGAF can be used

• Either in its own right, with its generic deliverables as outlined.
• Extend TOGAF deliverables by replacing or extending by a more specific set, defined in any other framework that the architect considers relevant.