The Open Group Architecture Framework

(TOGAF) Version 7

Agenda

q Business Drivers for Good IT Architectureq Background to TOGAFq New in TOGAF Version 7q Looking Aheadq Summary

Every enterprise has an IT architecture

Some

are designed

and some

just happen

A good IT architecture will:

q Directly address the needs of the enterpriseq React to change at the rate dictated by the enterprise’s

marketsq Be understood and supported by senior managementq Clearly define the structure of the existing systemq Provide a roadmap and migration strategy for future

purchases / developmentsq Reduce the number and complexity of the interfaces

between components, improving the ease of:§ Application portability§ Component upgrade§ Component exchange§ Component development and maintenance

Do you have a plan?

q Greater ability to respond to new demandsq Greater business value from IT operationsq Greater ability to introduce new technologyq Faster, simpler and cheaper procurementq Faster time-to-market

Can a business succeed withouta documented business plan?

Can a business succeed withouta documented business plan?

Can I.T. succeed without a documented architecture?Can I.T. succeed without a documented architecture?

But where do you start?

q There are many successful IT architectures in use

q Can you benefit from that accumulation of knowledge?

q Can you examine in detail the IT architecture of another organization?

q Do you have to reinvent the wheel?q What reference material is available?

This is why TOGAF exists and is freely available.

TOGAF Origins and Motivations

q A customer initiative:§ Formal user requirement developed 1994§ 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

q Industry consensus

q Technology- and tool-neutral

q 8 years continuous development

q Proven in practice

q Publicly available:

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

TOGAF Today

TOGAF Structure and Components

Building Blocks

Information Base

(architecture building blocks

- future)

Standards Information

Base

(standards)

Technical Reference

Model

(services taxonomy)

Architecture Development Method

Resource Base

Target Architectures

TOGAF FoundationArchitecture

q Architecture Development Method

q Foundation Architecture

q Resource Base

Architecture Development Method (ADM)

q Open, industry consensus method for IT architecture

q Quick-start foundation

q Practical, experience based guidance

q Requires continual validation against requirements

q Associated with detailed taxonomy of services§ defines scope of

each service category

q Identifies system-wide capabilities (“qualities”), e.g.:§ Internationalization§ Security§ Management

Foundation Architecture:Technical Reference Model (TRM)

Qualities

Qualities

Network Services

Operating System Services

Data M

anag

emen

t

Lo

cation

& D

irectory

InfrastructureApplications

BusinessApplications

Data In

terchan

ge

Intern

ation

al Op

eration

s

User In

terface

Tran

saction

Pro

cessing

System

& N

etwo

rk Man

agem

ent

Secu

rity

So

ftware E

ng

ineerin

g

Grap

hics &

Imag

e

Communication Infrastructure

Application Programming Interface

Communications Infrastructure Interface

Qu

alit

ies Q

ualities

Foundation Architecture:Standards Information Base (SIB)

q A database of open industry standards§ The complete set of Open Group endorsed

standards§ Content determined by Open Group consensus

processq Structured according to TOGAF Technical Reference

Model taxonomyq Regularly updatedq Available for public web access§ http://www.db.opengroup.org/sib.htm

q Gateway to many linked resources

Resource Base

q Resources available in applying the TOGAF Architecture Development Method; e.g.§ ADML§ Architecture Compliance Reviews§ Architecture Principles§ Architecture Views§ Business Scenarios (requirements method)§ Case Studies§ IT Governance Strategies

TOGAF Development History

q 1994: Requirement§ Proof of Need

q 1995: TOGAF Version 1§ Proof of Concept

q 1996: TOGAF Version 2§ Proof of Application

q 1997: TOGAF Version 3§ Relevance to practical architectures (Building Blocks)

q 1998: TOGAF Version 4§ TOGAF in Context - the Enterprise Continuum

q 1999: TOGAF Version 5§ Business Scenarios - architecture requirements

q 2000: TOGAF Version 6§ Architecture views / IEEE 1471 § US DoD work (C4ISR Framework, C2STA)

q 2001: TOGAF Version 7

New in TOGAF Version 7

q ANSI/IEEE Std 1471-2000, Recommended Practice for Architectural Description§ Extensive rewrite of Architecture Views section,

integrating ANSI/IEEE Std 1471 concepts / terminology§ Integration with TOGAF Architecture Development

Method.q Architecture Compliance Reviews§ Ensuring conformance with architecture in projects -

new section based on Boeing workq Architecture Patterns§ new section based on IBM, US Treasury work§ Distinguish from design patterns

TOGAF Version 7 (continued)

q Architecture Principles§ new section base on US Air Force work

q Business Executive's Guide to IT Architecture§ update

q Business Scenarios§ additional material based on Open Group CIO work§ elevation in document hierarchy

q Model based representations of TOGAF Architecture Development Method and deliverables § joint effort of Computas and Frietuna§ using METIS tool

TOGAF Version 7 (continued)

q Tailoring the TOGAF Architecture Development Method§ new guidelines

q TOGAF comparison of with other frameworks:§ Federal Enterprise Architecture Framework (FEAF)§ Federal Enterprise Architecture Guidance§ Treasury Enterprise Architecture Framework (TEAF)§ Spewak Enterprise Architecture Planning (EAP)§ Zachman Framework

q TOGAF in the Enterprise§ TOGAF positioning relative to enterprise architecture

The Open Group Architecture Forumq The forum in which TOGAF is evolvedq A worldwide forum for: customers, tool

vendors, solution vendors, integrators, academic & research organizations involved with architecture

q Exchanging information, experience, and requirements

q Access to current work in progressq Shaping the market for architecture

methods, tools and services

Looking Ahead…

q Potential 2002 projects:§ Architect certification§ TOGAF migration from infrastructure to

enterprise framework§ Tools support

Summary

q 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

q Participate in the Architecture Forum§ Worldwide forum for customers, tools vendors, solution

vendors, integrators, academic & research organizations§ Dialog with peers and industry experts§ Practical information and experience§ Access to work in progress§ Vendor, technology, product neutral

For More Information . . .

q Architecture Portal:§ http://www.opengroup.org/architecture/index.htm

q TOGAF Documentation:§ http://www.opengroup.org/public/arch

q TOGAF Information:§ http://www.opengroup.org/public/togaf

q Standards Information Base (SIB):§ http://www.db.opengroup.org/sib.htm