Good e-Learning Resources : : www.goodelearning.com/downloads

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 countriesSource: The eight fundamental factors in EA – “Information First”, Roger & Elaine Evernden, Butterworth Heinemann, 2003

@goodelearning /goodelearning /company/good-e-learning

TOGAF® Poster Series #51

by Roger Evernden

TOGAF Techniques

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. We’ve included the Chapter number for each Technique to make it easy to find in the TOGAF documentation, and an example for each.

STAKEHOLDER MANAGEMENTUsed 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.

24

Q/A STANDARDS GROUPS

PROGRAM MANAGEMENT OFFICE HR

SUPPLIERS REGULATORY BODIES

ENTERPRISE SECURITY

EXECUTIVES

LINE MANAGEMENT

EXECUTIVES

SERVICE DESK

DATA OWNERSPRODUCT SPECIALIST INFRASTRUCTURE MANAGEMENT

TECHNICAL SPECIALIST TECHNICAL SPECIALIST

LINE MANAGEMENT

IT SERVICE MANAGEMENT

BUSINESS DOMAIN EXPERTS

BUSINESS PROCESS DOMAIN EXPERTS APPLICATION MANAGEMENT

PROCUREMENT

CXOCorporate Functions

External

End-User Organization Project Organization System Operations

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

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

25 ARCHITECTURE PATTERNS

ARCHITECTURE PRINCIPLESGeneral 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

23 Name Represents the essence of the rule and easy to rememberStatement Succinctly and unambiguously communicates the fundamental ruleRationale 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?”

RISK MANAGEMENT

Used to manage risk during an architecture/business transformation project

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

RISK ID RISK

PRELIMINARY RISK

MITIGATION

RESIDUAL RISK

EFFECT FREQUENCY IMPACT EFFECT FREQUENCY IMPACT

31

GAP ANALYSISWidely 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:

TARGET ARCHITECTURE > BASELINE ARCHITECTURE

VIDEO CONFER-ENCING SERVICES

ENHANCED TELEPHONY SERVICES

MAILING LIST SERVICES

ELIMINATED SERVICES

BROADCAST SERVICES INTENTIONALLY ELIMINATEDVIDEO CONFERENCING

SERVICES INCLUDED

ENHANCED TELEPHONY SERVICES POTENTIAL MATCH

SHARED SCREEN SERVICES UNINTENTIONALLY EXCLUDED - A GAP IN TARGET ARCHITECTURE

NEW > GAP: ENHANCES SERVICES

GAP: TO BE DEVEL-OPED OR PRODUCED

27 MIGRATION PLANNING TECHNIQUES 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

28

PROJECTE

PROJECTD

PROJECTB

PROJECTH

PROJECTG

PROJECTC

PROJECTF

PROJECTA

RISK >

ON TARGET

AT RISKIN TROUBLE

PROJECT SIZE INDICATED BY SIZE OF CIRCLE

VALU

E >

BUSINESS SCENARIOSIn TOGAF scenarios are a way to derive business requirements for architecture and the implied technical requirements

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.

26

1. PROBLEM

3. OBJECTIVES

5. COMPUTER ACTORS

2. ENVIRONMENT

4. HUMAN ACTORS

6. ROLES AND RESPONSIBILITIES

GATHER ANALYSE REVIEW

REFINE IF NECESSARY

REFINE IF NECESSARY

REFINE IF NECESSARY

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

29

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

SH A B C D E F G

A 2 3 2 3 3 3

B 2 3 2 3 2 2

C 3 3 2 2 2 3

D 2 2 2 3 3 3

E 4 4 2 3 3 3

F 4 4 2 3 3 2

G 2 2 3 3 3 3

SH= Stakeholders

CAPABILITY-BASED PLANNINGUsed to manage risk during an architecture/business transformation project

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

32

CAPABILITY(OUTCOME-ORIENTED)

CAPABILITYINCREMENT

BUILDING BLOCKS(DELIVERABLE)

CORPORATE STRATEGIC PLANBUSINESS TRANSFORMATION

GOALS AND OBJECTIVESARCHITECTURE VISION

(PHASE A)CORPORATE PROJECT

PORTFOLIO

ARCHITECTURE DEFINITION(PHASE B, C, D)

CORPORATE PROJECT(ACROSS PORTFOLIOS)

MANAGES & CREATES

BASIS FOR

BASIS FOR BROKEN DOWN INTO

BASIS FOR CONSIST OF

ALL DELIVER DELIVERBASIS FOR

WORK PACKAGES

WORK PACKAGES

CONSISTS OF

DESIGNATES

TRANSITION ARCHITECTURE(PHASE E, F,)

CORPORATE PROJECT INCREMENTS(ACROSS PORTFOLIOS)

ARCHITECTURE AND SOLUTION BUILDING BLOCKS

CAPABILITY INCREMENT SOLUTIONS

INTEROPERABILITY REQUIREMENTS

Used for identifying and quantifying an organization’s readiness to undergo change

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

30

Business Transformation Readiness Assessment - Maturity Model

Factor 2: Need for Enterprise Information Architecture

Class Organizational Context

BTEP Readiness Factor YES

Defini-tion

There is recognition by the organization the information is a strategic corporate asset requiring stewardshipThere 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 Respect-

able

3 Defined

4 Man-aged

5 Oprim-

ized

Please refer to course for definitions