Course Structure

Day 1

Foundations of Enterprise Architecture

 Definitions of Enterprise, Architecture and Architecture Framework in the context of TOGAF

TOGAF9 Core Concepts

 Role of an Enterprise Architect

Enterprise Architecture should know the following
 Policy – Standards and principles
 Business – Process and Organization
 Governance – Compliance and maturity
 Technology – Forecasting and assessments
 Key Characteristics of an Enterprise Architect
o Skills and experience is producing designs
o Extensive technical breadth and depth
o Method-driven approach to execution
o Full Project scope experience
o Leadership (Communication and team building)
o Personal and professional skills
o Skills and experience in one or more industries (strategic technical leadership)
 Architecture Skills framework

It defines

o Roles within a work area

o The skills required within each role
o The depth of knowledge required to fulfill the role successfully
The Architecture Content Framework

Structural model for architectural content that allows major work products that an architect
creates to be consistently defined structured and presented.

Grouped into

 Deliverable
Work product that is contractually specified and in turn formally reviewed, agreed, and
signed off by the stakeholders.

 Artifact
Architectural work product that describes an aspect of the architecture.
(Catalogs (requirements catalog), matrices (business interaction matrix), and diagrams
(use case diagrams))

 Building block

Components of business, IT, or architectural capability that can be combined with other
building blocks. It represents a (potentially re-usable) component of business.

Artifacts describe building block (eg. Customer services representative, baseline call
handling process etc.).

Architectural Building Blocks (ABB) - Describe required capability and shape the
specification of Solution Building Blocks.

Solution Building Blocks (SBB) – Describe components that will be used to implement
required capability.

Eg. Customer service capability (ABB) may be required within an enterprise, supported
by many SBBs, such as processes, data, and application software.

Content Meta Model

Provides a definition of all types of building blocks that may exist within an enterprise, showing how
these building blocks can be described and related to one another.
For example, when creating architecture, an architect will identify applications, “data entities” held
within applications, and technologies that implement the applications. These applications will in turn
support particular group of business user or actors to fulfill “business services”.

(Overview of Content metamodel)

Content Framework and the TOGAF ADM

TOGAF ADM describes the process of moving from a baseline state of the enterprise to the
target state of the enterprise.

The Content framework provides and underlying structure for the ADM and describes what the
architecture should look like once it is done.
Day 2

The Architecture Content Framework

 Core Content Metamodel

Content Metamodel defines formal structure for the entities that are used to build
architecture description to ensure consistency within the ADM and also provide
guidance for organizations that wish to implement their architecture within an
architecture tool.

 Architectural Artifacts
Catalog, Matrix, and Diagrams

(Artifacts in Each phase of ADM)

  Architecture Deliverables

TOGAF Content Framework identifies deliverables that are produced as outputs from executing the
ADM cycle and potentially consumed as input at other points in ADM.

 Building blocks

Characteristics

 A package of functionality defined to meet the business needs across an organization.

 A type that corresponds to TOGAF content meta model (such as actor, business service,
application etc.)
 A defined boundary and is generally recognized as “a thing” by domain experts.
  May interoperate with other inter-dependent building blocks.

Architecture Building Blocks:

 Capture architecture requirements; eg. Business, data, application and technology

Solution Building Blocks:

 Defines what products and components will implement the functionality

 Define the implementation
 Fulfill business requirements
 Are product or vendor-aware

Architecture Repository

Allows enterprise to distinguish between different types of architectural assets that

exist at different levels of abstraction in the organization.

Holds information concerning Enterprise Architecture activities and their associated

artifacts.

Six classes of architectural information are expected to be held within an Architecture Repository.

1. Architecture metamodel

Describes the organizationally tailored application of an architecture framework,

including a method for architecture development and a metamodel for architecture content.

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

3. Architecture Landscape
Presents an architecture representation of assets in use, or planned, by the enterprise at
a particular points in time.
Architecture landscape again divided into three levels of granularity:

Strategic architecture: Long term summary view of the entire enterprise

Segment architecture: Provide more detailed operating models for areas within an enterprise.
Capability architecture: Show in a more detailed fashion how the enterprise can support a
particular unit of capability. Provides an overview of current capability, target capability, and
capability increments.
 4. Standards Information Base
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.

5. 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.

6. Governance Log

Provides a record of governance activity across the enterprise.

Enterprise Continuum

Provides methods for classifying architecture and solution artifacts , both internal and external
to the architecture repository, as they evolve from generic foundation architectures to organization
specific architectures.
The Architecture Development Method

It describes a method for developing and managing the lifecycle of an enterprise architecture,
and forms the core of TOGAF.
Relationship between ADM and Enterprise Continuum

The enterprise continuum provides a view of the architecture assets that are stored in the Architecture
Repository. These assets may include architecture descriptions, models, and patterns taken from a
variety of sources.

Relationship between ADM and Architecture Repository

Throughout the ADM, there are reminders to consider which, if any, architecture assets from the
architecture repository the architect should use. For example, for the development of technology
architecture, TOGAF Foundation Architecture can be used. In case of Business architecture, it may be a
reference model for the e-Commerce application from the industry at large.

Architecture development is a continuous, cyclic process, and in executing the ADM repeatedly
over time, more and more content will be added to the organization’s Architecture Repository.

ADM Phases & Steps

1. Select reference models, viewpoints and tools

2. Develop baseline architecture description
3. Develop target 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 Architecture
9. Create Architecture Definition Document