TOGAF Certification Series 2: Foundations Core Concepts

Chapter 3: Core Concepts

  • What are the ADM phase names and the purpose of each phase?

  • The Preliminary Phase describes the preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF framework, and the definition of Architecture Principles.
  • Phase A: Architecture Vision describes the initial phase of an Architecture Development Cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals.
  • Phase B: Business Architecture describes the development of a Business Architecture to support an agreed Architecture Vision.
  • Phase C: Information Systems Architectures describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures.
  • Phase D: Technology Architecture describes the development of the Technology Architecture for an architecture project.
  • Phase E: Opportunities and Solutions describes the process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture defined in the previous phases.
  • Phase F: Migration Planning describes the development of a detailed Implementation and Migration Plan that addresses how to move from the Baseline to the Target Architecture.
  • Phase G: Implementation Governance provides an architectural oversight of the implementation.
  • Phase H: Architecture Change Management establishes procedures for managing change to the new architecture.
  • Requirements Management examines the process of managing architecture requirements throughout the ADM.
  • What are deliverables, artifacts, and building blocks?

  • What is 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 generic Foundation Architectures to Organization-Specific Architectures. The Enterprise Continuum comprises two complementary concepts: the Architecture Continuum and the Solutions Continuum.

The Enterprise Continuum and the Architecture Repository The Enterprise Continuum provides a view of the Architecture Repository that shows the evolution of these related architectures from generic to specific, from abstract to concrete, and from logical to physical. [Source: TOGAF 9 Part V: Enterprise Continuum and Tools]

  • What is the Architecture Repository?

Architecture Repository is used to store different classes of architectural output at different levels of abstraction

The major components within an Architecture Repository are as follows:

  • The Architecture Metamodel describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content.
  • The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository.
  • The Architecture Landscape shows an architectural view of the building blocks that are in use within the organization today (e.g., a list of the live applications). The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives
  • The Standards Information Base (SIB) captures the standards with which new architectures must comply, which may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.
  • The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged to accelerate the creation of new architectures for the enterprise.
  • The Governance Log provides a record of governance activity across the enterprise. abstraction to suit different architecture objectives
  • How to establish and operate an enterprise architecture capability?

    The benefits of Architecture Governance include:

  • Increased transparency of accountability, and informed delegation of authority
  • Controlled risk management
  • Protection of the existing asset base through maximizing re-use of existing architectural components
  • Proactive control, monitoring, and management mechanisms
  • Process, concept, and component re-use across all organizational business units
  • Value creation through monitoring, measuring, evaluation, and feedback
  • Increased visibility supporting internal processes and external parties’ requirements; in particular, increased visibility of decision-making at lower levels ensures oversight at an appropriate level within the enterprise of decisions that may have far-reaching strategic consequences for the organization
  • Greater shareholder value; in particular, enterprise architecture increasingly represents the core intellectual property of the enterprise – studies have demonstrated a correlation between increased shareholder value and well-governed enterprises
  • Integrates with existing processes and methodologies and complements functionality by adding control capabilities
  • How to use the TOGAF framework with other frameworks?

Why is the TOGAF standard becoming so popular in the industry? One key reason is that architects can use the TOGAF ADM in conjunction with any of the popular frameworks. The TOGAF ADM is framework-agnostic and helps IT architects fill in the framework they might already have in use.

Chapter 4: Key Terminology

  • Architecture: Architecture has two meanings depending upon its contextual usage:
    • A formal description of a system, or a detailed plan of the system at component level to guide its implementation
    • The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.
  • Architecture Principles: A qualitative statement of intent that should be met by the architecture. Has at least a supporting rationale and a measure of importance.
  • Architecture Vision: A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.
  • Baseline: A specification that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development or change and that can be changed only through formal change control procedures or a type of procedure such as configuration management.

TOGAF Certification Series 1: Foundations Introduction

Chapter 1 Introduction:

  • Why is TOGAF certification important? The existence of a certification program for the TOGAF standard provides a strong incentive for organizations to standardize on the TOGAF standard as the open method for enterprise architecture, and so avoid lock-in to proprietary methods. It is an important step in making enterprise architecture a well-recognized discipline, and in introducing rigor into the procurement of tools and services for enterprise architecture.
  • The purpose of certification to TOGAF 9 Level 1, known as TOGAF 9 Foundation, is to provide validation that the candidate has gained an acceptable level of knowledge of the terminology, structure, and basic concepts of TOGAF 9, and understands the core principles of enterprise architecture and the TOGAF standard
  • Individuals certified at this level will have demonstrated their understanding of:
    • The basic concepts of enterprise architecture and the TOGAF standard
    • The core concepts of TOGAF 9
    • The key terminology of TOGAF 9 
    • The ADM cycle and the objectives of each phase, and how to adapt and scope the ADM
    • The concept of the Enterprise Continuum; its purpose, and its constituent parts
    • How each of the ADM phases contributes to the success of enterprise architecture
    • The ADM guidelines and techniques
    • How Architecture Governance contributes to the Architecture Development Cycle
    • The concepts of views and viewpoints and their role in communicating with stakeholders
    • The concept of building blocks
    • The key deliverables of the ADM cycle
    • The TOGAF reference models
    • The TOGAF certification program
  • What is the relationship between TOGAF 9 Foundation and TOGAF 9 Certified? The learning outcomes for TOGAF 9 Foundation are a subset of those for TOGAF 9 Certified. Candidates are able to choose whether they wish to become certified in a stepwise manner by starting with TOGAF 9 Foundation and then at a later date TOGAF 9 Certified, or alternately to go direct to TOGAF 9 Certified by taking the combined examination

Chapter 2 Basic Concepts:

  • What is the TOGAF Standard? The TOGAF standard is an architecture framework. The TOGAF standard is a tool for assisting in the acceptance, production, use, and maintenance of enterprise architectures. It is based on an iterative process model supported by best practices and a re-usable set of existing architectural assets.
  • Structure of the TOGAF Document:
    • Part I: Introduction This part provides a high-level introduction to the key concepts of enterprise architecture and, in particular, to the TOGAF approach. It contains the definitions of terms used throughout the TOGAF standard and release notes detailing the changes between this version and the previous version of the TOGAF standard.
    • Part II: Architecture Development Method (ADM) This part is the core of the TOGAF standard. It describes the TOGAF Architecture Development Method (ADM) – a step-by-step approach to developing an enterprise architecture.
    • Part III: ADM Guidelines and Techniques This part contains a collection of guidelines and techniques available for use in applying the ADM.
    • Part IV: Architecture Content Framework This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable Architecture Building Blocks (ABBs), and an overview of typical architecture deliverables.
    • Part V: Enterprise Continuum and Tools: This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise.
    • Part VI: TOGAF Reference Models: This part provides two architectural reference models, namely the TOGAF Technical Reference Model (TRM), and the Integrated Information Infrastructure Reference Model (III-RM).
    • Part VII: Architecture Capability Framework: This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture practice within an enterprise.
  • What is an Enterprise? An “enterprise” is any collection of organizations that has a common set of goals. For example, an enterprise could be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership. The term “enterprise” in the context of “enterprise architecture” can be used to denote both an entire enterprise, encompassing all of its information systems, and a specific domain within the enterprise. An extended enterprise frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units. For example, an organization with an online store that uses an external fulfillment house for dispatching orders would extend its definition of the enterprise in that system to include the fulfillment house.
  • What is Architecture in the Context of the TOGAF Standard? Architecture has two meanings depending upon the context:
    • 1. A formal description of a system, or a detailed plan of the system at a component level to guide its implementation \
    • 2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time
  • Enterprise architecture is:
    • 1. The organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the firm’s operating model.
    • 2. A conceptual blueprint that defines the structure and operation of an organization. The intent of an enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives.
  • Why do I Need Enterprise Architecture? The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes (both manual and automated) into an integrated environment that is responsive to change and supportive of the delivery of the business strategy. Effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage. An enterprise architecture addresses this need, by providing a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment. Ultimately, the benefits of enterprise architecture derive from the better planning, earlier visibility, and more informed designs that result when it is introduced.
  • What is an Architecture Framework? An architecture framework is a foundational structure, or set of structures, that can be used for developing a broad range of different architectures. It should describe a method for designing a target state of the enterprise in terms of a set of building blocks, and for showing how the building blocks fit together. It should contain a set of tools and provide a common vocabulary. It should also include a list of recommended standards and compliant products that can be used to implement the building blocks. Using an architecture framework will speed up and simplify architecture development, ensure more complete coverage of the designed solution, and make certain that the architecture selected allows for future growth in response to the needs of the business.
  • Why is the TOGAF Standard Suitable as a Framework for Enterprise Architecture? Using the TOGAF standard results in enterprise architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration both to current requirements and to the perceived future needs of the business.
  • What are the Different Architecture Domains that the TOGAF Standard deals with?
    • Business Architecture: The business strategy, governance, organization, and key business processes.
    • Data Architecture: The structure of an organization’s logical and physical data assets and data management resources.
    • Application Architecture: A blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
    • Technology Architecture: The software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, and standards.
  • Definition of “Capability”: An ability that an organization, person, or system possesses. Capabilities are typically expressed in general and high-level terms and typically require a combination of organization, people, processes, and technology to achieve. For example, marketing, customer contact, or outbound telemarketing.
    • An enterprise architecture capability (or architecture capability) in the context of the TOGAF standard, is the ability for an organization to effectively undertake the activities of an enterprise architecture practice.
  • What does the TOGAF Standard Contain?
  • TOGAF Reference Models
    • TOGAF Foundation Architecture Technical Reference Model: The TOGAF Technical Reference Model is an architecture of generic services and functions that provides a foundation on which specific architectures and Architecture Building Blocks (ABBs) can be built.
    • Integrated Information Infrastructure Reference Model (III-RM) : The Integrated Information Infrastructure Reference Model (III-RM) is based on the TOGAF Foundation Architecture, and is specifically aimed at helping the design of architectures that enable and support the vision of Boundaryless Information Flow.