The Open Group Architecture

Framework
(TOGAF)

What is Architecture

A structure of systems

Provides guidance to design of system

Enterprise Architecture

Architecture at Enterprise level

Enterprise Architecture

Data Architecture
Process Architecture
Product Architecture
Application Architecture
Technology Architecture

Enterprise Architecture

Benefits of Good Enterprise Architecture

Directly address the needs of the enterprise

React to change at the rate dictated by the
enterprises markets
Clearly define the structure of the existing system
Provide a roadmap and migration strategy for
future purchases / developments
Reduce the number and complexity of the
interfaces between components, improving the ease
of:

Application portability
Component upgrade
Component exchange
Component development and maintenance

What is an Architectural Framework?

An architectural framework is a tool for:

Designing a broad range of a architectures

Assisting the evaluation of different architectures
Selecting and building the right architecture for an
organization

It embodies best practice and acknowledged

wisdom
It presents a set of services, standards, design
concepts, components and configurations

Architectural Framework- Benefits

Use of a framework leads to:

The use of common principles, assumptions

and terminology
The development of information systems with
better integration and interoperability
especially with respect to issues that affect the
whole enterprise

The position of IT Architects

How do I know
what I want,
when I dont
know what you
can do for me

We know
solutions to every
problem? Whats
your problem?

Ar IT
chitect

TOGAF

Main themes:

A single, unifying Architectural
Framework for the IT industry

A framework for developing
architectures to meet specific
business needs

not a one-size-fits-all architecture

Aligning IT Architecture with

Enterprise goals

TOGAF Today

Industry consensus

Technology- and tool-neutral

Continuous development

Proven in practice

Publicly available:
http://www.opengroup.org/public/arch

Forum Membership

Architecting the Enterprise (UK)

BMC Software Inc. (US)
Boeing Corporation (US)
Booz Allen & Hamilton (US)
Brandeis University (US)
CC and C Solutions ((Aus)
Centre For Open Systems (Aus)
ChiSurf (Hong Kong)
Computacenter (UK)
Computas (Nor)
Computer Associates (US)
Conclusive Logic (US)
Department of Defense / DISA (US)
Department of Works and Pensions (UK)
Desktop Management Task Force (US)
Fujitsu (Japan)

Frietuna Consultants (UK)

Hewlett-Packard (US)
Hitachi (Japan)
IBM (US)
Innenministerium NordRhein-Westfalen (Ger)
Jet Propulsion Labs (US)
Lockheed Martin (US)
MEGA International (Fr)
Ministry of Defence (UK)
Mitre Corporation (US)
Monash University (Australia)
Motorola (US)
NASA Goddard Space Flight Center (US)
National Computerization Agency (Korea)
NATO C3 Agency (Bel)
NEC (Japan)

Forum Membership

NEMMCO (Australia)
NeTraverse, Inc. (US)
Nexor, Inc. (US)
Open GIS Consortium, Inc. (US)
PASS Network Consulting (Ger)
Popkin Software and Systems, Inc. (UK)
POSC (US)
Predictive Systems AG (Ger)
Primeur (Italy)
ReGIS (Japan)
QA Consulting (UK)
SCO (US)
Sun Microsystems (US)
Teamcall (Bel)
The Terasoft Group (US)
Tivoli (US)

Toyota InfoTechnology Center (Japan)

TRON Association (Japan)
University of Plymouth (UK)
University of Reading (UK)
US Army Weapon Systems Technical Working
Group (WSTAWG) (US)
Veriserve Corporation (US)
Visa International (US)
Weblayers, Inc (US)
Westpac Banking Corporation (Australia)

57

Desired benefits of TOGAF?

Architected business information systems

will provide:

A greater ability to respond to new demands

A greater business value to the organization
A greater ability to use new technology
A faster, simpler and cheaper procurement
process
The ability to support a faster time-to-market

The story so far

The direction of TOGAFs evolution has been driven

by The Open Groups membership over a period of
8 years
An annual publication cycle

1994: Requirement statement developed

1995: X/Open Architectural Framework - version 1

Proof of concept

1996: TOGAF - version 2

Proof of need

Proof of application

1997: TOGAF - version 3

Relevance to practical architectures

The story so far

1998: TOGAF - version 4

1999: TOGAF - version 5

TOGAF in context - the Enterprise Continuum

Web structured documentation - ease of use
Re-organized around extended ADM
Business scenarios to help define requirements
Addition of ADML

2000: TOGAF - version 6

Integration of Building Block work

Integration of other initiatives, US DoD, IEEE 1471, IEEE
1003.23

Current situation

2001: TOGAF - version 7 (Technical Edition)

New sections on Architecture Patterns, Architecture Principles,

Architecture Compliance Reviews
Significant additional material on Business Scenarios
Comparisons of TOGAF with other frameworks
Further integration of IEEE Std 1471-2000 into TOGAF
Metis model of the TOGAF ADM
Positioning of TOGAF relative to enterprise architecture

2002: TOGAF - version 8 (Enterprise Edition)

2009: TOGAF- version 9
2012: TOGAF version 9.1

TOGAF consists of

An Architecture Development Method

(ADM)
Foundation Architecture

A Technical Reference Model (TRM)

A Standards Information Base (SIB)
Building Blocks Information Base (BBIB)

More about TOGAF

Foundation
Architecture

Target Architectures
Architecture Development Method

Technical
Reference
Model
(services)

Standards
Information
Base
(standards)

Business Requirements

Building
Block
Information
Base (future)

Architecture Management by TOGAF

TOGAF Manages

Business Architecture
Data/Information Architecture
Applications Architecture
Technologies Architecture

How to go about it ?

Start with a foundation architecture

Follow the phases of the ADM

Results in

an organization-specific architecture

more reusable building block assets in the Enterprise
Continuum

Each iteration becomes easier and has more reusable
building blocks to use

Architecture
Development Method

G
Architecture
Change
Management

G
Implementation
Governance

F
Migration
Planning

A
Architecture
Vision

Requirements
Management

E
Opportunites
& Solutions
21

of 49
Preliminary
Framework &
Principles

B
Business
Architecture

CC
Information
Information
System
System
Architectures
Architectures

D
Technology
Architecture

ADM Continued..

Preliminary

Define framework and detailed methods

confirm governance framework,
select supporting tools and infrastructure
define architecture principles.

Architecture vision

Ensure project has support,

Define scope,
define relevant stakeholders and their
concerns
Articulate architecture vision, create a plan.

22

ADM Continued..

Business Architecture :

Describe baseline business architecture

( AS- IS architecture),
A target business architecture
(to be architecture)
Analyze the gaps.

23

ADM Continued..

Information Systems Architecture

Define application system architecture

Two components : System (Application) &

Data

(to process data and support business)

[System/ Role matrix] and [System/ Function

matrix ]
data architecture [Data entity / Business
function matrix ], [system / data entities
matrix]

Technology Architecture

[Technology / System matrix]

24

Technical Reference Model

Infrastructure Applications

Business Application

Application Program Interface

Application Platform

Communications Infrastructure Interface

Communication Infrastructure

Services and Qualities

Service Qualities

Graphics & Image

Data Management

Communication Infrastructure

Data Interchange

CII

International Operations

Network Services

User Interface

Operating System Services

Location & Directory

Transaction Processing
Sys & Net Management
Security

Application Platform
Services

Software Engineering

API

Business Application
Infrastructure Applications

Standards Information Base (SIB)

A complete and up to date database of open

industry standards with links to conformant
products
Can be used to:

Define particular services

Define properties of components
Be the basis of procurement procedures

Keeps the architecture up to date with the latest IT

industry consensus
Standards Information Base publicly available

At http://www.opengroup.org/sib
With user guide
Search or full listing

Benefits of TOGAF to the architect

Avoids regular reinvention of the wheel

Provides a corporate memory of previous
successes and failures
Ensures completeness of the design process
Provides access to accumulated best practice
wisdom
Avoids communication difficulties within the team
The professional approach

Summary

Vendor-Neutral
TOGAF is available under a free perpetual license for
use within your own organization
Comprehensive process - from business requirements to
applications to infrastructure
Cuts up-front costs - avoids re-inventing the wheel
(reusability)
Refined and honed checklists at all levels - from
business requirements to physical components

Continued..

Adopt and use TOGAF

Improved ability to respond to new business demands

Improved ability to introduce new technology
Greater business value from IT operations
Faster, simpler, cheaper procurement
Faster time-to-market

Reference

The Open Group