EA Basics PDF

Introduction to Enterprise Architecture
University of Jyvskyl
23rd Aug. 2007
Ari Hirvonen
2006-03-23
Copyright 2007 TietoEnator Corporation
Page 1
Agenda
Why EA
What is EA
EA frameworks and methodologies
2006-03-23
Page 2
Some TietoEnator facts

Annual net sales
exceeding EUR 1,5 billion
Over 15 000 employees in
more than 25 countries
Listed on Stockholm and
Helsinki Exchanges
Focusing on selected
industries
Since 1968
Superior expertise
At the core of our customers businesses
2006-03-23
Page 3
Some speaker facts
- Department manager of EA consulting in Government Services Finland

- CTO of GMR Business Area
- Ph.D. (economics) 2005
2006-03-23
Page 4
Why EA?
2006-03-23
Page 5
The Changing Role of ICT
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
Source: Ward and Peppard 2002, Dickson 2003

2006-03-23
Page 6
More than multi-device e-banking
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
Nordea: Netbank customers 1982 - 2005

4 500 000
4 000 000
3 500 000
customers
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
Number of transactions (private customers Nordea level)
200
180
160
140
120
100
80
60
40
20
0
E-bank up
128 million
payment trx
Manual down
95 million trx
1999 2000 2001 2002 2003 2004 2005

2006-03-23
Page 9
Megatrend: Business and ICT are merging
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
What are we aiming at?

Enterprise Architecture is the aligned big picture of organisations
business, information, information systems and technologies, and their
management
ICT is today any organisations strategic asset
ICT enables new business opportunities, improvements in
efficiency and effectiveness as well as cost savings
The concepts fundamental to managing information technology are those of business,
not of technology: portfolios, business value, investment, and alignment of resources
with strategic goals.
The objective of information technology investment is to provide business value in two
related ways: to successfully implement current strategies and to use the technology to
enable new strategies,
(Weill, P. and Broadbent, M.)
2006-03-23
Page 11
Primary Driver for EA
Based on data from over 200 EA programs

2006-03-23
Page 12
SOA adoption approaches

Integration ESB (60-70% of cases)
Uncover services from existing applications
Use an ESB to solve traditional A2A integration problems
BPM top down (20-30% cases)
Pick a business process for automation, model it and implement it in a
BPM system
Expose/Discover services from existing applications and use them in
process
BAM (10-20% cases)
Inject measurement points into existing infrastructure and collect
performance data about a business process with a BPM/ESB-tool
Analyse results and choose a way to make the measured process more
efficient
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 (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 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)
(GAO = US Government Accountability Office)

2006-03-23
Page 19
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
Enterprise Architecture (EA)

EA = Fin. Kokonaisarkkitehtuuri = Yritysarkkitehtuuri
The Open Group's Enterprise Architecture definition (TOGAF 2003):
There are four types of architecture that are commonly accepted as
subsets of an overall Enterprise Architecture:
business architecture: this defines the business strategy, governance,
organisation, and key business processes.
data/information architecture: this describes the structure of an
organization's logical and physical data assets and data management
resources.
application (systems) architecture: this kind of architecture provides a
blueprint for the individual application systems to be deployed, their
interactions, and their relationships to the core business processes of the
organization.
Information Technology (IT) architecture: the software infrastructure
intended to support the deployment of core, mission-critical applications.
Architecture != Just technology

2006-03-23
Page 21
Layered Model of Software Architecture

guide
software Meta-Architecture
architects Architectural vision, principles, styles, key concepts and mechanisms.
Typically part of EA
Focus: high-level decisions that will strongly influence the
structure of the system; rules certain structural choices out,
and guides selection decissions and tradeoffs among others
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
Use model and guidelines; policies, mechanisms and design patterns;

frameworks, infrastructure and standards
Focus:guide engineers in creating designs that maintain the integrity of architecture
Malan, R., Bredemeyer, B., 2002

2006-03-23
Page 22
Enterprise Architecture Impact Areas

System
System of
of systems
systems architecture
architecture
Enterprise IT architecture decisions
Domain architect decisions
Application architect
Enterprise
decisions
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
Component (Service) owner

decisions
System
System of
of components
components architecture
architecture
2006-03-23
Domain IT
Malan, R., Bredemeyer, B., 2002
Page 23
Modeling of Business Processes

Modeling levels and the hierarchy
Input
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
Process flow chart, Sub-Process 24
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
Page 24
EA frameworks and methodologies
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
Which EA framework do you mainly use

and plan to use in the next 18 months?
Source: Forrrester Research 2006

2006-03-23
Page 28
The history of EA frameworks

JTA
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:
Well known and widely

used
Strong process
Public and available
Commonly accepted EA
views included
Strong support for
technology architecture
Too strong technology

focus
Limited support for
abstraction perspective
Version 9 not yet available
Comes with a lot of
detailed information,
impossible to learn and
adopt in short projects
2006-03-23
Page 31
FEAF: NIST
Pros:
Cons:
Simple and easy to

understand
Reference models
Developed for government
purposes
Too simple (e.g.

abstraction levels missing)
From the 80s todays
networking platforms &
technologies not
considered
Process for large
government organisations
Separates the
considerations on
enabling technologies
from strategies and
business development
2006-03-23
Page 32
NAF
Pros:
Cons:
In use and proven in

practice
Interoperability
All you need is included
(e.g. method, framework,
tamplates)
Focus in technology and

systems development
rather than overall
planning
Focus in defence domain
Heavy methodology
2006-03-23
Page 33
The EA Grid: framework for the EA

process
Business
Architecture
Pros:
2006-03-23
Information
Architecture
Applications
Architecture
Technology
Architecture
Cons:
Simple and easy toEnterprise level decisions

Limited user base
Enterprise
understand
Even too simple for some
level
Based on long term
situations
consultancy practice &
theories of IS planning
Domain level decisions
4 main views commonly
Domain
level
shared
Includes all necessary
views
Based on common
public models (e.g. Systems level decisions
Systems
TOGAF) and therefore
level
can be integrated
Public and available
Page 34
Other light weight frameworks

EAP
Two highest levels from Zachman framework. Thus only business view
included.
A linear process suited for taking on EA work
Not a continuous, cyclic management process
Pera
For industry
For enterprise systems (ERP, SCM, MRP) development rather than
overall planning
ProACT, Forrester
Both owned by a consulting company
ARIS
Originally for enterprise systems development
Owned by a tool vendor
2006-03-23
Page 35
EA-frameworks and users
Source: Forrrester Research 2006

2006-03-23
Page 36
EA development process
2006-03-23
Page 37
Architecture Process Model examples

Prelim:
Framework and
Principles
DoC IT Architecture Process

1. Define Vision,
6.
&
Implementation Objectives
Principles
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
Current State Analysis
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
Architecture Process Scheduling

workshop
workshop22
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
Here is an outline for a 3 calendar month architecture process.

2006-03-23
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.
Technology Oriented Business Oriented

Operative Consulting Operative Consulting
Involvement to
the development process
High
Page 41
How far are you?

Methodologies for EA Maturity Evaluation
Enterprise Architecture Assessment Framework (Federal Enterprise
Architecture Program Management Office, US FEAPMO),
The Enterprise Architecture Maturity Model, EAMM (National
Association of State Chief Information Officers , NASCIO)
The Extended Enterprise Architecture Maturity Model, E2AMM
(Institute for Enterprise Architecture Developments, IFEAD).
A Framework for Assessing and Improving Enterprise Architecture
Management, EAMFF (US General Accounting Office, GAO)
The COSM (Component Oriented Software Manufacturing) Maturity
Model (Herzum Software).
IT Architecture Capability Maturity Model, ACMM (US Department of
Commerce, Doc)
Capability Maturity Models Integration, CMMI (The Software
Engineering Institute, SEI)
2006-03-23
Page 42
Questions
2006-03-23
Page 43
Just do it!
2006-03-23
Page 44
2006-03-23
Page 45

EA Basics PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

EA Basics PDF

Caricato da

Copyright:

Formati disponibili

Introduction to Enterprise Architecture

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Some TietoEnator facts

Copyright 2007 TietoEnator Corporation

Some speaker facts

- Department manager of EA consulting in Government Services Finland

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

The Changing Role of ICT

Source: Ward and Peppard 2002, Dickson 2003

Copyright 2007 TietoEnator Corporation

More than multi-device e-banking

Copyright 2007 TietoEnator Corporation

Nordea: Netbank customers 1982 - 2005

Copyright 2007 TietoEnator Corporation

Number of transactions (private customers Nordea level)

1999 2000 2001 2002 2003 2004 2005

Copyright 2007 TietoEnator Corporation

Megatrend: Business and ICT are merging

Copyright 2007 TietoEnator Corporation

What are we aiming at?

Copyright 2007 TietoEnator Corporation

Primary Driver for EA

Based on data from over 200 EA programs

Copyright 2007 TietoEnator Corporation

SOA adoption approaches

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

(GAO = US Government Accountability Office)

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Enterprise Architecture (EA)

Architecture != Just technology

Copyright 2007 TietoEnator Corporation

Layered Model of Software Architecture

Use model and guidelines; policies, mechanisms and design patterns;

Malan, R., Bredemeyer, B., 2002

Copyright 2007 TietoEnator Corporation

Enterprise Architecture Impact Areas

Component (Service) owner

Malan, R., Bredemeyer, B., 2002

Copyright 2007 TietoEnator Corporation

Modeling of Business Processes

Process flow chart, Sub-Process 24

EA frameworks and methodologies

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Which EA framework do you mainly use

Source: Forrrester Research 2006

Copyright 2007 TietoEnator Corporation

The history of EA frameworks

Copyright 2007 TietoEnator Corporation

Copyright 2007 TietoEnator Corporation

Well known and widely

Too strong technology

Copyright 2007 TietoEnator Corporation

Simple and easy to