Introduction to Enterprise

Architecture Framework
And
TOGAF
Konakanchi Srinivasa Rao

Agenda

What is an Enterprise
What is an Architecture
What is Enterprise Architecture
Why Enterprise Architecture
What is an Architecture Framework
Top Architecture Frameworks
TOGAF..
.

What is an Enterprise?
A collection of organizations that share a common set of
goals
Government agency
Part of a corporation
Corporation
Large corporations may comprise multiple enterprises
extended enterprise including partners, suppliers and
customers

Example for Enterprise:

P&G

P&G Global Brands

What is an Architecture?
An Architecture is the fundamental organization of
something, embodied in:
its components,
their relationships to each other and the environment its
design and evolution.

What is Enterprise
Architecture?

The organizing logic for business processes and IT

infrastructure reflecting the integration and standardization
requirements of the firms operating model
A conceptual blueprint that defines the structure and
operation of an organization.
The intent of an enterprise architecture is to determine
how an organization can most effectively achieve its
current and future

Example for Enterprise Architecture

The analysis and

documentation of an enterprise in its
current and future states from a strategy,
business, and technology perspective.

T e c h n o lo g y B u s in e s s S tr a te g y

Enterprise Architecture:

S e c u rity / S ta n d a r d s / W o rk fo rc e

N e tL wi n eo s r ok f B u s i n e s s
INn ef rt wa so t r ku c t u r e
I n f r a s t r u c t uG r eo a l s &
I n Ni tei at wt iov rek s
NI n ef rt wa so t rr ku c t u r e
I n fPr ar so t dr uu c ct ut sr e &
S Ne er vt wi co er ks
N I en tf wr aos rtkr u c t u r e
I n f r a s t r uD c at ut ar e &
I n f o rNme tawt ioor nk
N I en tf wr aos rtkr u c t u r e
I n f rSa ys st r tuec mt u sr e &
A p p l i Nc ae tt wi o onr ks
N I en tf wr aos rtkr u c t u r e
I n Nf r ae st wt r uo cr tku sr e &

In fr a s t r u c t u r e

CURRENT
A R C H IT E C T U R E

L i n e s No ef Bt wu s oi n re ks s

INn ef rtaw s ot rr uk c t u r e
C
O
M
P
O
N
E
N
T
S

U p d Iant ef rda Ss t r au t ce tg ui cr e
G o a l s & I n i t i a t iNv ee st w o r k

INn ef rtaw s ot rr uk c t u r e

A r c h ite c tu re
M anagem ent &
T r a n s itio n P la n

I m p r o v e d I nB fur sa isn ter su s c t u r e

P r o d u c t s a n d S e r vNi ce et sw o r k

NI ne ftrwa so tr rku c t u r e

E n h a n c e dI nD f ar at as at rn ud c t u r e
I n f o r m a t i o n F l o wN se t w o r k

NI ne ftrwa so tr rku c t u r e

I n t e g r a t e dI nS f yr as tse tmr us c t u r e
a n d A p p l i c a t i o nN se t w o r k

NI ne ftrwa so tr rku c t u r e

O p t i m i z e dI nN f er at ws ot r uk sc t u r e
a n d In fr a s tr u c tu r e

FUTURE
A R C H IT E C T U R E

C
O
M
P
O
N
E
N
T
S

AS-IS

Strategi
c

TO-BE Architecture

New Direction & Goals

(Leadership Team)

Operating
Scenarios

New Business Priorities

(Management Team)
Tactical

Capabilities
of the
Current
Enterprise

to

Emerging Technologies
(IT Support Team)

Program
Plans

Capabilities
of the
Future
Enterprise

Why Enterprise Architecture?

Effective management and exploitation of information
through IT is key to business success
Good information management = competitive advantage
Current IT systems do not really meet the needs of
business
Broken, duplicated
Poorly understood
Not responsive to change

Investment in Information Technology

Focussed on system maintenance
Tactical developments rather than a strategic plan

What is an Architecture
Framework?

A conceptual structure used to develop, implement and

sustain an Enterprise Architecture

It should describe a method for designing target state of the

Enterprise 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

Top Architecture Frameworks

The Zachman Framework

The Open Group Architecture Framework(TOGAF)

Federal Enterprise Architecture(FEA)

Gartner

Every enterprise has an IT

architecture

Some
are designed
and some
just happen

A good IT architecture will:

Directly address the needs of the enterprise

React to change at the rate dictated by the
enterprises markets
Be understood and supported by senior
management
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

Do you have a plan?

Can
Canaabusiness
businesssucceed
succeedwithout
without
aadocumented
documented business
business plan?
plan?
Can
CanI.T.
I.T.succeed
succeedwithout
without aadocumented
documentedarchitecture?
architecture?

Greater ability to respond to new demands

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

But where do you start?

There are many successful IT architectures
in use
Can you benefit from that accumulation of
knowledge?
Can you examine in detail the IT
architecture of another organization?
Do you have to reinvent the wheel?
What reference material is available?
The TOGAF is going to answers for all
your questions.

TOGAF Origins and

Motivations
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

TOGAF Momentum

More than 100,000 downloads

Over 16,000 certified practitioners
More than 220 corporate members of The Open Group
Architecture Forum
Over 55,000 TOGAF series books shipped
Association of Enterprise Architects membership at more
that 20,000

TOGAF Today

Industry consensus

Technology- and tool-neutral

8 years continuous development

Proven in practice

Publicly available

TOGAF Development History

1994: Requirement
Proof of Need
1995: TOGAF Version 1
Proof of Concept
1996: TOGAF Version 2
Proof of Application
1997: TOGAF Version 3
Relevance to practical architectures (Building Blocks)
1998: TOGAF Version 4
TOGAF in Context - the Enterprise Continuum
1999: TOGAF Version 5
Business Scenarios - architecture requirements
2000: TOGAF Version 6
Architecture views / IEEE 1471
US DoD work (C4ISR Framework, C2STA)
2001: TOGAF Version 7
2003: TOGAF Version 8
2009: TOGAF Version 9
2011: TOGAF Version 9.1

TOGAF 9.1

TOGAF 9.1 was released in December 2011

It is the first maintenance update to TOGAF 9
It is an upwards-compatible evolution from TOGAF 9,
addressing usage feedback and comments raised
It addresses over 400 comments received
Contains over 450 changes

The TOGAF 9.1-Body knowledge

The Architecture Development

Method

ADM Iterative view

TOGAF Structure and

Components

Architecture Development Method

Target
Foundation Architecture
Architectures
Resource Base
Architecture Development Method

TOGAF
Foundation
Architecture

Technical
Reference
Model

Standards
Information
Base

Building
Blocks
Information
Base

(services
taxonomy)

(standards)

(architecture
building blocks
- future)

Resource Base

The Architecture Continuum

Overview of TOGAF exam

Q&A

Thanks