Professional Documents
Culture Documents
University of Jyvskyl
23rd Aug. 2007
Ari Hirvonen
2006-03-23
Page 1
Agenda
Why EA
What is EA
EA frameworks and methodologies
2006-03-23
Page 2
Page 3
2006-03-23
Page 4
Why EA?
2006-03-23
Page 5
The internet
And WWW
(late 90s to
present)
Regulated
free market
(mid 80s to
Organization
late 90s)
Distributed
Systems
(late 70s to
Organization
mid 80s)
Isolated
Machines
(late 50s to
eraly 60s)
Mainframe
Monolopoly
(eraly 60s to
late 70s)
Organization
Next: BPM/Business
orientation ,
Agile computing,
Multiple channels
IT
IT
Organization
IT
IT
IT
IT
Strategic
Information
Systems: 1980s-
IT
IT
Organization
Management
Information
Systems: 1970s-
IT
IT
Data
Prosessing
Systems: 1960s-
Time
Page 6
Adding new:
1. Banking,
2.E-business and
3.General Insurance =
Adding value exponentially
Foreign
payments
E-studentloan
E-Loans
E-billing
E-signature
Customer
value
Inv.Funds
E-shopping
E-identification
Equity,bond
etc trades
Balances+
Payments
General
E-salary InsuWAP-eq rance
WAP-fx
2001
E-mortg
Warrants
Time depos
E-invoicing
2002-4
2000
1999
1998
1996
1992
1988
Services
1982
2006-03-23
Page 7
3 000 000
2 500 000
2 000 000
1 500 000
1 000 000
500 000
2006-03-23
20
05
04
20
02
03
20
20
01
20
00
20
98
99
19
19
97
19
96
19
94
95
19
19
93
19
92
19
90
91
19
19
89
19
87
88
19
19
86
19
85
19
83
84
19
19
19
82
Page 8
200
180
160
140
120
100
80
60
40
20
0
E-bank up
128 million
payment trx
Manual down
95 million trx
Page 9
Industrial
Society
Information
Society
Business
Banking
Business
Business
Abyss
Increasing
Interaction
Travel
New
management
New
Business
logic
ICT
ICT
ICT
Industry
Government
Retail trade
Evolution
2006-03-23
Revolution
Productivity
leaps
Page 10
2006-03-23
Page 11
Page 12
2006-03-23
Page 13
IT-reality?
2006-03-23
Page 14
Mission impossible?
2006-03-23
Page 15
Enterprise Architecture
2006-03-23
Page 16
Consepts
The general term architecture is defined as the design of any type of
structure whether physical or conceptual, real or virtual (ORourke et
al. 2003)
Enterprise means a group of people organized for a particular
purpose to produce a product or provide a service (ORourke et al.
2003)
2006-03-23
Page 17
Enterprise Architecture
"Enterprise architecture (EA) identifies the main components of the
organization, its information systems, the ways in which these
components work together in order to achieve defined business
objectives, and the way in which the information systems support the
business processes of the organization.
The components include staff, business processes, technology,
information, financial and other resources, etc.
Enterprise architecting is the set of processes, tools, and structures
necessary to implement an enterprise-wide coherent and
consistent IT architecture for supporting the enterprise's
business operations.
It takes a holistic view of the enterprise's IT resources rather than an
application-by-application view." (Kaisler et al., 2005)
2006-03-23
Page 18
Enterprise Architecture
"Enterprise Architecture is a strategic information asset base, which
defines the mission, the information necessary to perform the mission
and the technologies necessary to perform the mission, and the
transitional processes for implementing new technologies in
response to the changing mission needs. An enterprise architecture
includes a baseline architecture, target architecture, and a
sequencing plan. " (CIO Council 2001)
"A defined EA is ...providing to people at all organizational levels an
explicit, common and meaningful structural frame of reference that
allows an understanding of what the enterprise does, when, where,
how and why it does it and what it uses to do it" (GAO, 2003)
Page 19
Enterprise Architecture
The design of business and IT system alignment is the domain of
Enterprise Architecture (EA). Enterprise architects seek to align
enterprise processes and structure with their supporting IT systems.
(Wegmann et al. 2005)
Enterprise Architecture is the process of translating business
vision and strategy into effective enterprise change by creating,
communicating and improving the key principles and models that
describe the enterprises future state and enable its evolution.
(Gartner Group 2006)
Business and IT structures
Business oriented
Holistic
Alignment
Transitional
2006-03-23
Page 20
Page 21
Software Architecture
Structures and relationships, static and dynamic views, assumptions and rationale
Focus: decomposition and allocation of responsibility, interface design, assignment to
processes and threads
guide
Architecture Guidelines and Policies
designers
Page 22
Enterprise
Enterprise
IT
IT
Architecture
Architecture
Domain
Domain
Scope
Group IT
Domain A
Scope
Domain B
Scope
Application
scope
Component
(Service)
scope
IT Vendor
Application
Application
Architecture
Architecture
Domain
Domain
2006-03-23
Domain IT
Page 23
Suppliers
Process map
Output
Company
Customer
Customer
Process 1
Process 2
Core
processes
Process 3
Process 4
Process environment
Support
processes
Process n Process m
Customer Processes
Process 1
Process m
Process X
Customer
Process 3
Role 1
Role 2
Sub-Process 21
Sub-Process 22
Sub-Process 24
Supplier
Sub-Process 23
Application
Interface
2006-03-23
Process n
Copyright 2007 TietoEnator Corporation
Page 24
2006-03-23
Page 25
Consepts
An EA framework is an abstract graphical representation of the
enterprise or more pragmatically its information landscape. EA
frameworks help enterprise architects classify different models,
facilitating different viewpoints and levels of detail for a spectrum of
users. They can also ease communication by clearly establishing
boundaries and responsibilities, depending on whether firms adopt
decentralized, centralized, or federated architect groups. Forrester
Research 2006
EA methodologies describe the different steps and deliverables
needed to progress along the EA front. Most methodologies are
available from private consulting companies. TOGAF from The Open
Group is the only methodology freely available to the end customers.
Forrester Research 2006
2006-03-23
Page 26
Consepts
An Enterprise Architecture framework is a communication model
for developing an Enterprise Architecture (EA). It is not an architecture
pe se. Rather; it presents a set of models, principles, services,
approaches, standards, design concepts, components, visualisations
and configurations that guide the development of specific aspect
architecture. Schekkerman, Jaap: How to survive in the jungle of
Enterprise Architecture Frameworks. Trafford, 2006.
2006-03-23
Page 27
Page 28
ISO/IEC
14252
DoD AF
2004
C4ISR
1999
DoD TRM
TAFIM
EA
Grid
TOGAF
2002
TOGAF
Zachman
1987
EAP
1992
FEAF
1999
TEAF
2000
TISAF
1997
UVA Model
1994
IAF v1
1996
EIF
2005
Zachman
2003
FEAF
2003
E2AF
2003
IAF v3
2001
NORA
2006
E2AF
2005
XAF
2003
Source: Schekkerman, Jaap: How to survive in the jungle of Enterprise Architecture Frameworks. Trafford, 2006.
2006-03-23
Page 29
Zachman Framework
WHAT
HOW
Pros :
The first and was long
time unique
Well Known
Really exhaustive
Different viewpoints
2006-03-23
WHERE
WHO
WHEN
WHY
Cons :
Too complex
Columns historically
sorted
Need to be tailored
Not for operations
Fragmentation effect
No typical models for the
columns on the right
Separates the
considerations on
enabling technologies
from strategies and
business development
Page 30
TOGAF
Pros:
Cons:
2006-03-23
Page 31
FEAF: NIST
Pros:
Cons:
2006-03-23
Page 32
NAF
Pros:
Cons:
2006-03-23
Page 33
Pros:
2006-03-23
Information
Architecture
Applications
Architecture
Technology
Architecture
Cons:
Page 34
2006-03-23
Page 35
Page 36
EA development process
2006-03-23
Page 37
TOGAF
ADM cycle
A
H
Architecture
Vision
Architecture
Change
Management
5. Migration
Options
7. Continuous
Review &
Update
2. Characterize
Baseline
G
Implementation
Governance
4. Opportunity
ID & Gap
Analysis
3. Target
Architecture
B
Business
Architecture
Requirements
F
Migration
Planning
Information
System
Architectures
D
E
Opportunities
and Solutions
Technology
Architecture
TEAF
cycle
2006-03-23
Page 38
EA project phases
Enterprise Architecture Development Process
2006-03-23
Target Architecture
Development Plan
Business Analysis
Business Process
Analysis
and Development
Road Map
IT Analysis
Application and
Information
Cost Estimation
IT Infrastructure
and
Technology
Risk Management
Page 39
workshop
workshop33
Information
InformationSystems
Systems
Architecture
Architecture
kick-off
kick-off
interviews
interviews
workshop1
workshop1
workshop
workshop55
workshop
workshop66
workshop
workshop44
presenpresentations
tations
workshop
workshop77
finalising
finalising
Roadmap
Roadmap presenpresentations
tations
Technical
TechnicalArchitecture
Architecture
Prestudy
Prestudy
IT
ITService
Service
Architecture
Architecture
month1
month2
month3
month4
Page 40
Consulting
1.
1.1.
1.1.1.
1.1.1.1.
Information
Facilitation
1.1.1.2.
Facilitative
Consulting
2006-03-23
1.2.
Operative
Consulting
Process
Facilitation
1.1.2.
1.1.2.1.
Technology Oriented
Business Oriented
Information Facillitation Information Facillitation
Low
Consulting
1.1.2.2.
Process
Support
1.2.1.
Method and
Process use
1.2.2.
Involvement to
the development process
High
Page 41
2006-03-23
Page 42
Questions
2006-03-23
Page 43
Just do it!
2006-03-23
Page 44
2006-03-23
Page 45