TOGAF 9 Foundation

TOGAF Standard

Architecture framework that provides methods and tools for assisting in the acceptance, production, use and maintenance of Enterprise Architecture.

Based on an iterative process.

TOGAF Standard structure

1. Introduction

2. ADM

3. ADM Guidelines and Techniques

4. Architecture Content Framework

5. Enterprise Continuum and Tools

6. Architecture Capability Framework

Architecture Development Method

A process for deriving an organization-specific Enterprise Architecture that addresses Business Requirements.

Provides a number of Architectural Development Phases in a cycle.

Provides a narrative of each architecture phase, in terms of objectives, approach, inputs, steps and outputs.

Provides cross-phase summaries that cover requirements management.

ADM Guidelines and Techniques (Overview)

Provides a number of guidelines and techniques to support the application of the ADM.

ADM Guidelines

Include adapting the ADM to deal with a number of usage scenarios, including different process styles and applying the ADM across the Architecture Landscape.

ADM Techiques

Support specific tasks within the ADM such as Capability-Based Planning, defining principals gap analysis, migration planning, risk management, and stakeholder management.

ADM Phases

Architecture Content Framework

A detailed model of architectural work products, deliverables, artifacts within deliverables, and the Architectural Building Blocks (ABBs) that deliverables represent.

Enterprise Continuum

A model for structuring a virtual repository and provides methods for classifying architecture and solution artifacts, showing how the different types of artifacts evolve, and how they can be leveraged reused as they evolve from generic Foundation Architectures to Organization-Specific Architectures.

Architecture Capability Framework

A set of resources, guidelines, background information, provided to help the architect establish an architecture practice within an organization.

What best describes the TOGAF Standard?

A framework and method for architecture development.

What best describes why you need a framework for Enterprise Architecture?

A framework provides a set of tools and a common vocabulary.

Architecture Domains Supported by TOGAF

1. Business Architecture

2. Data Architecture

3. Application Architecture

4. Technology Architecture

Business Architecture

The business strategy, governance, organization, and key business processes.

A representation of holistic, multi-dimensional business views of: capabilities, end-to-end value delivery, information, and organizational structure; and the relationships among these business views and strategies, products, policies, initiatives, and stakeholders.

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.

A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage data assets.

Technology Architecture

The software and hardware capabilities that are required to support the deployment of business, data and their application services.

This includes IT Infrastructure, middleware, networks, communications, processing and standards.

Capability

An ability that an organization, person, or system possess.

Preliminary Phase

Preparation and initiation activities required to create an Architecture Capability, including the customization of the TOGAF Framework, and definition of Architecture Principles.

Architecture Vision (Phase A)

Initial phases of an Architecture Development Cycle.

Defining:

- Scope

- Identifying Stakeholders

- Creating the Architecture Vision

- Obtaining approvals (needed to proceed to phase B)

Business Architecture (Phase B)

Describes the development of a Business Architecture to support an agreed Architecture Vision.

Information Systems Architecture (Phase C)

Describes the development of Information Systems Architectures for an architecture project, including development of Data and Application Architectures.

Technology Architecture (Phase D)

Describes the development of the Technology Architecture for an architecture project.

Opportunities and Solutions (Phase E)

The process of identifying major implementation projects and grouping them into work packages that deliver the Target Architecture.

Migration Planning (Phase F)

Describes the development of a detailed Implementation and Migration Plan that addresses how to move forward from the Baseline to the Target Architecture.

Implementation Governance (Phase G)

Provides an architectural oversight of the implementation.

Architecture Change Management (Phase H)

Establishes procedures for managing change to the new architecture.

Requirements Management (Central to ADM Phases)

The process of managing architecture requirements throughout the ADM.

Architecture Content Framework (Categories)

These 3 categories describe the type of architectural work product within the context of use.

Deliverables, Artifacts, and Building Blocks.

Deliverable

A work product that is contractually specified and in turn formally reviewed, agreed and signed off on by stakeholders.

These represent the output of projects. Those that are in documentation form will typically be archived at completion of a project, or transitioned into an Architecture Repository as a reference model, standard or snapshot of the Architecture Landscape at a specific point in time.

Artifact

an architectural work product that describes an aspect of architecture.

Catalogs, matrices, and diagram.

Forms the content of the Architecture Repository.

Building Block

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.

Architecture Building Blocks (ABB)

Typically describe the required capability in order to shape the Solution Building Blocks (SBB).

Solution Building Blocks (SBB)

Represent the components to be used to implement the required capability.

Enterprise Continuum (Detailed)

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.

Comprises 2 complementary concepts:

- Architecture Continuum

- Solutions Continuum

TOGAF Documents

Foundation -> Generic -> Industry -> Organization Specific

Builds off each other from Foundation to Organization.

Architecture Repository

Used to store different classes of architectural output at different levels of abstraction, created by the ADM.

Architecture Repository (Major Components)

1. Architecture Metamodel

2. Architecture Capability

3. Architecture Landscape

4. Standards Information Base (SIB)

5. Reference Library

6. Governance Log

7. Architecture Requirements Repository

8 Solutions Landscape

Architecture Metamodel

Describes organizationally tailored application of an architecture framework, including a metamodel for architecture content.

Architecture Capability

Defines the parameters, structures, and processes that support governance of the Architecture Repository

Architecture Landscape

Shows an architectural view of the building blocks that are in use within the organization today.

Likely to exist at multiple levels of abstraction to suit different architecture objectives.

Standards Information Base (SIB)

Captures the standards with which new architectures must comply. May include industry standards, selected products and services from suppliers, or shared services already deployed within the organization.

Reference Library

Provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise

Governance Log

provides a record of governance activity across the enterprise

Architecture Requirements Repository

Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board.

Solutions Landscape

An architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed by the enterprise.

Enterprise Continuum (Diagram)

Layout of Enterprise Continuum. Should be able to explain core concepts.

Architecture Capability Framework Contents

1. Establishing an Architecture Capability

2. Architecture Board

3. Architecture Compliance

4. Architecture Contracts

5. Architecture Governance

6. Architecture Maturity Models

7. Architecture Skills Framework

Architecture Capability Framework (Diagram)

Layout of Architecture Capability Framework. Should be able to explain core concepts.

Establishing an Operational Architecture Capability

Should be treated like a business and establish capabilities in the following areas:

1. Financial Management

2. Performance Management

3. Service Management

4. Risk Management

5. Resource Management

6. Communications and Stakeholder Management

7. Quality Management

8. Supplier Management

9. Configuration Management

10. Environment Management.

Establishing an Architecture Capability

Guidelines for establishing an Architecture Capability within an organization.

Architecture Board

Guidelines for establishing and operating an enterprise Architecture Board.

Architecture Compliance

Guidelines for ensuring project compliance to architecture.

Architecture Contracts

Guidelines for defining and using Architecture Contracts.

Architecture Maturity Models

Techniques for evaluating and quantifying an organization's maturity in Enterprise Architecture.

Architecture Skills Framework

A set of role, skill, and experience norms for staff undertaking Enterprise Architecture work.

Architecture Governance

Frameworks and guidelines for establishing Architecture governance.

Whereby all architecturally significant activity is controlled and aligned within a single framework.

The practice of monitoring and directing architecture-related work.

The goal is to deliver desired outcomes and adhere to relevant principles, standards, and roadmaps.

Architecture Governance benefits

1. Increased transparency of accountability, and informed delegation of authority.

2. Controlled risk management

3. Protection of the existing asset base through maximizing re-use of existing architecture components.

4. Proactive control, monitoring and management mechanisms.

5. Process, concept and component re-use across all organizational business units.

6. Value creation through monitoring, measuring, evaluation and feedback.

7. Increased visibility supporting internal processes and external parties requirements.

8. Greater shareholder value.

9. Integrates with existing processes and methodologies and complements functionality by adding control capabilities.

Using TOGAF with other frameworks

The TOGAF Standard is a generic framework that provides a flexible and extensible content framework that underpins a set of generic architecture principles.

It is expected that architects will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise.

This tailoring may including adopting elements from other architecture frameworks such as ITIL, CMMI, COBIT, etc.

As a generic framework and method for EA, TOGAF also complements other frameworks that are aimed at specific vertical business domains, specific horizontal technology areas, or specific application areas.

Which phase of the ADM provides oversight of the implementation?

Phase G Implementation Governance

Which phase of the ADM includes creation and approval of the Architecture Vision document?

Phase A Architecture Vision

The Enterprise Continuum provides

methods for classifying artifacts.

Which component of the Architecture repository provides guidelines, templates and patterns that can be used to create new architectures?

Reference Library

Architectural Style

The combination of distinctive features related to the specific context within which architecture is performed or expressed.

A collection of principles and characteristics that steer or constrain how an architecture is formed.

Architecture

1. The fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution.

2. The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.

Architecture Building Block (ABB)

A constituent of the architecture model that describes a single aspect of the overall model.

Architecture Continuum

A part of the Enterprise Continuum.

Begins with the foundational definitions such as reference models, core strategies, and basic building blocks. From there it spans to Industry Architectures and all the way to an organization's specific architecture.

Architecture Development Method

Core of the TOGAF framework. A multi-phase, iterative approach to develop and use an Enterprise Architecture to shape and govern business transformation and implementation projects.

Architecture Domain

The architectural area being considered.

TOGAF has 4 primary domains (BDAT):

- Business

- Data

- Application

- Technology

Architecture Framework

A conceptual structure used to plan, develop, implement, govern, and sustain an architecture.

Architecture Principle

A quantitative statement of intent that should be met by the architecture.

Architecture View

A representation of a system from the perspective of a related set of concerns.

Architecture Viewpoint

A specification of the conventions for a particular kind of architecture view.

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.

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.

Business Capability

A particular ability that a business may possess or exchange to achieve a specific purpose.

Business Governance

Concerned with ensuring that the business processes and policies (and their operation) deliver the business outcomes and adhere to relevant business regulation.

Concern

An interest in a system relevant to one or more of its stakeholders.

Course of Action

Direction and focus provided by strategic goals and objectives, often to deliver the value proposition characterized in the business model.

Enterprise

The highest level (typically) of description of an organization and typically covers all missions and functions. An enterprise will often span multiple organizations.

Foundation Architecture

Generic building blocks, their inter-relationships with other building blocks, combined with the principles and guidelines that provide a foundation on which more specific architectures can be built.

Gap

A statement of difference between two states. Used in gap analysis where the Baseline and Target Architecture is identified.

Governance

The discipline of monitoring, managing, and steering a business to deliver the business outcome required.

Information

Any communication or representation of facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audio-visual.

Information Technology (IT)

1. The lifecycle management of information and related technology used by an organization.

2. An umbrella that includes all or some of the subject areas relating to the computer industry.

3. A term commonly assigned to a department within an organization tasked with provisioning some or all of the relevant domains.

4. Alternate names commonly adopted include Information Services, Information Management, etc.

Logical Architecture

An implementation-independent definition of the architecture, often grouping related physical entities according to their purpose and structure; for example, the products from multiple infrastructure software vendors can all be logically grouped as Java® application server platforms.

Metadata

Data about data, of any sort in any media, that describes the characteristics of an entity.

Metamodel

A model that describes how and with what the architecture will be described in a structured way.

Method

A defined, repeatable approach to address a particular type of problem.

Modeling

A technique through construction of models which enables a subject to be represented in a form that enables reasoning, insight, and clarity concerning the essence of the subject matter.

Objective

A time-bounded milestone for an organization used to demonstrate progress towards a goal.

Physical

A description of a real-world entity.

Reference Model

An abstract framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. Based on small number of unifying concepts and may be used as a basis for education and explaining standards.

Facilitates efficient communication of system details between stakeholders

Provides a point of reference for system designers to extract system specifications

Repository

A system that manages all of the data of an enterprise, including data and process models and other enterprise information.

Requirement

A statement of need that must be met by a particular architecture or work package.

Segment Architecture

A detailed, formal description of areas within an enterprise, used at the program or portfolio level to organize and align change activity.

Service

A repeatable activity; a discrete behavior that a building block may be requested or otherwise triggered to perform.

An element of behavior that provides specific functionality in response to requests from actors or other services.

Solution Architecture

A description of a discrete and focused business operation or activity and how IS/IT supports that operation.

Note: A Solution Architecture typically applies to a single project or project release, assisting in the translation of requirements into a solution vision, high-level business and/or IT system specifications, and a portfolio of implementation tasks.

Solutions Continuum

A part of the Enterprise Continuum. A repository of re-usable solutions for future implementation efforts. It contains implementations of the corresponding definitions in the Architecture Continuum.

Stakeholder

An individual, team, organization or class thereof, having an interest in a system.