togaf roadshow

Andrew Tomsky

E.A. Consultant

TOGAF 9

Framework for Enterprise

Architecture

Introduction to TOGAF

3 – www.anywhere.cz Introduction to TOGAF

TOGAF is…

• TOGAF is an architecture framework.

– The Open Group architecture framework.

• Provides the methods and tools for

assisting in the acceptance, production, use

and maintenance of an enterprise

architecture

• TOGAF is based on:

– An iterative process model

– A re-usable set of existing architecture assets

– Supported by architectural best practices

What is enterprise architecture?

Enterprise architecture is…

System A

System CSystem B

System DSolution

Architecture

Solution

Architecture

Solution

Architecture

Enterprise Architecture

Solution

Architecture

Typical problems in Enterprise Architecture

• Multiple sources for the same data entity

• Proliferation of interfaces

• Incompatible technologies

Information System Architecture

Technology Architecture

Business Architecture

IT Architecture

Enterprise Architecture

• How the business

meets it‘s strategy

and goals

• Support of business

strategy and goals

• How the technology

fits together

Other issues in Enterprise Architecture

• Reuse

• Procurement and supplier control

• Support of business strategy

... ...

FINANCE SALES CUSTOMER SERVICE

:Database_1

:Database_2

:Database_3

:Database_5

:Database_6

:Application_1

:Application_2

:Application_3

:Application_5

:Application_6

:Database_7:Database_4

:Application_4

What should an Architectural Framework contain?

• A foundational structure, or set of

structures, which can be used for

developing a broad range of different

architectures

• It should contain a method for designing

an information system in terms of a set

of building blocks, and for showing how

the building blocks fit together

• It should contain a set of tools and

provide a common vocabulary

• It should also include a list of

recommended standards and compliant

products that can be used to implement

the building blocks

11 – www.anywhere.cz

TOGAF – history and development

The Open Group

• A vendor- and technology-neutral consortium

• Committed to the vision of boundary-less information flow

• Architecture Forum members – more than 300 organizations, from

industry, government as well as academia

• „Making Standards Work“

• IT Specialist Certification – ITSC

TOGAF – history and development

The Open Group Architecture Framework

• First version of TOGAF launched in 1995 – originally based on the US

department of defense TAFIM framework

• First version of TOGAF focused primarily on technology.

• 2002 – Enterprise Edition – TOGAF v 8

• 2009 – TOGAF 9

– Better linkage to business layer (business strategy, business models, processes)

– More user friendly framework (templates, guidelines)

– Parts of the methodology have been simplified

• TOGAF has been continuously improved for over 15 years!

Some members of the Architecture Forum

• Massachusetts Institute of

Technology, Lincoln Laboratory

• NASA SEWP

• Nissan Motor Co., Ltd.

• Nomura Research Institute, Ltd.

• PricewaterhouseCoopers LLP

• Procter & Gamble Company

• Rolls-Royce plc

• SAP

• Sun Microsystems

• Sybase® PowerDesigner®

• Tata Consultancy Services

• The Boeing Company

• Unisys

• Wipro Technologies

• American Express

• ACORD Corporation

• BP International

• British Telecom Plc

• Capgemini SA

• Cisco Systems, Inc.

• Deloitte Consulting LLP

• Deccan Global Solutions LLC

• Hewlett-Packard

• France Telecom

• HSBC Bank plc

• IBM

• IDS Scheer AG

• Infosys Technologies Ltd

• Intel Corporation

• Lockheed Martin Corporation

Development overview

The TOGAF content is divided into 7 parts:

• Part I – Introduction

• Part II - Architecture Development Method

• Part III - ADM Guidelines and Techniques

• Part IV - Architecture Content Framework

• Part V - Enterprise Continuum & Tools

• Part VI - TOGAF Reference Models

• Part VII - Architecture Capability Framework

Architecture Development Method

(Part II)

ADM Guidelines and Techniques (Part III)

Architecture Content

Framework(Part IV)

Enterprise Continuum and Tools

(Part V)

TOGAF Reference Models (Part VI)

Architecture Capability Framework (Part VIII)

Overview of the TOGAF content

Types of content in TOGAF Types of content in TOGAF

The content in the TOGAF specification is categorized as follows:

– TOGAF Core consists of the fundamental concepts that form the essence of

– TOGAF Mandated consists of the normative parts of the TOGAF

specification. These elements of TOGAF are central to its usage and without

them the framework would not be recognizably TOGAF.

– TOGAF Recommended consists of a pool of resources that are specifically

referenced in TOGAF as ways in which the TOGAF Core and Mandated

processes can be accomplished (e.g., the SEI Architecture Trade-Off Analysis

Method or business scenarios)

– TOGAF Supporting consists of additional resources that are not referenced

in the other three TOGAF categories itself but provide valuable assistance

Using TOGAF with other frameworks

• TOGAF is a generic framework and it is

expected that the architect will adapt and build

on the TOGAF to create an organization-specific

framework

• The generic TOGAF deliverables may be

replaced or extended by deliverables defined in

any other relevant framework

– E.g.: ITIL, CMMI, COBIT, PRINCE2, PMBOK, MSP etc

• TOGAF also complements other frameworks

that are aimed at specific vertical business

domains, specific horizontal technology areas

(such as security or manageability), or specific

application areas (such as e-Commerce)

Advantages of using TOGAF (IT)

• Prevents growth of IT into unmanageable complexity

• TOGAF represents best practice in architecture development.

– It has been developed through the collaborative efforts of 300

Architecture Forum member companies from some of the world’s

leading IT customers and vendors

• Using TOGAF enable companies to build quality architectures, which are:

– Consistent

– Support the needs of stakeholders

– Support current requirements and to the likely future needs of the

business

– Employ best practice

• Strong focus on removing the barriers between business and IT

• Supports optimal reuse of existing IT assets

• Enables business strategy

Architecture governanceArchitecture governance

What is architecture governance

• Architecture governance is the practice and orientation by which enterprise

architectures are managed and controlled at an enterprise-wide level

• Architecture governance typically operates within a hierarchy of other

governance structures, e.g.:

– Corporate governance

– Technology governance

– IT governance

– Architecture governance

• Domains of governance may exist at multiple geographic levels

• Effective Governance creates a controlled environment for IT across the

enterprise

Architecture Governance

What is architecture governance

• Conceptually, architecture

governance is:

– A series of processes

– A set of owned responsibilities

– An approach

– A cultural orientation

• These things are defined by the

governance framework

Establishing an Architecture Capability

• It is increasingly recognized that a

successful enterprise architecture

practice must sit on a firm

operational footing

• Effective governance requires

that all architecturally significant

activity is controlled and aligned

within a single framework

• In effect, an enterprise

architecture practice should be

run like any other operational

unit (e.g. a Project Management

Office)

Architecture Governance — Organization Structure

Architecture Governance Framework —Conceptual Structure

25 – www.anywhere.cz Architecture Governance

A mature Architecture Capability

Architecture Governance — Key Success Factors

• For successful Architecture Governance, the following things should be

considered:

• Organizational responsibilities and structures which support the

architecture governance processes and reporting requirements

• Governance processes, procedures, roles, skills, and tools

• Best practices for architecture policies

– For their submission, adoption, reporting, and retirement

• Criteria for the control of the architecture governance processes,

dispensations, compliance assessments, SLAs, and OLAs

• Requirements for the effectiveness of all architecture governance-related

activities

The benefits of Architecture Governance

• Greater shareholder value → studies have demonstrated a correlation

between increased shareholder value and well-governed enterprises

• Upholds a standard of consistency, quality and interoperability in

architecture

– Prevents growth of architecture into unmanageable complexity

• Supports strategic, long-term evolution of architecture

• Increased transparency of accountability

• Proactive control, monitoring, and management mechanisms

• Integrates with existing processes and methodologies and complements

functionality by adding control capabilities

The Architecture Development The Architecture Development Method (ADM)Method (ADM)

29 – www.anywhere.cz The Architecture Development Method

The architecture domains used by TOGAF

• Business Architecture

– Defines the business strategy, governance, organization, and key business

processes

• Data Architecture

– Describes the structure of an organization’s logical and physical data assets and

data management resources

• Application Architecture

– A blueprint for the individual application systems to be deployed, their

interactions, and their relationships to the core business processes of the

organization

• Technology Architecture

– Describes the logical software and hardware capabilities that are required to

support the deployment of business, data, and application services

– Includes IT infrastructure, middleware, networks, communications, processing,

standards, etc

Overview of the ADM

• The ADM consists of 9 phases:

– The 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

– And Requirements Management

• Each phase contains a series of steps

The Architecture Development Method

The Preliminary Phase

• Describes the preparation and initiation

activities to prepare to meet the business

directive for a new enterprise

architecture

– Includes the definition of an

Organization-Specific Architecture

framework

– Includes the definition of principles

Phase A: Architecture Vision

• Phase A is the initial phase of an

architecture development cycle

• It includes:

– Defining the scope

– Identifying the stakeholders

– Creating the Architecture Vision

– Obtaining approvals

Phase B: Business Architecture

• Phase B: Business Architecture

describes the development of a

Business Architecture to support an

agreed Architecture Vision

Phase C: Information Systems

• Phase C: Information Systems

Architectures describes the development

of Information Systems Architectures for

an architecture project, including the

development of Data and Application

Architectures

Phase D: Technology Architecture

• Phase D: Technology Architecture

describes the development of the

Technology Architecture for an

architecture project

Phase E: Opportunities & Solutions

• Phase E describes initial

implementation planning

– Includes the identification of delivery

vehicles for the architecture defined

in the previous phases

Phase F: Migration Planning

• Phase F addresses the formulation of a

set of detailed sequence of transition

architectures with a supporting

Implementation and Migration Plan

Phase G: Implementation Governance

• Phase G provides an architectural

oversight of the implementation

Phase H: Architecture Change

• Phase H: Architecture Change

Management establishes procedures for

managing change to the new architecture

Requirements Management

• Requirements Management examines

the process of managing architecture

requirements throughout the ADM

Overview of the ADM

• The ADM is a generic method: It can be used by enterprises in a wide

variety of different geographies, applied in different vertical

sectors/industry types and can be tailored to specific needs

• The ADM is iterative: Over the whole process, between phases, and

within phases

• For each iteration of the ADM, a fresh decision must be taken as to:

– The breadth of coverage of the enterprise to be defined

– The level of detail to be defined

– The extent of the time period aimed at

– The architectural assets to be leveraged, including:

� Assets created in previous iterations of the ADM cycle within the enterprise

� Assets available elsewhere in the industry (other frameworks, systems

models, vertical industry models, etc.)

Adapting the ADM

• To take account of the maturity of the

architecture discipline within the

organization

– e.g. by putting more emphasis on phases

that were formerly not well understood

by the organization

• The business and/or architecture

principles of an enterprise may require

that the ADM is adapted

• To integrate the ADM with another

enterprise framework or other firm

standards

– e.g. the Zachman Framework

– e.g. program management, business

planning or procurement

Advantages of the ADM as a method

• Strong focus on eliminating the barriers between Business and IT

• Ensures a high level of consistency and control

– Through reuse of architectures, use of principles etc

– Formal post-implementation feedback and control is part of the method

• Supports strategic, long-term architecture planning

– Planning techniques, architecture governance after implementation etc

• A realistic method

– Covers all the key domains, but does not force the architect to make views that

are not necessary for anyone

• Highly flexible and can be adapted:

– For companies of any size, for architecture projects to any level of detail

Supporting the architectSupporting the architect

The Architecture Repository

• The Architecture Repository provides a framework and context to support

the leverage of relevant architecture assets in executing the ADM

– One part of the Architecture Repository is the Enterprise Continuum, which is a

tool for categorizing architectural source material

– At relevant places throughout the ADM, there are reminders as to which assets

from the repository can be used

– e.g. Foundation Architecture in Phase D: Technical Architecture

• In executing the ADM, the architect also populates the organization’s own

Architecture Repository

• The criteria for including source materials in an organization’s

Architecture Repository will typically form part of the enterprise

architecture governance process

Supporting the architect

Architecture repository

• An environment used to store

architectural output created

in the ADM

– Helps architects leverage

relevant resources and assets

for developing Architecture

Enterprise continuum

• A view of the

Architecture

Repository that

provides methods for

classifying

architectures and

solution artifacts in a

structured way

Enterprise continuum

TRM – Detailed level

• Entities:

– Application Software

– Application Platform

• Communications Infrastructure

– Interfaces:

– Application Platform Interface

– Communications Infrastructure

Interface

TOGAF Metamodel Entities

• Defines a set of entities

that allow architectural

concepts to be captured,

stored, filtered, queried,

and represented in a way

that supports consistency,

completeness, and

traceability

Metamodel Relationships

TOGAF supporting materials

Skills framework

• TOGAF provides a skills framework which details the skills needed by the roles

in the architecture team

Skills framework

• Types of skill categories used in the TOGAF skills framework:

– Generic Skills: typically comprising leadership, team working, inter-personal

skills, etc

– Business Skills & Methods: typically comprising business cases, business

process, strategic planning, etc

– Enterprise Architecture Skills: typically comprising modeling, building block

design, applications and role design, systems integration, etc

– Program or Project Management Skills: typically comprising managing business

change, project management methods and tools, etc

– IT General Knowledge Skills: typically comprising brokering applications, asset

management, migration planning, SLAs, etc

– Technical IT Skills: typically comprising software engineering, security, data

interchange, data management, etc

– Legal Environment: typically comprising data protection laws, contract law,

procurement law, fraud, etc

Developer-Led SOA

• Developer-led SOA considers an information system service to be a unit of

application code providing an open interface that is abstracted from its

implementation

Developer-led SOA

Asks:”What is the best way to

design, build and operate services?

Business-Led SOA

Ask:”What services are

needed and how should

they be governed and

fulfilled?

How TOGAF Supports SOA

• TOGAF provides in an SOA context is a set of tools and techniques to link

top-down business-led SOA to bottom-up developer-led SOA in a robust

and maintainable way that addresses many of the nontechnical challenges

TOGAF Guidelines and Techniques

They are detailed in part III of the TOGAF documentation:

• Applying Iteration to the ADM

– Discusses the concept of iteration and shows potential strategies for applying

iterative concepts to the ADM

• Applying the ADM at Different Enterprise Levels

– Discusses the different types of architecture engagement that may occur at

different levels of the enterprise. This section then also discusses how the ADM

process can be focused to support different types of engagement

• Security Architecture and the ADM

– Provides an overview of specific security considerations that should be

considered during different phases of the ADM

• Using TOGAF to Define & Govern SOAs

– Shows how SOA concepts can be supported by the TOGAF framework

• Architecture Principles

– Principles for the use and deployment of IT resources across the enterprise —

describes how to develop the set of general rules and guidelines for the

architecture being developed

• Stakeholder Management

– Describes Stakeholder Management, an important discipline that successful

architecture practitioners can use to win support for their projects

• Architecture Patterns

• Business Scenarios

– A method for deriving business requirements for architecture and the implied

technical requirements

• Gap Analysis

– A technique used in the TOGAF ADM to validate an architecture that is being

developed

• Migration Planning Techniques

– Describes a number of techniques to support migration planning in Phases E

• Interoperability Requirements

– A technique for determining interoperability requirements

• Business Transformation Readiness Assessment

– A technique for identifying business transformation issues

• Risk Management describes

– A technique for managing risk during an architecture/business transformation

project

• Capability-Based Planning

• Tool selection

TOGAF Certification

• Ensures that individuals are

knowledgeable about TOGAF

• Is a common baseline of

knowledge

• Provides a visible trust mark

• Is a foundation for the emerging

profession

The TOGAF Certification for People Program

Certification

LEVEL TAG PURPOSE

1 TOGAF 9

Foundation

To provide validation that the candidate has

gained knowledge of the terminology and basic

concepts of TOGAF 9 and understands the core

principles of Enterprise Architecture and

2 TOGAF 9

Certified

To provide validation that in addition to

knowledge and comprehension, the candidate

is able to analyze and apply knowledge of

The TOGAF Certification for People Program

We are…. Anywhere

• Provide consultancy services and training linked to Enterprise Architecture

• The first Czech company to provide accredited training in TOGAF

• Members of the Open Group

www.anywhere.cz

Andrew.tomsky@anywhere.cz

togaf roadshow

essence of togaf togaf

enterprise architecture

version of togaf

togaf history

togaf core

togaf specification

elements of togaf

enterprise edition togaf

Education

ea frameworks &togaf

togaf 9 study guide...

togaf ebook

developping a semantic mapping between togaf and...

togaf® 9 foundation study guide 3rd edition - van haren...

plantilla togaf principles

3.togaf (uploaded)

togaf artifacts for business capabilities togaf artifacts...

module 7 togaf content metamodel - togaf® information site...

sabsa-togaf integration

togaf version 9_a_pocket_guide_zzz

togaf project

avancier’s togaf quick reference charts quick...

foundation slides - togaf

togaf simplified - part 7 - architecture capability...

togaf certified e2

togaf 10 intro

togaf course

identity management - togaf

togaf 9 introduction