The Open Group OG0-091 - TOGAF 9 Part 1

They are a package of functionality intended to meet the business needs across the organization

They should have stable, published interfaces that allow other building blocks to interoperate with them

They are equivalent to software component objects or web services

They may have multiple implementations but with different, interdependent Building Blocks

They may be assembled from other Building Blocks

Risk analysis is best conducted in the Architecture Vision phase so that the risk is eliminated in subsequent phases

Risk analysis should be carried out first in the Migration Planning phase

Risk analysis is outside the scope of enterprise architecture projects

Risk is pervasive in all enterprise architecture activity and should be managed in all phases of the ADM

The only risks that are within the scope of enterprise architecture are technological risks

Standards Information Base

Enterprise Continuum

Governance Log

Architecture Landscape

Reference Library

They should not be reused in other enterprise architecture projects

They should have stable, published interfaces that allow other building block to interoperate with them

They are packages of functionality intended to meet the business needs across the organization

They have defined boundaries

Architecture Landscape

Architecture Vision

Enterprise Continuum

Governance Log

Standards Information Base

Part I, the Enterprise Continuum, describes a model for structuring a virtual repository

Part II, the Architecture Development Method, describes the definitions of terms used in TOGAF, and the changes between versions of TOGAF

Part III, Tools and Support, describes a collection of guidelines and techniques used in the other parts of TOGAF

Part VI, TOGAF Reference Models, includes a model for release management of the TOGAF specification

Part VII, the Architecture Capability Framework, describes processes and skills to establish an enterprise function

Common Systems Architecture

Industry Specific Architecture

Foundation Solution

Organization Specific Solution

Technology Neutral Implementation

addresses and resolves requirements between ADM phases

is a central process that prioritizes requirements for all ADM phases

is used to dispose of resolved requirements for all ADM phases

generates new requirements and passes them to all ADM phases

stores requirements and manages their flow into relevant ADM phases

Architecture Domains

Enterprise Focus

Level of Detail

Subject Matter

Time Period

Design a viewpoint to address all stakeholder concerns

Develop views for the target architecture first

Ensure completeness of the architecture

Refer to existing libraries of viewpoints, to identify one for re-use