Good e-Learning Resources :: www.goodelearning.

com/downloads

TOGAF Poster Series #51

TOGAF Techniques
by Roger Evernden
TOGAF Part III describes some Techniques that can be used in conjunction with the ADM. Here is a useful summary of the Techniques described in TOGAF 9.1.
Weve included the Chapter number for each Technique to make it easy to find in the TOGAF documentation, and an example for each.

General rules and guidelines, intended to be enduring and

seldom amended, that inform and support the way in which
an organization sets about fulfilling its mission.
TOGAF describes 2 domains that inform architecture:
Enterprise and Architecture principles. It describes
characteristics and components of principles, how to develop
and apply principles, and also provides a detailed set of
example business, data, application & technology principles

24

Name

Represents the essence of the rule and easy to remember

Statement

Succinctly and unambiguously communicates the fundamental rule

Rationale

Highlights the business benefits of adhering to the principles and describes the
relationship to other principles. Describes situations where one principle would be given
precedence or carry more weight than another for making a decision.

Implication

Highlights the requirements for business and IT for carrying out the principle, in terms of
resources, costs, and activities/task. The impact to the business and consequences of adopting
a principle should be clearly stated. The reader should see How does this affect me?

STAKEHOLDER MANAGEMENT

Used to identify individuals and groups who contribute to the development

of the architecture, to identify those that gain or lose from its introduction,
and develop strategies for dealing with them
TOGAF describes an approach & steps in the process, and provides a
template stakeholder map.
Corporate Functions

CXO

PROGRAM
ENTERPRISE SECURITY MANAGEMENT
OFFICE
End-User Organization

Q/A STANDARDS
GROUPS

Project Organization

LINE MANAGEMENT

SERVICE DESK

BUSINESS PROCESS
DOMAIN EXPERTS

APPLICATION MANAGEMENT

PRODUCT SPECIALIST

INFRASTRUCTURE MANAGEMENT

TECHNICAL SPECIALIST

TECHNICAL SPECIALIST

BUSINESS
DOMAIN EXPERTS

SUPPLIERS

External

System Operations
IT SERVICE MANAGEMENT

EXECUTIVES

DATA OWNERS

HR

EXECUTIVES
LINE MANAGEMENT

27

PROCUREMENT

REGULATORY BODIES

Widely used to validate an architecture that is being developed by

highlighting shortfall between Baseline and Target Architecture - items that
are deliberately omitted, accidentally left out, or not yet defined
TOGAF describe suggested steps and an example:
VIDEO CONFERENHANCED
ENCING SERVICES TELEPHONY SERVICES

BROADCAST SERVICES
VIDEO CONFERENCING
SERVICES
ENHANCED TELEPHONY
SERVICES

MAILING LIST
SERVICES

ELIMINATED
SERVICES
INTENTIONALLY ELIMINATED

INCLUDED
POTENTIAL MATCH

SHARED SCREEN SERVICES

GAP:
GAP: TO BE DEVELENHANCES SERVICES OPED OR PRODUCED

NEW >

29 INTEROPERABILITY
REQUIREMENTS
Interoperability is the ability to
share information and services,
the degree to which information
and services are to be shared is a
useful architectural requirement,
especially in a complex
organization and/or extended
enterprise
TOGAF defines interoperability,
describes where it is determined
throughout the ADM, and explains
the tasks followed in establishing
interoperability requirements
SH

B
2

3
2

In TOGAF patterns are

considered as a way of
putting building blocks
into context; e.g. to
describe a re-usable
solution to a problem.
Building blocks are what
you use: patterns tell
you how you use them,
when, why, and what
trade-offs you have to
make in doing so

PhaseB:
Inter-stakeholder
interoperability
Requirements
(Using degrees
of information
interoperability)

UNINTENTIONALLY EXCLUDED A GAP IN TARGET ARCHITECTURE

30 INTEROPERABILITY
REQUIREMENTS

Definition

Organizational
Context
YES

There is recognition by the organization the information

is a strategic corporate asset requiring stewardship
There is also recognition that the data is not universally
understandable, of requisite quality, and accessible.
Maturity Model Levels

0
Not
defined

1
Ad
Hoc

2
Respectable

3
Defined

4
Managed

5
Oprimized

Please refer to course for definitions

SH= Stakeholders

@goodelearning

TOGAF says good scenarios are SMART,

explains their benefits, outlines the process
to create one, and describes its content. It
also shows where they are used in the ADM,
lists typical interview questions, and provides
example categories of goals and objectives.
GATHER

ANALYSE

REVIEW

1. PROBLEM
2. ENVIRONMENT
3. OBJECTIVES
4. HUMAN ACTORS
5. COMPUTER ACTORS
6. ROLES AND RESPONSIBILITIES
REFINE IF
REFINE IF
REFINE IF
NECESSARY NECESSARY NECESSARY

PROJECT SIZE
INDICATED BY
SIZE OF CIRCLE

MIGRATION PLANNING TECHNIQUES

ON TARGET

TOGAF describes a number of

techniques to support migration
planning in Phases E and F.
These include Implementation
Factor Assessment an Deduction
Matrix, Consolidated Gaps,
Solutions, and Dependencies Matrix,
Architecture Definition Increments
Table, Transition Architecture State
Evolution Table, and Business Value
Assessment Technique

PROJECT

AT RISK

PROJECT

IN TROUBLE

PROJECT

PROJECT

PROJECT

PROJECT

PROJECT

PROJECT

RISK >

TOGAF provide ways to classify and identify risk, carry out an initial risk assessment,
risk mitigation and residual risk assessment, and monitor and govern risk

Business Transformation Readiness Assessment Maturity Model

BTEP Readiness
Factor

In TOGAF scenarios are a way to derive

business requirements for architecture and
the implied technical requirements

Used to manage risk during an architecture/business transformation project

TOGAF outlines the steps required

for the assessment, including
determine, present and assess
readiness factors, readiness and
migration planning, and marketing
the implementation plan

Class

BUSINESS SCENARIOS

31 RISK MANAGEMENT

Used for identifying and

quantifying an organizations
readiness to undergo change

Factor 2: Need
for Enterprise
Information
Architecture

26

TOGAF describes the

content an terminology
of patterns, how they
relate to the Enterprise
Continuum, views and
business scenarios,
examples of their use,
and links to resources

28

GAP ANALYSIS

TARGET ARCHITECTURE >

BASELINE ARCHITECTURE

25 ARCHITECTURE
PATTERNS

VALUE >

23 ARCHITECTURE PRINCIPLES

/goodelearning

PRELIMINARY RISK
RISK ID

RISK

EFFECT

FREQUENCY

RESIDUAL RISK
IMPACT

MITIGATION

EFFECT

FREQUENCY

IMPACT

32 CAPABILITY-BASED PLANNING
Used to manage risk during an architecture/business transformation project
TOGAF provide ways to classify & identify risk, carry out an initial risk assessment, risk mitigation & residual risk assessment, and monitor & govern risk
CORPORATE STRATEGIC PLAN
BUSINESS TRANSFORMATION
GOALS AND OBJECTIVES
MANAGES & CREATES
CAPABILITY
(OUTCOME-ORIENTED)
CONSISTS OF
CAPABILITY
INCREMENT
DESIGNATES
BUILDING BLOCKS
(DELIVERABLE)

ARCHITECTURE VISION
(PHASE A)
BASIS FOR
ARCHITECTURE DEFINITION
(PHASE B, C, D)
BASIS FOR
TRANSITION ARCHITECTURE
(PHASE E, F,)
ALL DELIVER
ARCHITECTURE AND SOLUTION
BUILDING BLOCKS

/company/good-e-learning

BASIS FOR

CORPORATE PROJECT
PORTFOLIO
BROKEN
DOWN INTO
CORPORATE PROJECT
(ACROSS PORTFOLIOS)
CONSIST OF

WORK
PACKAGES
WORK
PACKAGES

CORPORATE PROJECT INCREMENTS

(ACROSS PORTFOLIOS)
DELIVER

BASIS FOR

CAPABILITY INCREMENT
SOLUTIONS

Free Resource Library

www.goodelearning.com

Good e-Learning 2015. ArchiMate, The Open Group and TOGAF are registered trademarks of the Open Group in the United States and other countries
Source: The eight fundamental factors in EA Information First, Roger & Elaine Evernden, Butterworth Heinemann, 2003