Togaf 9 an introduction

TOGAF 9
“The Open Group Architecture
Framework”
(TOGAF)
“an Introduction”
1

TOGAF
“A Definition”
TOGAF - “The Open Group Architecture Framework”
• TOGAF is a Framework - a Detailed Method and a Set of Supporting Tools - for
Accepting, Developing, Maintaining and Gaining Value from an Enterprise
Architecture.
– Set of Building Blocks and how they Fit Together
• a Framework not an Architecture
– Set of Tools
– Common Vocabulary
– Recommended Standards
– Compliant Products
• TOGAF Version 9.1 (2011)
• Open Standard Developed & Maintained by The Open Group
– The Open Group Architecture Forum
2

Boundaryless Information Flow™
3
The mission of The Open Group Architecture Forum is to
advance The Open Group vision of “Boundaryless
Information Flow”, for and between enterprises
• …achieved through Global Interoperability
• …in a Secure, Reliable and Timely manner
Interoperability
- The ability of two or more systems or components
to exchange information and use the information
that has been exchanged to do useful work.
Boundaryless does not mean there are no boundaries – it
means that boundaries are permeable to enable business.

TOGAF Components
• PART I - Introduction
• PART II - TOGAF Architecture Development Method (ADM)
• PART III - ADM Guidelines & Techniques
• PART IV - TOGAF Architecture Content Framework
• PART V - Enterprise Continuum
• PART VI - TOGAF Reference Models
• PART VII - TOGAF Capability Framework
4

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
TOGAF and release notes detailing the
changes between this version and the
previous version of TOGAF.
5

TOGAF
“Types of Architectures”
• Business Architecture - The business strategy,
governance, organization, and key business
processes.
• Information Systems Architecture = Data
Architecture + Application (s) Architecture
– Data Architecture - The structure of an
organization’s logical and physical data assets and
data management resources.
– Application(s) Architecture - A blueprint for the
individual applications to be deployed, their
interactions, and their relationships to the core
business processes of the organization.
• Technology Architecture - The logical 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.
6

Architecture Development Method
7
The TOGAF Architecture Development
Method (ADM) provides a tested and
repeatable process for developing
architectures.
• Preliminary Phase
• Phase A: Architecture Vision
• Phase B: Business Architecture
• Phase C: Information Systems
Architectures Phase D: Technology
Architecture
• Phase E: Opportunities & Solutions
• Phase F: Migration Planning
• Phase G: Implementation
Governance
• Phase H: Architecture Change
Management
• Requirements Management

Deliverables, Artifacts, and Building Blocks
8
Architects executing the ADM will produce a number of outputs as a result of
their efforts.
• Deliverable is a work product that is contractually specified and in turn
formally reviewed, agreed, and signed off by the Stakeholders.
• Artifact is an architectural work product that describes an aspect of the
architecture.
– catalogs (lists of things)
– matrices (relationships between things)
– diagrams (pictures of things).
• Building Block represents a
(potentially re-usable) component
of business, IT, or Architectural
Capability
– Architecture Building Blocks (ABBs)
– Solution Building Blocks (SBBs)
– Vendor, Product, Version

Enterprise Continuum
9
A Model for Structuring a Virtual Repository and Methods for Classifying
Architecture and Solution Artifacts
• Architecture Continuum
• Solutions Continuum

Architecture Repository
10
Supporting the Enterprise Continuum is the concept of an Architecture
Repository which can be used to store different classes of architectural output
at different levels of abstraction, created by the ADM. In this way, TOGAF
facilitates understanding and co-operation between stakeholders and
practitioners at different levels.
• Architecture Metamodel.
• Architecture Capability
• The Architecture Landscape
• The Standards Information Base (SIB)
• The Reference
• The Governance Log

Establishing and Maintaining an Enterprise
Architecture Capability
11
Enterprise Architecture Capability
• Organization Structures
• Roles
• Responsibilities
• Skills
• Processes

TOGAF Content Overview
“Relationships”
• Central to TOGAF is the Architecture
Development Method (ADM)  TOGAF – Part II
• The Architecture Capability  TOGAF – Part VII
operates the ADM.
• The ADM is supported by a number of Guidelines
and Techniques  TOGAF – Part III
• This produces content to be stored in the
repository  TOGAF – Part IV
• This is classified according to the Enterprise
Continuum  TOGAF – Part V
• The repository is initially populated with the
TOGAF Reference Models  TOGAF – Part VI
13

TOGAF Components
14

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

PART VII - TOGAF Capability Framework
16
A Set of Reference Materials
for how to Establish an
Architecture Function
(Capability).
• Architecture Governance
Framework
– Architecture Board
– Architecture Compliance
• Skills Framework
• Architecture Maturity
Model (CMMI)
• Connection with..
– Strategy
– PMO
• Prince II
– Operations Mgt
• ITIL, Cobit
– Portfolio Mgt

TOGAF Components
17

Part II: Architecture Development Method
This part is the core of TOGAF. It
describes the TOGAF Architecture
Development Method (ADM) – a step-by-
step approach to developing an enterprise
architecture.
18

PART II - Architecture Development Method
(ADM)
19
Central to TOGAF is the Architecture
Development Method (ADM)
This part is the core of TOGAF. It
describes the TOGAF Architecture
Development Method (ADM) – An
Iterative (Continuous) Sequence of
Steps to Develop an Enterprise-wide
Architecture
Possible Iterations
1. Getting the organization committed
and involved
2. Getting the Architecture right
3. Making the Architecture work
4. Keeping the Process running

Architecture Development Method (ADM)
“Getting the organization committed and involved”
20
• Setting up the Architecture
Capability
– Preliminary Phase
• Starting the Architecture Project
– Architecture Vision

“Preliminary Phase”
21
• Setting up the Architecture Capability (Determine &
Establish)
– Management Commitment (Sponsorship)
– Architecture Capability Maturity Model
– Architecture Scope (Environment)
• Breadth
• Depth
• Time
• BDAT
– Roles & Skills
– Establish Architecture Principles
– Establish Governance Structure
– EA Framework
• Choice
• Integration
– Customization of TOGAF
– Tools
– Architecture Repository (Content
Metamodel)
– Deliverables

“A. Architecture Vision”
22
• Starting the Architecture Project
– Request for Architecture Work
– Architecture Vision (High-Level
Overview of the Architectural Change)
• Business Case
• Aspirational View (Target
Architecture)
– Identify Stakeholders
• Stakeholder Management
• Communications Plan
– Business Transformation Readiness
Assessment (BTRA)
– Risk Management
– Validate Business Context
– Architecture Definition Document
(ADD)
– Statement of Architecture work

“Getting the Architecture right”
23
• Architecture Development Phases
– Business Architecture (Phase B)
– Information Systems Architecture (Phase C)
• Data Architecture
• Application(s) Architecture
– Technology Architecture (Phase D)
• Reference Models, Viewpoints and Tools
• Baseline Architecture
• Candidate Architecture Roadmap
Components
• Target Architecture
• Gap Analysis
• Stakeholder Review
• Architecture Definition Document (ADD)

“B. Business Architecture”
24
• Phase B describes the
development of a Business
Architecture to support the
agreed Architecture Vision.
– Business Perspective
– Business Value
– Return on Investment
• Architecture Building Blocks
(ABB)
• Architecture Roadmaps

“C. Information Systems Architectures”
25
• Phase C describes the
development of Information
Systems Architectures to support
the agreed Architecture Vision.
– Applications
– Data
(ABB)

“D. Technology Arechitecture”
26
• Phase D describes the
development of the Technology
Architecture to support the
agreed Architecture Vision
(ABB)

“Making the Architecture work”
27
• Planning the migration to the new
situation.
– Consolidated GAP Analysis
results
– Identify Work Packages
• Establish Migration Plan
– Prioritize Work Packages
• Ensure Compliance between
Architecture and Implementation
Project(s)

“E. Opportunities and Solutions”
28
Opportunities for delivering the
Target Architecture by
implementing specific Solutions
• Solution Building Blocks (SBB)
- Vendor
- Product
- Version
• Consolidated GAP Analysis
– Business Transformation
Readiness Assessment (BTRA)
• Implementation Migration Plan

“F. Migration Planning”
29
Finalize Implementation & Migration Plan and
final Architecture Roadmap
Formalize *.0
Collaboration between…
• Business Planning
• Enterprise Architecture
• Portfolio and Project Management
• Operations Management
Prioritize efforts based on…
- Performance Evaluation
- Return-on-Investment
- Business Value
- Critical Success Factors
- Measures of Effectiveness
- Strategic Fit.

“G. Implementation Governance”
30
Ensure Compliance between
Architecture and Implementation
Project(s)
Architectural Contract
- Sponsor
- Implementation Partner
• Confirming Scope & Priorities
• Guiding Development
• Perform Compliance Reviews

“Keeping the Process running”
31
• Requirements
– Management
– Prioritization
– Version Control
• Architecture Change Management
– Fit for Purpose
– New Requirements
– (Possible) New Development
Cycle

“H. Architecture Change Management”
32
• Change Management
– Monitoring Governance Requests
– New Technologies
– Changes in the Business Environment
• Respond to Change
– Simple Architecture Update or
– New ADM Cycle
• Change Requests
– Simplification - reduce investment
– Incremental change - derive additional
value from existing investment;
– Re-architecting - change increase
investment and create new value.
• Fit for Purpose

“Requirements Management”
33
• Process for Managing
Requirements throughout the
overall ADM
- Each Phase / Cycle of the ADM
- Produce
- Analyze
- Review
• Architecture Requirements
Specification (ARS)
• Requirements Impact Assessment
(RIA)

TOGAF Components
34

Part III: ADM Guidelines and Techniques
This part contains a collection of guidelines
and techniques available for use in
applying the ADM.
35

PART III - ADM Guidelines & Techniques
• Guidelines and Techniques to support the application and adoption
of the ADM
– Guidelines
– Templates
– Checklists
– Techniques
36

ADM Guidelines & Techniques
• Guidelines
– Iteration
• Architecture Context
• Architecture Definition
• Transition Planning
• Architecture Governance
– Levels
• Strategic
• Segmented
• Capability
– Adjust ADM for…
• SOA
• Security
37

ADM Guidelines & Techniques
• Techniques
– Principles
– Stakeholder Management
– Business Scenarios
– GAP Analysis
– Architecture Planning
– Migration Planning
– Capability Based Planning
– Interoperability Requirements
– Business Transition Readiness Assessment (BTRA)
– Risk Management
38

TOGAF Components
39

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

PART IV - TOGAF Architecture Content
Framework
41
Consistency of
Architectural Content
• Catalogs
• Matrices
• Diagrams
Provides a Detailed
Model of Architectural
Work Products

TOGAF Architecture Content Framework
“Full Content Metadata Model”
42
Core Content Metadata Model +
6 Extensions …
• Governance
• Services
• Process Modeling
• Data
• Infrastructure Consolidation
• Motivation

TOGAF Architecture Content Framework
“Architectural Artifacts”
• A "system" is a collection of components organized to accomplish a specific function
or set of functions.
• "Stakeholders" are people who have key roles in, or concerns about, the system
• "Concerns" are the key interests that are crucially important to the stakeholders in the
system
• A "view" is a representation of a whole system from the perspective of a related set of
concerns.
• A "viewpoint" defines the perspective from which a view is taken.
43
• Catalogs are lists of building blocks.
• Matrices show the relationships
between building blocks of specific
types.
• Diagrams present building blocks
plus their relationships and
interconnections in a graphical way
that supports effective stakeholder
communication.

Architecture Deliverables
• Request for Architecture Work
• Statement of Architecture Work
• Communications Plan
• Architecture Vision Document
• Architecture Requirements
• Architecture Defenition Document (ADD)
• Architecture Roadmap
• Implementation & Migration Plan
• Architecture Contract
44

TOGAF Components
45

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.
• Enterprise Continuum
• Architecture Partitioning
• Architecture Repository
• Tools for Architecture Development
46

PART V - Enterprise Continuum
47
A Model for Structuring
a Virtual Repository and
Methods for Classifying
Architecture and
Solution Artifacts
• Foundation
• Common System
• Industry
• Organization-
Specific

TOGAF Components
48

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).
49

PART VI - TOGAF Reference Models
“Technical Reference Model (TRM)”
50
• A Foundation
Architecture
• A Model and a
Taxonomy of
Generic Platform
Services

TOGAF Reference Models
“Integrated Information Infrastructure Model (III-RM)”
51
• A Model for Business
Applications and
Infrastructure
Applications
• Specifically aimed to
Support the Vision of
Boundaryless
Information Flow™

Inspiration
This content is inspired and based on (online) content from the following
parties
The Open Group (http://bit.ly/TOGAF_91_online)
The Unit (Joost Bleijenberg - http://bit.ly/TOGAF9_Overview)
Bizz Design (http://bit.ly/TOGAF91_Archimate21_BizzDesign)
Orbus Software (http://bit.ly/TOGAF_Distilled)
52

Togaf 9 an introduction

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (19)

Similar to Togaf 9 an introduction

Similar to Togaf 9 an introduction (20)

More from Daan Bakboord

More from Daan Bakboord (9)

Recently uploaded

Recently uploaded (20)

Togaf 9 an introduction