Post on 30-Jan-2021
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise IT ArchitecturesEnterprise Architecture (EA) Part 1
Hans-Peter Hoidnhans-peter.hoidn@ch.ibm.com
December 3, 2007
EA Part 1 | Hans-Peter Hoidn 2
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Agenda
I. Positioning Enterprise Architecture (EA)
II. Enterprise Architecture Methods
III. Enterprise Capabilities & Principles
IV. EA Architecture Framework
V. Case 3
EA Part 1 | Hans-Peter Hoidn 3
Enterprise IT Architectures
© Copyright IBM Corporation 2007
I. Positioning Enterprise Architecture (EA)
EA Part 1 | Hans-Peter Hoidn 4
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Why “Enterprise Architecture”
EA is helping enterprises do the right things right
EA is a holistic approach to the control and co-ordination of IT based business projects
Two viewpoints: - Solution Architects are focused on creating an IT based solution to a
business problem- Enterprise Architects with a sense of what the enterprise needs to be and
do, and how IT should be used in a wider sense
EA Part 1 | Hans-Peter Hoidn 5
Enterprise IT Architectures
© Copyright IBM Corporation 2007
… and even if an individual house is well architected, if each house is different (e.g. different electricity voltage, water pressure) then the city will not work…
… plus, if the purpose of the building is not
clear…
Solution Architecture
… with the intent of avoiding chaos…
EA Part 1 | Hans-Peter Hoidn 6
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Architecture Management – Analogy of the Building Industry – Dependence on Size and Scope
EA Part 1 | Hans-Peter Hoidn 7
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Systems & TechnologySystems & Technology
Business EnvironmentBusiness Environment
Enterprise IT Architecture Channels
Applications
Common System ServicesInte
rface
Ser
vice
s
Sec
urity
Ser
vice
s
Network ServicesPlatform Services
Sys
tem
Man
agem
ent S
ervi
ces
Sys
tem
& In
frast
ruct
ure
Dev
elop
men
t
CommonApplicationServices
DataClaim
Enterprise Business ArchitectureG r o u p I T A r c h i t e c t u r e D e f i n i t i o n I n f r a s t r u c t u r e D e s i g n & P l a n n i n g E s t a b l i s h I T C o m p e t e n c y C e n t r eE n d U s e r I n f r a s t r u c t u r e U p g r a d eI n t e r - c o m p a n y W A N ( i m p l e . )
O u t s o u r c e N e w C o r e s y s t e m s
O u t s o u r c e H e l p d e s k a n d D e s k t o p
O u t s o u r c e n e t w o r k
O u t s o u r c i n g I n i t i a t i v e s
C o m p e t e n c y C e n t r e I n i t i a t i v e s
E l e c t r o n i c S e r v i c e D e l i v e r y
D a t a W a r e h o u s e
C u s t o m e r S e r v i c e C e n t r e
W A N i n fr a s tru c t ur e
In t ra n e t /M a i l i n fr a st ru c t u re
C us t o m e r S e r vi ceD at a W a re h o u s e
G r a p h ic a l IS
B .U . B .U .
D o c u m e n t M a n ag em e n t
S y s t e m s M a n a g e m e n t
M id d le w ar e
N E T W O R K
P l a n n i n g / D e s i g n I n i t i a t i v e s
I n f r a s t r u c t u r e I n i t i a t i v e s
O t h e rB u s i n e s s U n i t S y s t e m sK i o s k sT e l e m e t r y s y s t e m se t c
I n i t i a t i v e s f o c u s e d o n m i g r a t i n g t o t h e n e w d e l i v e r y e n v i r o n m e n t
P l a n n i n g / D e s i g nI n f r a s t r u c t u r eO u t s o u r c i n g
I n i t i a t i v e s f o c u s e d o n i m p l e m e n t i n g t h e v i s i o n
P l a n n i n g / d e s i g nI T C o m p e t e n c y c e n t r e
K e y G r o u p D e c i s i o n P o i n t s
Solution Architecture & Delivery Solution Outline Build Cycle DeploymentMacro Design Micro Design
Business & IT Strategy G r o u p I T A r c h i t e c t u r e D e f i n i t i o n I n f r a s t r u c t u r e D e s i g n & P l a n n i n g E s t a b l i s h I T C o m p e t e n c y C e n t r eE n d U s e r I n f r a s t r u c t u r e U p g r a d eI n t e r - c o m p a n y W A N ( i m p l e . )
O u t s o u r c e N e w C o r e s y s t e m s
O u t s o u r c e H e l p d e s k a n d D e s k t o p
O u t s o u r c e n e t w o r k
O u t s o u r c i n g I n i t i a t i v e s
C o m p e t e n c y C e n t r e I n i t i a t i v e s
E l e c t r o n i c S e r v i c e D e l i v e r y
D a t a W a r e h o u s e
C u s t o m e r S e r v i c e C e n t r e
W A N i n fr a s tru c t ur e
In t ra n e t /M a i l i n fr a st ru c t u re
C us t o m e r S e r vi ceD at a W a re h o u s e
G r a p h ic a l IS
B .U . B .U .
D o c u m e n t M a n ag em e n t
S y s t e m s M a n a g e m e n t
M id d le w ar e
N E T W O R K
P l a n n i n g / D e s i g n I n i t i a t i v e s
I n f r a s t r u c t u r e I n i t i a t i v e s
O t h e rB u s i n e s s U n i t S y s t e m sK i o s k sT e l e m e t r y s y s t e m se t c
I n i t i a t i v e s f o c u s e d o n m i g r a t i n g t o t h e n e w d e l i v e r y e n v i r o n m e n t
P l a n n i n g / D e s i g nI n f r a s t r u c t u r eO u t s o u r c i n g
I n i t i a t i v e s f o c u s e d o n i m p l e m e n t i n g t h e v i s i o n
P l a n n i n g / d e s i g nI T C o m p e t e n c y c e n t r e
K e y G r o u p D e c i s i o n P o i n t s
“the city plan”
“the building design”
“the city’s purpose & goals”
“the actual buildings”
“the external influences& interactions”
Enterprise Architecture
Solution Architecture
Strategy
Systems Technology
Business Context
BusinessTransformation
Software GroupProducts
Systems TechnologyGroup
Products
Systems Engineering &Architecture
CBM
LegacyTransformation
ApplicationPortfolio
ManagementSOA
Enterprise-Wide Architecture
EA is not an island … there are many variations of engagement
EA Part 1 | Hans-Peter Hoidn 8
Enterprise IT Architectures
© Copyright IBM Corporation 2007
System Architecture• functional aspects• operational aspects“the infrastructure and singlebuilding design”
BusinessStrategy
InformationTechnology
Strategy
BusinessOpportunity
TechnologyAvailability
Business Operating Environmentand IT Infrastructure
IT Solutions
Design andDelivery
Strategy
The Gap
If you do not know where you are going,
any road will do.
If you do not know where you are, a map will not help.
?
It can be a challenge to ensure IT based business solutions implement the business strategy…
EA Part 1 | Hans-Peter Hoidn 9
Enterprise IT Architectures
© Copyright IBM Corporation 2007
IBM believes that an Enterprise Architecture provides the vital linkages between “strategy” and “implementation”
System Architecture• functional aspects• operational aspects“the infrastructure and singlebuilding design”
BusinessStrategy
InformationTechnology
Strategy
BusinessOpportunity
TechnologyAvailability
Design andDelivery
EA identifies where the organization wants to be
and how to get there
EA tells the organization where they are on the map Enterprise Architecture
!!
Business Operating Environmentand IT Infrastructure
IT Solutions
Planning
Design andDelivery
Ent
erpr
ise
wid
e fo
cus
Pro
ject
focu
s
Strategy
EA Part 1 | Hans-Peter Hoidn 10
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Architecture“the city plan”
System Architecture• “the building design”
BusinessStrategy
InformationTechnology
Strategy
BusinessOpportunity
TechnologyAvailability
ITArchitecture
- Applications- Data- Technology
Planning
Design andDelivery
Ent
erpr
ise
wid
e fo
cus
Pro
ject
focu
s
Strategy
Business Operating Environmentand IT Infrastructure
IT Solutions
Enterprise Architecture
Transition Plan
BusinessArchitecture
- Processes- Information- People- Locations
Enterprise Architecture embraces both Business and IT Architectures, providing the “city plan” for “building projects”
EA Part 1 | Hans-Peter Hoidn 11
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Intended to capture the need for an EA to link an enterprise's business strategy to its change programs, through the definition of:
- Architecture models to capture the business’s intended structure (through a Business Architecture) and to provide a clear specification of how multiple projects and programs must exploit information technology (through common (explicit) IS and IT Architectures),
- Mechanisms such as Architecture Governance and Transition Planning to help plan, co-ordinate and control all parts of the business – ensuring they all “pull in the same direction”.
“The EA discipline defines and maintains the architecture models, governance and transition initiatives needed to effectively co-ordinate semi-autonomous groups towards common business and/or IT goals.“
EA Academy Study Team, Orlando Workshop, 12th-13th March 2004
Enterprise Architecture (EA) Definition – Architecture Models and Governance
EA Part 1 | Hans-Peter Hoidn 12
Enterprise IT Architectures
© Copyright IBM Corporation 2007
“The Enterprise Architecture is the organising logic for business processes and IT infrastructure, reflecting the integration and standardisation requirements of the company’s operating model
The Enterprise Architecture provides a long term view of a company’s processes, systems and technologies so that individual projects can build capabilities – not just fulfil immediate needs”
Ross et al, “Enterprise Architecture as Strategy”,2006 (Harvard business press)
A definition:
EA Part 1 | Hans-Peter Hoidn 13
Enterprise IT Architectures
© Copyright IBM Corporation 2007
A second Definition: IBM’s
“The EA discipline defines and maintains the architecture models, governance and transition initiatives needed to effectively co-ordinate semi-autonomous groups towards common business and/or IT goals.“
“The EA discipline defines and maintains the architecture models, governance and transition initiatives needed to effectively co-ordinate semi-autonomous groupstowards common business and/or IT goals.”
EA ensures the architecture is
maintained and used
EA is not just passive or
reactive, it is proactive
EA can address the
business andIT domains
“neutral phrasing”: EA works at many
levels
EA provides reference material in many forms
EA Part 1 | Hans-Peter Hoidn 14
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Strategy
Business Operating Environmentand IT Infrastructure
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
TransitionPlanning
ArchitectureGovernance
TransitionPlanning
ArchitectureGovernance
BusinessArchitecture
ITArchitecture
AEICorporate
YankeeGroup
SaturnGroup
YarnDivision
KnitsDivision
SenecaPlant
RaleighPlant
Ca shManageme nt
Shipping
Ac counting
ComponentDe sign
Yarn Buy ing
Order Entry
Compone nt
Scheduling
Yarn
Dy eing
Inventory
Ass ortmentPla nning
ComponentKnitting
Tagging & Pack ing
Business Structure
AEICorporate
YankeeGroup
SaturnGroup
YarnDivision
KnitsDivision
SenecaPlant
RaleighPlant
Ca shManageme nt
Shipping
Ac counting
ComponentDe sign
Yarn Buy ing
Order Entry
Compone nt
Scheduling
Yarn
Dy eing
Inventory
Ass ortmentPla nning
ComponentKnitting
Tagging & Pack ing
Business Structure
Business LocationsBusiness Locations
Change Programs
Soln Outline Macro Design Micro Design Devt, etc.
Programme Architecture
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureSoln Outline Macro Design Micro Design Devt, etc.
Programme Architecture
Soln Outline Macro Design Micro Design Devt, etc.
Programme Architecture
Soln Outline Macro Design Micro Design Devt, etc.
Programme Architecture
Soln Outline Macro Design Micro Design Devt, etc.
Programme Architecture
TechnologyAvailability
BusinessOpportunity
Business Strategy IT Strategy
Enterprise Architecture
System Design"the buildings"
Enterprise Architecture"the city plan"
Strategy"the city’s purpose & goals"
As an integral part ofthe strategic planning process, the EA is the linkage between the business strategy, IT strategy and IT implementation
EA guides investment, cost reduction and design decisions to support the goal of optimizing return on IT investments (ROI)
The Enterprise Architec-ture defines an environ-ment in which infrastruc-ture and solutions can be built for both known and unforeseen future requirements
Enterprise Architecture provides the “city plan” for business and IT “building blocks”
EA Part 1 | Hans-Peter Hoidn 15
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Strategy
Architecture
Dev Program
Architecture
Project PP
Architecture
Design DDesign D
Infra. Proj
Arch
D DD
Enterprise Architecture
Programme Architecture
Infrastructure Architecture
EA provides a context and guidance, keeping everyone “on the same road”
EA Part 1 | Hans-Peter Hoidn 16
Enterprise IT Architectures
© Copyright IBM Corporation 2007
II. Enterprise Architecture Methods
EA Part 1 | Hans-Peter Hoidn 17
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Main aspects of an Enterprise Architecture
Enterprise Architecture is between the Business and IT Strategy and the programs and projects to be carried out
Enterprise Architecture includes Business Architecture as well as IT Architecture (which is IS Architecture – Information System – and Technology Architecture)
Enterprise Architecture guides the programs and projects
EA Part 1 | Hans-Peter Hoidn 18
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro DesignBusiness as
usual projectprioritization & Planning
Work Streams
"These are theThings we Should do”
EARoadmap
BusinessObjectives,,Vision, etc.
EAGovernance
BuildingBlocksBuildingBlocks
Rules & stdconstructionsRules &
std
EAArchitecture
AchievingBusinessObjectives
“This is the waythese things shouldbe architected”
“Things we should do”
“Are we doing these Things the way we saidWe want them done?
“Are our target architectures still
right?”“Are we still moving in the right direction?”
EA is More than Architecture
EA Part 1 | Hans-Peter Hoidn 19
Enterprise IT Architectures
© Copyright IBM Corporation 2007
“Are our target architectures still
right?”
“Are we moving the right
direction?”
Programmes& Projects
Strategic DeliverySolution
Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Strategic Intent
EAGovernance
"Are we designing these systems the way we said we want them
done?”
Enterprise IT Architecture
FunctionalOperational
"This is the way these systems should be designed”
Enterprise Business
Architecture
“Business as Usual” project prioritisation &
planning
"These are the projects we should
do”
EA Transition
“These are ourroadmaps”
DOWNSTREAM: Ensuring projects can exploit the architecture’s “standard
components” requires each part to be described and published in an easy-to-
use, easy-to-find “catalogue like” format
UPSTREAM: Identifying viable projects that help realise the
enterprise architecture requires a good “map”, capable of portraying
the overall “as is” and “to be”architectural landscape
There are three parts to EA – part 1: Architecture
EA Part 1 | Hans-Peter Hoidn 20
Enterprise IT Architectures
© Copyright IBM Corporation 2007
“Are our target architectures still
right?”
“Are we moving the right
direction?”
Programmes& Projects
Strategic DeliverySolution
Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Strategic Intent
EAGovernance
"Are we designing these systems the way we said we want them
done?”
Enterprise IT Architecture
FunctionalOperational
"This is the way these systems should be designed”
Enterprise Business
Architecture
“Business as Usual” project prioritisation &
planning
"These are the projects we should
do”
EA Transition
“These are ourroadmaps”
CONFORMANCE and EXCEPTION: are projects using the architectures as
we wish them to?
VITALITY and COMMUNICATION:is the architecture still OK, and do
people know how to use it?
There are three parts to EA – part 2: Governance
EA Part 1 | Hans-Peter Hoidn 21
Enterprise IT Architectures
© Copyright IBM Corporation 2007
“Are our target architectures still
right?”
“Are we moving the right
direction?”
Programmes& Projects
Strategic DeliverySolution
Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Solution Outline Build Cycle DeploymentMacro Design Micro Design
Strategic Intent
EAGovernance
"Are we designing these systems the way we said we want them
done?”
Enterprise IT Architecture
FunctionalOperational
"This is the way these systems should be designed”
Enterprise Business
Architecture
“Business as Usual” project prioritisation &
planning
"These are the projects we should
do”
EA Transition
“These are ourroadmaps”
TRANSITION INITITIVES: these are the changes we
could make
TRANSITION PLANS: these are the
changes we want tomake
PROJECTS:these are the
changes we will make
There are three parts to EA – part 3: Transition
EA Part 1 | Hans-Peter Hoidn 22
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Therefore there are three aspects to implementing an Enterprise Architecture
Implementing the EA
Business
User
Arch Review
Board
TRB
IT SteeringCommittee
ProjectArchitect
or DA
Yes
Yes
No
No
BusinessRequirement
Identified
Analyse
and
Understand
Business
Requirement
Design
Solution
Develop/
implement
system/
solution
Research
&
analyse
conforming
alternatives
Conduct
Design/
Product
Evaluation
Review
Mtg
Identify
potential
confirming
alternatives
Advise/
Assist
ArchitectureInitiative
Advise/
Assist
DesignConforms to Architecture?
ArchConformingAlternativeavailable?
Vitality Process
ARB
TRB
DA
Governance
Organisation
Processes
Evaluation & Selection
Architecture
Models
Principles
Enterprise Tech Framework
Business ArchitectureInformationarchitectureComponentarchitecture
Data architecture
IT architecture
Cha
nnel
s
Applications
Common System Services
Inte
rfac
e S
ervi
ces
Sec
urity
Ser
vice
s
Network Services
Platform Services
Syst
em M
anag
emen
t Ser
vice
s
Syst
em &
Infr
astr
uctu
re D
evel
opm
ent
CommonApplication
Services
DataClaim
Transition
Transition Plan
Management Action Plan
Group IT Architecture Definition
Infrastructure Design & Planning
Establish IT Competency Centre
End User Infrastructure Upgrade
Inter-company WAN (imple.)
Outsource New Core systems
Outsource Helpdesk and Desktop
Outsource network
Outsourcing Initiatives
Competency Centre Initiatives
Electronic Service Delivery
Data Warehouse
Customer Service Centre
Reco gnise and r epor prob lem
D iagnose pro blem
Escalat e pr obl em
Anal yse pr obl em
Log P robl em
Cl ose pr obl em
U pdat e cust omer
Resol ve pr oblem
Bypass and/ or f ix
Conf ig. Management
Oper at ions Management
C hange Management
Cal l management
O per ati ons mana gement
Updat e customer
Perf and C apacit y man agement
WAN in frastruc ture
Intranet/Mai l infras tructure
Cus tomer Servic eData Warehous e
Graphica l IS
B.U.
B.U.
Document Management
Systems Management
Middleware
NETWORK
Planning/Design Initiatives
Infrastructure Initiatives
OtherBusiness Unit SystemsKiosksTelemetry systemsetc
Initiatives focused on migrating to the new delivery environment
Planning/DesignInfrastructureOutsourcing
Initiatives focused on implementing the vision
Planning/designIT Competency centre
Key Group Decision Points
EA Part 1 | Hans-Peter Hoidn 23
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Architecture
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
Business Architecture
Corporate StrategyFinance & Planning
Human ResourcesInformation Systems
Purchasing & Supply
Marketing& Sales
Technical Operations
FlyingOperations
CustomerService
ManageCargo
DevelopProducts
Develop Schedules
Distribute Products
ManageAgency Sales
ManageAlliances
ManageAeroplane
ManageAircraft Seat
Inventory
Perform Base Maintenance (A/C)
Perform Line Maintenance
MaintainEngines
MaintainComponents
Manage Materials & Service
Plan Crews
ScheduleCrews
ManageIn- flightService
ManageDay-of -flightOperations
ServiceReservations
Process PAX at Airports
Process Baggage
ManageAirport SystemsOperations
Perform Base Maintenance (contract)
Financial Planning & Reporting
Manage Labour Contracts
IT Architecture
ArchitectureTechnology
“This is the landscape of all the applications we envisage for the enterprise
“Application
Function Mo
del”
“This is the set of user types
you are allowed to use in your
Solution Architecture” “User Groups”
“This is the set of Data Groupsyou are allowed to use in your
Solution Architecture”
“Data S
tores”
“These are the building blocksyou are allowed to use in your
Solution Architecture”
“Enterprise
Technology
Framework”
There is a relatively simple mapping from EA to solution …
EA Part 1 | Hans-Peter Hoidn 24
Enterprise IT Architectures
© Copyright IBM Corporation 2007
II. Enterprise Architecture Methods
EA Part 1 | Hans-Peter Hoidn 25
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Architecture Methods
Enterprise Architecture methods provide guidelines and templatesfor the definition of an Enterprise Architecture
Templates are available for Work Products / Artifacts – most of them as described in Architecture Methods
Most popular Enterprise Architecture Methods- IBM - Zachman (www.zifa.com)- TOGAF (www.opengroup.org)
EA Part 1 | Hans-Peter Hoidn 26
Enterprise IT Architectures
© Copyright IBM Corporation 2007
The intersection between a layer and an aspect. Typically occupied by one or more of the EA Method’s architecture related work products
Framework cell (or “cell”)
An elemental part of an EA’s architecture. ABBs are used as standard parts across an enterprise in the design and construction of its many and varied business and IT systems, as well as being a useful categorisation of stuff in transition planning. An ABB category may be associated with a specific aspect of a specific layer of an Architecture framework
Architecture Building Block
The IS and IT architectures created for a specific business solution. Sometimes called IT Architecture (particularly by IT Architects), or Solution Design (often by our clients)
Solution Architecture
A slice of the EA architecture framework, generally drawn vertically, that separates out common themes or topics across the layers.
Architecture aspect
A slice of the EA architecture framework, generally drawn horizontally, that separates out the business, IS and technology assets.
Architecture layer
A structured approach to the management and use of an enterprisearchitecture’s various architectural assets, commonly called architecture building blocks (ABBs)
Architecture framework
Key terms and phrases used in EA Methods
EA Part 1 | Hans-Peter Hoidn 27
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business Architecture
Informationarchitecture
Componentarchitecture
Data architecture
IT architecture
How the business will be run
Logical model of information needs
Automated business functions
Physical model of data
Hardware & software products
”increased focus on a ’Market of one’”
”Customer information will be integrated across all bus. units”
”applications will use catalogue services”
”some personal data may be stored locally”
”Business units may use local SAP servers”
Strategy
Source: European Government Agency, 2002
Purpose ofthe layer
SamplePrinciple
A popular way of structuring an EA’s architecture framework: is to adopt a simple layered approach
EA Part 1 | Hans-Peter Hoidn 28
Enterprise IT Architectures
© Copyright IBM Corporation 2007
© CapGemini, 2005
© John A Zachman
http://www.zifa.com/
http://www.capgemini.com/services/soa/ent_architecture/
The Open Group’s Architecture Framework(TOGAF), UK
All EAs have a “framework” – a means of organizing, managing and communicating the architecture (1)
EA Part 1 | Hans-Peter Hoidn 29
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business Architecture
Technology Architecture
Governance
Strategic Gap Analysis
Transition
Enterprise Capabilities
IS Architecture
Current Environment
Proposal and Engagement PlanningClientObjectives
EmergingOpportunities
EA Method Overview
EA Part 1 | Hans-Peter Hoidn 30
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Strategy
Business Operating Environmentand IT Infrastructure
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
Prog
ram
foc
usEn
terp
rise
wid
e fo
cus
Strategy
Planning
Design and
Delivery
TransitionPlanning Gr ou p IT Ar c h ite c tu re D e finit ion Inf r a s tr uc tu r e D e s ig n & P la nn ing E s ta blis h IT C om pe te n c y
C e nt re
E n d U s e r In fr a s tr uc t ur e U pgr a de
Int e r- c om p a ny W AN (im p le .)
Ou ts ou rc e N ew C or e s y s te m s
Ou ts ou rc e H e lpd es k a n d D e s k top
O ut so ur c e n e tw or k
O u ts o u rc in g In it ia t iv e s
C o m p e ten cy C en tre In it ia t iv e s
E le c tr on ic S e r vi ce D e live r y
D a ta W a r eh ous e
C u s tom e r S e r v ic e C e ntr e
W A N inf ras tru ct ureIn tra ne t/M ail inf ra str uct ure
C us tom e r S er vic eDa ta W are ho us e
G ra ph ic al I S
B .U. B .U .
D oc um e nt Ma n ag em en t
S ys te ms M an a ge me nt
Mi dd lew ar e
N E T W O R K
Pl an n in g /D es ig n I n it i at i ve s
In fr as tru ctu re In it ia t iv e s
O th erB u sin ess U n it S ystem sK i osk sTel em etr y sys te m setc
In itia tiv e s f oc us e d on m igr a tin g to the n e w d e liv e ry e nv ir on m e nt
P la nn ing / D es i gnI n f ras truc t u reO uts ou rc i ng
In itia tiv e s f oc us e d on im ple m e n ting the v is io n
P la nn ing / des i gnI T C om pet enc y c en tre
K e y G ro up D ec is io n P o int s
ArchitectureGovernance
TransitionPlanning Gr ou p IT Ar c h ite c tu re D e finit ion Inf r a s tr uc tu r e D e s ig n & P la nn ing E s ta blis h IT C om pe te n c y
C e nt re
E n d U s e r In fr a s tr uc t ur e U pgr a de
Int e r- c om p a ny W AN (im p le .)
Ou ts ou rc e N ew C or e s y s te m s
Ou ts ou rc e H e lpd es k a n d D e s k top
O ut so ur c e n e tw or k
O u ts o u rc in g In it ia t iv e s
C o m p e ten cy C en tre In it ia t iv e s
E le c tr on ic S e r vi ce D e live r y
D a ta W a r eh ous e
C u s tom e r S e r v ic e C e ntr e
W A N inf ras tru ct ureIn tra ne t/M ail inf ra str uct ure
C us tom e r S er vic eDa ta W are ho us e
G ra ph ic al I S
B .U. B .U .
D oc um e nt Ma n ag em en t
S ys te ms M an a ge me nt
Mi dd lew ar e
N E T W O R K
Pl an n in g /D es ig n I n it i at i ve s
In fr as tru ctu re In it ia t iv e s
O th erB u sin ess U n it S ystem sK i osk sTel em etr y sys te m setc
In itia tiv e s f oc us e d on m igr a tin g to the n e w d e liv e ry e nv ir on m e nt
P la nn ing / D es i gnI n f ras truc t u reO uts ou rc i ng
In itia tiv e s f oc us e d on im ple m e n ting the v is io n
P la nn ing / des i gnI T C om pet enc y c en tre
K e y G ro up D ec is io n P o int s
ArchitectureGovernance
BusinessArchitecture
ITArchitecture
AEICorporate
YankeeGroup
SaturnGroup
YarnDivision
KnitsDivision
SenecaPlant
RaleighPlant
CashManagement
Shippi ng
Accounting
ComponentDesign
Yarn Buying
Order E ntry
ComponentSchedul ing
YarnDyeing
Inventory
Assortm entP lanni ng
Com ponentKnitting
Tagging & P acking
Business Structure
AEICorporate
YankeeGroup
SaturnGroup
YarnDivision
KnitsDivision
SenecaPlant
RaleighPlant
CashManagement
Shippi ng
Accounting
ComponentDesign
Yarn Buying
Order E ntry
ComponentSchedul ing
YarnDyeing
Inventory
Assortm entP lanni ng
Com ponentKnitting
Tagging & P acking
Business Structure
Business LocationsBusiness Locations
Change Programs
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGro u p I T A rc hi te ctu re D e f in i t i on I n fra stru c tur e D e s ig n & P l a nn i n gE sta b l is h IT C o mp e ten c y C e ntre
E nd U s er I nfra s truc tu re U p gra d e
I nte r-c o mp an y W A N ( i m p le . )
O uts o u rce N ew C ore sy s tem s
O uts o u rce H el p de s k a nd D es kto p
Ou tso u rc e ne two rk
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ureC ustom er Se rvice
Data Ware house
Graph ical IS
B.U. B.U.
Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nn ing /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu re
O ut sour ci ngIn itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGro u p I T A rc hi te ctu re D e f in i t i on I n fra stru c tur e D e s ig n & P l a nn i n gE sta b l is h IT C o mp e ten c y C e ntre
E nd U s er I nfra s truc tu re U p gra d e
I nte r-c o mp an y W A N ( i m p le . )
O uts o u rce N ew C ore sy s tem s
O uts o u rce H el p de s k a nd D es kto p
Ou tso u rc e ne two rk
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ure
C ustom er Se rviceData Ware house
Graph ical IS
B.U. B.U. Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nning /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu reO ut sour ci ng
In itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGroup IT Arc hite cture De fin ition In fra struc tur e De s ign & Pla nningEsta b lis h IT Compe tenc y Ce ntre
End Us er Infra s truc ture Upgra de
Inte r-c ompany W AN (im ple .)
O uts ource New C ore sy s tem s
O uts ource H elpde s k a nd D es ktop
Outsourc e ne twork
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ureC ustom er Se rvice
Data Ware house
Graph ical IS
B.U. B.U.
Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nning /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu re
O ut sour ci ngIn itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGroup IT Arc hite cture De fin ition In fra struc tur e De s ign & Pla nningEsta b lis h IT Compe tenc y Ce ntre
End Us er Infra s truc ture Upgra de
Inte r-c ompany W AN (im ple .)
O uts ource New C ore sy s tem s
O uts ource H elpde s k a nd D es ktop
Outsourc e ne twork
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ureC ustom er Se rvice
Data Ware house
Graph ical IS
B.U. B.U.
Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nning /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu re
O ut sour ci ngIn itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGroup IT Arc hite cture De fin ition In fra struc tur e De s ign & Pla nningEsta b lis h IT Compe tenc y Ce ntre
End Us er Infra s truc ture Upgra de
Inte r-c ompany W AN (im ple .)
O uts ource New C ore sy s tem s
O uts ource H elpde s k a nd D es ktop
Outsourc e ne twork
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ure
C ustom er Se rviceData Ware house
Graph ical IS
B.U. B.U. Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nning /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu reO ut sour ci ng
In itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
Soln Outline Macro Design Micro Design Devt, etc.
Programme ArchitectureGroup IT Arc hite cture De fin ition In fra struc tur e De s ign & Pla nningEsta b lis h IT Compe tenc y Ce ntre
End Us er Infra s truc ture Upgra de
Inte r-c ompany W AN (im ple .)
O uts ource New C ore sy s tem s
O uts ource H elpde s k a nd D es ktop
Outsourc e ne twork
O uts ou rc ing In itia tiv e s
C om pe te nc y Ce nt re In itia tiv e s
Ele ctr on ic Se rv ice Delive ry
Da ta W a rehouse
Cus tom er Se rvic e Ce ntre
WAN infras tructur eIntra net/Ma il infra struct ure
C ustom er Se rviceData Ware house
Graph ical IS
B.U. B.U. Docu ment Manag emen t
Sys tems M anag emen t
Middle ware
N ET W O RK
Pla nning /D e s ign In itia tiv e s
In fra s tr uc ture In it iat ive s
Othe rB us in ess U ni t S yst em sK io sksTe le m et r y s yst em set c
In itia tive s foc us e d on m igra ting to the ne w de liv ery env ironm ent
P lan nin g/ De sig nI nf ra str uc tu reO ut sour ci ng
In itia tive s foc us e d on im ple me nting the vis ion
P lan nin g/ desi gnI T Co mp et ency ce nt re
K ey G ro u p De c i si o n P oi n ts
TechnologyAvailability
BusinessOpportunity
Business Strategy IT Strategy
Enterprise Architecture
Enterprise Capabilities
Business Architecture
IS Architecture
Technology Architecture The EA Consulting Method’s architectural layers
All EAs have a “framework” – a means of organizing, managing and communicating the architecture (2)
EA Part 1 | Hans-Peter Hoidn 31
Enterprise IT Architectures
© Copyright IBM Corporation 2007
All EAs have a “framework” – a means of organizing, managing and communicating the architecture (3)
EA Part 1 | Hans-Peter Hoidn 32
Enterprise IT Architectures
© Copyright IBM Corporation 2007
A business architecturehas no regard for the use
of automation
An information systems architecture describes
how parts of the business are to be automated –known as the “business
dependent IT architecture”
A technology architecture describes the underlying, “business
independent IT architecture” needed to
support automation
The Enterprise Capabilities provide a strategic context for the
architecturs
Describing the architectural context, at each level of abstraction
Describing the functional models and building blocks
from which IT based business solutions are built
Describing how the IT based business solutions are spread out over the business and geographic
landscape
All EAs have a “framework” – a means of organizing, managing and communicating the architecture (4)
EA Part 1 | Hans-Peter Hoidn 33
Enterprise IT Architectures
© Copyright IBM Corporation 2007
This framework provides a readily navigated and understood source of guidance for Solution Projects
Home Shopping Order Mgt System
Customer registrationCustomer order handlingShopping listsPayment detailsDelivery details
Credit authorisationrequests
Catalogue updates
Credit authorisations
OrdersAmendmentsDelivery arrangements
Customer registrationCustomer order creationCustomer order handlingShopping listsPayment detailsDelivery details
Order exceptionsOrder statusSubmitted orders
Order exceptions
Customer registrationCustomer order handlingShopping listsPayment detailsDelivery details
Product & catalog updates
A_WarehouseMgt System
A_ProductSystem
A_CreditAgency
A_E-mailSystem
A_On-line Customer
A_Off-line Customer
A_Call CentreRep.
A_CatalogueSystem
A_non-foodFulfillment
A_Mgt InfoSystem
Sales data
Product updates
A_Application Administrator
Application Maintenance
!!!
The characteristics of this actor must
match one of the User Groups,
while their location must be
one of the location types in
Locations
This must be one of the applications (*) on
the Application Component Map
These actors are also applications(*) in the
Application Component Map
The business data“owned” by these
applications is defined in the Data Stores
The services offered across these echanges
are defined on the Application Component
Map (from theApplication Services
Model)
EA Part 1 | Hans-Peter Hoidn 34
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Work Products guide and govern how solution Work Products are constructed
“EA constrains
and co-
ordinates the
construction of IT based business systems”
Use Case Model
Non-fn Rqts
Context Diagram
Arch Over Diagram
Component Model
Operational Model
Deployment Units
Requirements
Architecture
Reference Architectures
Viability
Enterprise Architecture
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
Business Architecture
Corporate StrategyFinance & PlanningHuman ResourcesInformation SystemsPurchasing & Supply
Marketing& Sales
Technical Operations
FlyingOperations
CustomerService
ManageCargo
DevelopProducts
Develop Schedules
Distribute Products
ManageAgency Sales
ManageAlliances
ManageAeroplane
ManageAircraft Seat Inventory
Perform Base Maintenance (A/C)
Perform Line Maintenance
MaintainEngines
MaintainComponents
Manage Materials & Service
Plan Crews
ScheduleCrews
ManageIn- flightService
ManageDay-of-flightOperations
ServiceReservations
Process PAX at Airports
Process Baggage
ManageAirport SystemsOperations
Perform Base Maintenance (contract)
Financial Planning & Reporting Manage
Labour Contracts
IT Architecture
ArchitectureTechnology
EA Part 1 | Hans-Peter Hoidn 35
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Res
ourc
esC
apab
ilitie
sPr
opos
ition
sVa
lue
Sell books onlineAttract people to
website
Web-based catalog
Handle e-commerce
Context sensitive
advertising
3rd party order
fulfillment
Offer low pricing
Agreement with Yahoo, Excite, AOL
Scalable Servers
Proactive Notification
System"Associates"
IT SystemBook
DatabaseDistribution
Contract
Distribute through
Premier Online
BooksellerLow Cost Provider
3rd party search
capability
3rd party distribution capability
Convenient Transactions
Large Selection
Web-based search
3rd party web content
Information
Process
Organisation
Technology
Capability
Enterprise Capabilities: Linking Strategy to Architecture(Example Amazon)
EA Part 1 | Hans-Peter Hoidn 36
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business Architecture
Business Locations
Business Information
Business Roles
Business ProcessesActivity Activity Activity ActivityActivity
Event
Process ProcessProcess Process Process
Capability ModelCapability ScenariosCapability Enablers
Business DirectionBusiness Drivers
Business Model
AEICorporate
YankeeGroup
SaturnGroup
YarnDivision
KnitsDivision
SenecaPlant
RaleighPlant
CashManagement
Shipping
Accounting
ComponentDesign
Yarn Buying
Order Entry
ComponentScheduling
YarnDyeing
Inventory
AssortmentPlanning
ComponentKnitting
Tagging & Packing
Business Structure
Business Strategy
Business Architecture: Organization and co-operation
EA Part 1 | Hans-Peter Hoidn 37
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Cha
nnel
s
Applications Data
Common System Services
Inte
rfac
e Se
rvic
es
Secu
rity
Serv
ices
Network Services
Platform Services
Syst
em M
anag
emen
t Ser
vice
s
Syst
em &
Infr
astr
uctu
re D
evel
opm
ent
CommonApplication
Services
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
IS Architecture: Shape and Structure for ALL IT projects
EA Part 1 | Hans-Peter Hoidn 38
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Architecture ReviewBoard
Decides on which IT is best suited for the needs of the enterpriseDecides when a change in the architecture is neededPrioritise Initiatives
Ensures solution designs comply with the architectureMaintains the architecture
Technical ReviewBoard
Project Design Authority
Uses the architecture to best satisfy the project’s needs
Conformance
Conformance
Sele
ctio
nSe
lect
ion
VitalityVit
ality
Except
ions
Except
ions
Enterprise ArchitectureManagement
Processes
Enterprise ArchitectureManagement
Processes
Communication
Communication
Governance: Keeping it all together – day in, day out
EA Part 1 | Hans-Peter Hoidn 39
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Transition
Business System Project
Application Service Project
Infrastructure Project
IT Process Project
Organisation Project
01
23
45
MissionObjectives
ReqmtsOptions
Define
Monitor
Process
Mgt
Strategy
TrackResearchUnderstandDesignIntegrate
SLAs
Ownership
R&R
Skills
Scope
Usability
MetricsCust Sat
Improve
Gap Analysis and Transition: From A to B
EA Part 1 | Hans-Peter Hoidn 40
Enterprise IT Architectures
© Copyright IBM Corporation 2007
III. Enterprise Capabilities & Principles
EA Part 1 | Hans-Peter Hoidn 41
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Capabilities & Principles
Enterprise Architecture Overview Diagram
Enterprise Capability Model- This linkage between strategy and architecture can be represented using
three key concepts. The network of these 3 concepts is referred to as the Strategic Capability Network (SCN).
Enterprise Architecture Principles, Policies & Guidelines
EA Part 1 | Hans-Peter Hoidn 42
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Architecture Overview DiagramExample 1
e-business system boundary
Web Client(Browser)
PervasiveComputing and
Wireless Devices
Device Gateway
InternalLegacy
Applications
PRESENTATIONTIER
APPLICATIONTIER
ENTERPRISETIER
Systems Management Services
Base System Services
Enabling Services – JVM, XML Parsers etc.
Networking Services
ExternalPartnerServices
PackagedBusiness
Applications
Brokering
Process Mgmt
Common &Custom Svscs
AdaptersEnterpriseDatabaseExternall
IntegrationServices
Presentation LogicProcessing
Application LogicProcessing
Session State Manager
Load Balancing
Connection Pooling
Thread Pooling
Web ApplicationServices
Web Server
Caching
Proxies
Dispatcher/Load Balancing
Firewall
Security
WebEnhancingServices Data
Stores
PresentationDeliveryServices
EA Part 1 | Hans-Peter Hoidn 43
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Architecture Overview DiagramExample 2
Presentation Services
Application ServicesResource Managers
Internet
LoadBalancer
ReverseProxyServer
Browser
PervasiveDevice
Third PartySystems or
Services
Directory & SecurityServices
UserProfiles
StaticContent
IntegrationHub
Public orPrivate
Networks
Transcoder
Clients
Universal Layer
Enterprise System Management
Enterprise Security Management
ContentManagement
ManagedContent
ApplicationDatabaseServices
ApplicationData
Web ServerContentDelivery
WebApplication
ServicesApplication
Logic
PackagedSolutions
LegacyApplications
CRM
EnterpriseDatabase(s)
DeviceGateway
EA Part 1 | Hans-Peter Hoidn 44
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Strategic Capability Network (SCN) – Overview
EA Part 1 | Hans-Peter Hoidn 45
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Strategic Capabilities Network (SCN)
V
Value Proposition: What a company needs to be in order to offer a differentiated value to the market.Example: Ikea’s low cost, customer convenience, modular design
VV
C
C
C
CC
C
CC
Capability: What a company needs to do in order to achieve its strategic positions. Capabilities perform, improve, and create the activities of the firm.Example: Ability to design for customer assembly, Ability to merchandise in-store and online.
RR
R
R
R
RR
R
R
R
Capability Enabler(Resource): What a company needs to have in order to perform its capabilities. Resources represent the process, knowledge, organization and technology assets of the firm.Example: In-house engineers and designers, store locations, store layout expertise, web developer/programmer, server…
R
R
R
R
RR
R
Strategic Capability Network (SCN) – Detailed
EA Part 1 | Hans-Peter Hoidn 46
Enterprise IT Architectures
© Copyright IBM Corporation 2007
ITCa
pabi
litie
s
IT R
esou
rces
Valu
ePr
o pos
itio
nBu
sine
ss c
apab
iliti
es
Efficientscale
operations
Costleadership in
targetmarkets
Billing engine
Single customerview
Digitalstreaming
Contentwholesaler
Instantmessaging
Multi-modalPIM
Video telephany
Location basedservices & maps
WebSphere VoiceServer
WebSphere VoiceResponse
WebSphere ApplicationServer Network
Deployment
WebSphere EveryplaceMobile Portal
Rational SoftwareArchitect
Rational ApplicationDeveloper
Rational ClearCase
Lotus Domino WebSphere BusinessIntegration Server
Foundation
WebSphere StudioIntegration Edition
WebSphere BusinessIntegration Modeler
News & sportsfeeds
Music
Premiumdownloadservices
(relevance)
Games
Aggregation 3rdparty services
Customisedbilling
presentation &delivery
High qualitycustomerservice
Leadershipin youth
Consumerservices
SMB servicesEnterpriseservices
Secure highspeed data
WAPVoice
recognition
Zoo Portal
WebSphere ApplicationServer Extended
Deployment
Lotus Sametime
Lotus Quickplace
PIM Clientless multimodal Mobile portal AtomicRelevance
WAS XD
WAS ND
Example: Business Capabilities for Telco 3G
EA Part 1 | Hans-Peter Hoidn 47
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Strategic Capabilities Network (SCN)
V VV
C
C
C
CC
C
CC
RR
R
R
R
RR
R
R
R
R
R
R
R
RR
R
EA Engagement: During enterprise architecture activities, we focus on refining the needed capabilities and identifying the resources (capability enablers) the client needs to meet its strategic objectives.
Strategy Engagement: During strategy activities the focus is on understanding the client’s existing capabilities, evaluating their strengths and weaknesses and identifying new capabilities required.
The SCN is created and developed in Strategy engagements and Enterprise Architecture engagements
EA Part 1 | Hans-Peter Hoidn 48
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Architecture Principles
EA Part 1 | Hans-Peter Hoidn 49
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Applications DataOperationsSecurity
Technology
GuidingPrinciples
Technology AcquisitionTechnology Diversity Control
Training & Communication
FlexibilityCommon FunctionsApplication StandardsDevelopment Method
Data StewardshipData ManagementData ConfidentialityData Scalability
OwnershipConsistent EnvironmentReadinessService Levels
ComplianceEase of Use
Principle Example
Architecture Compliance: All deployment of IT systems, components and processes will conform to the Enterprise Architecture principles, processes and standards.
Motivation: …Implications: …Metrics: …
Architecture Principles, Policies & Guidelines are key governance mechanisms
EA Part 1 | Hans-Peter Hoidn 50
Enterprise IT Architectures
© Copyright IBM Corporation 2007
IT Systems will be designed to allow rapid implementation of changes to business rules - to reflect changes in business requirements. Motivation: - Increased flexibility to rapidly implement
changed business requirements- Reduced costs associated with making and
implementing system changes- Allows the parameterization of business rules
to minimize IT development
Implication:- Systems need to be designed such that
business rules are held externally from processing logic
- Increased cost of initial application development to make use of parameterisedbusiness rules
- Need to define the business rules which will be parameterised and how they will be accessed
- Imposes an additional non-functional requirement on the selection of ready-built solutions
Need to review and revise testing standards to ensure changes to external parameters do not impact system characteristics, e.g. performance
ANYbank will be proactive and innovative in its use of technology while minimizing the risk from being at the leading edge.Motivation: - Increases competitive advantage by
implementing systems that provide better customer service and enable new products to be brought to market more effectively
- Reduces costs by exploiting effective, proven technologies
- Contains risk by not being at the leading edge of technological advance
Implication:- Some competitive advantage may be lost
through not exploiting new technology when it first becomes available
- Resources are required to monitor, evaluate, trial and assess business opportunities arising from new technologies
Example: Guiding principles
EA Part 1 | Hans-Peter Hoidn 51
Enterprise IT Architectures
© Copyright IBM Corporation 2007
IV. EA Architecture Framework
EA Part 1 | Hans-Peter Hoidn 52
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Enterprise Architecture
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Object s
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Object s
Business Architecture
Corporate StrategyFinance & PlanningHuman ResourcesInformation SystemsPurchasing & Supply
Marketing& Sales
Technical Operations
FlyingOperations
CustomerService
ManageCargo
DevelopProducts
Develop Schedules
Distribute Products
ManageAgency Sales
ManageAlliances
ManageAeroplan
ManageAircraft Seat Inventory
Perform Base Maintenance (A/C)
Perform Line Maintenance
MaintainEngines
MaintainComponents
Manage Materials & Service
Plan Crews
ScheduleCrews
ManageIn-f lightService
ManageDay-of-f lightOperations
ServiceReservations
Process PAX at Airports
Process Baggage
ManageAirport SystemsOperations
Perform Base Maintenance (contract)
Financial Planning & Reporting Manage
Labor Contracts
TechnologyArchitecture
ISArchitecture
Enterprise Architecture Decomposition
EA Part 1 | Hans-Peter Hoidn 53
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Functional Aspect of Architecture
Data
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
BusinessArchitecture
IT Architecture
TechnologyArchitecture
Enterprise Architecture Framework
Applications
Users
Business Architecture
Information Systems Architecture
Technology Architecture
A business architecture has no regard for the use
of automation
An information systems architecture describes those aspects of the business that
are to be automated –sometimes known as the “business dependent IT
architecture”
A technology architecture describes the underlying, “business independent” IT
needed to support automation
“line of automation”
“line of business interest”
EA architecture framework – Layers
EA Part 1 | Hans-Peter Hoidn 54
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business Architecture
Technology Architecture
Enterprise Capabilities
IS Architecture
Business Event List
Locations
IT NodesIT Components
Business Activity Mdl Business
Structure
Technology Reference Architectures
Application Groups
User Groups IS Reference
Architectures
Capability Model
ResourcesEA
Overview Diagram
Strategic CBM
Business Directions
EA Guiding Principles
Business Scenarios
Deployment Unit
MatricesData
StoresDeployment
Units (IS)
Placement Guidelines
Standard Use Cases
Enterprise KPIs
Standard NFRs
Roles Business Reference Architectures
Enterprise Information
ModelUsage
Matrices
Data
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
BusinessArchitecture
IT Architecture
TechnologyArchitecture
Enterprise Architecture Framework
Applications
Users
Func
tiona
l vie
w
Use
r vi
ew
Dat
a vi
ew
BusinessArchitecture
IS Architecture
TechnologyArchitecture
Showing only a few, representative, work product dependencies
EA’s architecture framework – Use of work products and the notion of work product dependencies
EA Part 1 | Hans-Peter Hoidn 55
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business Architecture – Purpose
A Business Architecture (BA) provides a framework which reflects both current and future business environments and guides future IT investment and implementation decisions.
It ensures that any tactical decision making is aligned with the overall business goals and objectives.
It provides a transformation vehicle that allows a business strategy to be effectively translated into an implementation plan which uses process, information/knowledge, organization and technology resources.
EA Part 1 | Hans-Peter Hoidn 56
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business roles are logical, categories of job that perform the business activities of the enterprise — e.g. Underwriter, Claims Assessor, Regulator, Loan Recipient, Sales Person. As such, they combine business activities into a recognisable relationship.
Business Role
A person, place, thing, concept, or event that the business needs to manage and about which it may need to keep data.
Information Entity
A stimulus or trigger which initiates one or more processes. A set of conditions which cause a process to be performed.
Business Event
Activities are combined to create a business process — a structured, measured set of activities, that takes input and creates output of value to a customer. A "leaf level" activity can occur in many different business processes.
Business Process
An activity may be a manual or automated operation that completes a unit of work. A "leaf level" activity is the lowest level of activity that cannot be decomposed further without considering how to implement them.
Business Activity
Business locations identify both the physical and logical places, or sites, where the activities of the business are carried out. The physical locations are simply the geographical places where the business has a presence; the logical locations are classifications, or categories, of these physical sites, based on the types of business activities that are performed at them.
Business Location
Business Architecture – Definitions
EA Part 1 | Hans-Peter Hoidn 57
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Client orientation and role recognition Available, consistent, accurate client informationReduced duplicationFlexible, reusable componentsLower maintenance costsAccurate marketing informationCross-marketing, target-marketingFaster time-to-market Ability to add or assimilate channels
Externalization of rules
Standardization
Generalization
Business Architecture
Business Architecture – Reducing Variation
EA Part 1 | Hans-Peter Hoidn 58
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business models are built for the purpose of:Common understandingCommunicationRequirements definitionOptimal process definitionProblem resolutionReduced variation and greater reuseAlignment of projects to business strategy and priorities
A Business Model does not include implementation considerations.
A Business Model is a structured abstraction of important features of "the real world" for solving business problems. It is built within the Business Architecture to represent what the business cares about.
A good Business Architecture incorporates a model of how the company wants to do business in future
EA Part 1 | Hans-Peter Hoidn 59
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Business activities: define what is done. - How are business activities defined?- How easily can they be changed?- Are they reusable?
Business Information is an organization's most important asset.
- Is it defined in a common, useable form?- Is it being used effectively?- Is access to information limited by the current
organizational structure?
Business conditions determine how business dynamics are handled.
- How are the business procedures defined?- Can you easily change why, when and by
whom a business activity is performed?
Activities
Information
Roles & Locations
Events
A Business Model provides a common, stable, flexible, understandable, rigorous definition of a client's business
EA Part 1 | Hans-Peter Hoidn 60
Enterprise IT Architectures
© Copyright IBM Corporation 2007
User Groups
Business Applications& Services Data Stores
POLICY
Producer CompensationClaimant Claim Business PartnersProducerService Providers
Policy FinancialsInsured Objects Insurance ProductPolicy
Training, Education, AdviceThird Parties InquiriesLegal & Recovery ActionsExternal Agencies
Claim
Sponsoring OrganizationMarket ProspectsInsured PartyBusiness Plans
Info Objects
It is vital to ensure these are defined appropriately forthe whole enterprise
Enterprise Architecture
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Objects
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Objects
Business Architecture
Corporate StrategyFinance & PlanningHuman ResourcesInformation SystemsPurchasing & Supply
Marketing& Sales
Technical Operations
FlyingOperations
CustomerService
ManageCargo
DevelopProduc ts
Develop Schedules
Distribute Produc ts
ManageAgency Sales
ManageA lliances
ManageAer oplan
ManageA ircr af t Seat Inventor y
Perf orm Base Maintenance (A /C)
Perf orm Line Maintenance
MaintainEngines
MaintainComponents
Manage Mater ials & Ser vice
Plan Crews
ScheduleCr ew s
ManageIn- flightServ ice
ManageDay-of -f lightOperations
Serv iceReservations
Process PAX at Air ports
Process Baggage
ManageA irport SystemsOperations
Perf orm Base Maintenance (contract)
Financial Planning & Repor ting Manage
Labor Contr ac ts
TechnologyArchitecture
The IS Architecture is centered on an enterprise wide specification of the business drivers
EA Part 1 | Hans-Peter Hoidn 61
Enterprise IT Architectures
© Copyright IBM Corporation 2007
The Application Function Modelrepresents the optimal set of applications (or application groups) required to support the enterprise:
- The business functions contained within an application are closely related
- The scope and boundaries of each of the applications is clearly defined and do not overlap
Manage Enterprise Infrastructure
Develop and Administer Programs and Products
Deliver Health Services
Deliver and Manage Stakeholder Value
Develop and Manage the Business
Health Services and Products
Clinical Programs
Health Care Delivery
Networks
Outcomes and Medical
Management
Wellness and Prevention
Health Condition
Episodic Care
Business Operations Information & Technology
Customer Relationship Management Alliance Management Service Management
Business Mission, Goals and Markets
Strategies and Plans Performance Measures and Targets
Manage Knowledge
Knowledge Assets
Car
e C
oord
inat
ion
Enterprise Architecture
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Objects
UserArchitecture
ApplicationArchitecture
DataArchitecture
POLICY
P r o du c er C om p en s atio nC la im a nt Cla im B u sin e s s P ar tn e rsP r o du c erS e r vic e P r ov id er s
P o lic y Fin a n cia lsI n su re d O bje c t s I n su ra n ce Pr od u ctP o lic y
T r ain in g , E du c atio n , A d vic eT h ir d P ar tie s I n qu irie sL e g al & R e co v er y A ctio n sE x te r na l Ag e nc ie s
C la im
S p o ns o rin g O r ga niz a tio nM ar k et P r o sp e ct sI n su re d P ar tyB u sin e s s P la n s
Info Objects
Business Architecture
Corporate StrategyFinance & PlanningHuman ResourcesInformation SystemsPurchasing & Supply
Marketing& Sales
Technical Operations
FlyingOperations
CustomerService
ManageCargo
DevelopProduc ts
Develop Schedules
Distribute Produc ts
ManageAgency Sales
ManageA lliances
ManageAer oplan
ManageA ircr af t Seat Inventor y
Perf orm Base Maintenance (A /C)
Perf orm Line Maintenance
MaintainEngines
MaintainComponents
Manage Mater ials & Ser vice
Plan Crews
ScheduleCr ew s
ManageIn- flightServ ice
ManageDay-of -f lightOperations
Serv iceReservations
Process PAX at Air ports
Process Baggage
ManageA irport SystemsOperations
Perf orm Base Maintenance (contract)
Financial Planning & Repor ting Manage
Labor Contr ac ts
TechnologyArchitecture
Application Function Model
EA Part 1 | Hans-Peter Hoidn 62
Enterprise IT Architectures
© Copyright IBM Corporation 2007
V. Case 3 – Creata
EA Part 1 | Hans-Peter Hoidn 63
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 64
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Case 3 – Creata: a retail company
In the business since a long time- Has grown by acquisition- Has ambitious goals- But not yet the appropriate infrastructure
Case Study- Work out early drafts of Enterprise Architecture Work Products- Mainly
Define Enterprise Architecture PrinciplesDevelop an Enterprise Architecture Overview DiagramWork out Enterprise Capability Network (Review web-sites in the Appendix)
EA Part 1 | Hans-Peter Hoidn 65
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Principles- Cost-sensitive- Desire to custom develop software
solutions to provide strategic differentiation
- They want to focus on the application services rather than infrastructure services
- Its an SMB customer
Architecture Overview- Existing apps:
Microsoft Great Plains for finance/PO’s etcMany Lotus apps incl emailProduct lifecycle management
- Look at strategic capabilities work product
Strategic Capability Network- Review web-site for clues (provided in
Appendix)- What IT resources can IBM provide to
support key capabilities- It’s an SMB customer!
It’s an SMB (Small & Medium Business) customer!
Hints
EA Part 1 | Hans-Peter Hoidn 66
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Points to consider:- SMB- Cost-sensitive- Desire to custom develop software solutions to provide strategic
differentiation- They want to focus on the application services rather than infrastructure
services
Template- Principle:- Motivation:- Implication:
1) Define enterprise architecture principles
EA Part 1 | Hans-Peter Hoidn 67
Enterprise IT Architectures
© Copyright IBM Corporation 2007
2) Develop an enterprise architecture overview – based on as-is Architecture
EA Part 1 | Hans-Peter Hoidn 68
Enterprise IT Architectures
© Copyright IBM Corporation 2007
Creata AppendixThis section contains screen prints of
the case study website
EA Part 1 | Hans-Peter Hoidn 69
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 70
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 71
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 72
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 73
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 74
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 75
Enterprise IT Architectures
© Copyright IBM Corporation 2007
EA Part 1 | Hans-Peter Hoidn 76
Enterprise IT Architectures
© Copyright IBM Corporation 2007