Enterprise IT Architectures Enterprise Architecture (EA ...00000000-10dc-ddaa-0000-00003996c… ·...

© 2011 IBM Corporation

Enterprise IT Architectures

Enterprise Architecture (EA) – Level Set

Dr. Hans-Peter HoidnExecutive ArchitectIBM Software Group

© 2011 IBM Corporation2


I. Positioning Enterprise Architecture (EA)

II. Enterprise Architecture – Methodologies

III. Enterprise Architecture – Architectures

Agenda



Positioning Enterprise Architecture (EA)



Enterprise Architecture

Doing the right things right



Why EA – “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

Enterprise Architects with a sense of what the enterprise needs to be and do, and how IT should be used in a wider sense

Avoiding results like:



'If you don't know where you're going, any road will get you there.'Lewis Carroll

This house may function, but…

Does it meet business objectives?Is it an ‘Asset Junkyard’?Is it cost effective?Does it fit with the community

(standards)?Is it documented - who knows what it

consists of?Can it be repaired easily or

economically?Can it be adapted to changing needs?

Yesterday’s management approaches are not working in today’s complex and fast-paced environment.

Winchester House Syndrome



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…



Enterprise Architecture provides the vital linkages between “strategy” and “implementation”

System Architecture• functional aspects• operational aspects“the infrastructure and singlebuilding design”

BusinessStrategy


Strategy

BusinessOpportunity


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

!!


IT Solutions

Planning

Design andDelivery

Ente

rpris

e w

ide

focu

sPr

ojec

t foc

us

Strategy



Enterprise Architecture“the city plan”

System Architecture“the building design”

BusinessStrategy


Strategy

BusinessOpportunity


ITArchitecture

- Applications- Data- Technology

Planning

Design andDelivery

Ente

rpris

e w

ide

focu

sPr

ojec

t foc

us

Strategy


IT Solutions


Transition Plan

BusinessArchitecture

- Processes- Information- People- Locations

Enterprise Architecture embraces both Business and IT Architectures, providing the “city plan” for “building projects”



EAMethods

andTools

Processand

Content Modeling

BusinessStrategy

andPlanning

Enterprise Strategy

Fire and hope!



TransitionPlanning

G ro u p IT A r c h i t e c t u r e D e f in i t io n

I n f r a s t r u c t u re D e s ig n & P la n n i n g

E s t a b lis h IT C o m p e t e n c y C e n t re

E 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 e

In t e r - c o m p a n y W A N ( i m p le .)

O u t s o u r c e N e w C o re s y s t e m s

O u t s o u r c e H e lp d e s k a n d D e s k t o p

O u t s o u rc e n e t w o rk

O u t s o u r c in g I n i t i a t iv e s

C o m p e t e n c y C e n t re In i ti a t iv e s

E l e c t r o n ic S e r v i c e D e li 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

WA N in fr a s tru c tu r e

In tr a n et /M a il in f ra s tr u ct u re

C u s to m e r S e rv ic e

D a ta

Wa re h o u s e

G ra p h ic a l I S

B . U .

B . U .

D o cu m en t M an a g e me n t

S y s te m s Ma n a g e me n t

Mid d le w a r e

N E T W O R K

P la n n in g /D e s ig n In i t i a t iv e s

In f r a s t ru c t u r e In i ti a tiv e s

O t h e rB u s i n e s s U n it S y s te m sK i o s k sT e l e m e t r y s y s t e m se tc

In i t ia t iv 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 liv e ry e n v ir o n m e n t

P la n n in g /D e s ig nI n f ra s t ru c t u reO u t s o u rc in g

In i t ia t iv e s f o c u s e d o n im p le m e n t in g t h e v i s i o n

P la n n in g /d e s ig nI T C o m p e t e n c y c e n tre

K e y G r o u p D e c is i o n P o in t s

ArchitectureGovernance

Bus Arch’ture IT Architecture

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 Locations

Prog

ram

foc

usEn

terp

rise

wid

e fo

cus

Strategy

Planning

Designand

Delivery

Change Programs

Soln Outline Macro Design Micro Design Devt, etc.

Programme ArchitectureG r o u p I T A r c h i te c tu r e D e fi n it io n

I n fr a s t r u c tu r e D e s i g n & P l a n n i n g

E s ta b li s h IT C o m p e t e n c y C e n t re

E n d U s e r In f ra s t ru c t u r e U p g r a d e

In t e r - c o m p a n y W A N (i m p le .)

O u ts o u r c e N e w C o r e s y s t e m s

O u ts o u r c e H e lp d e s k a n d D e s k t o p

O u ts o u r c e n e tw o r k

O u t s o u r c i n g I n i t ia t iv e s

C o m p e t e n c y C e n t r e In i t ia t i v e s

E l e c t r o n ic S e r v ic e D e li v e r y


C u s to m e r S e r v ic e C e n t r e

W AN infr astr uctu reI ntra net/ Mai l inf rast ruct ure

C ust om er S ervic eDat a Wa reho use

Gra phic al I S

B. U. B.U .

Do cu men t M ana gem en t

Sys tem s M an age me nt

Mid dle war e

N E T W O R K

P l a n n i n g / D e s i g n In i t ia t i v e s

I n f r a s t r u c t u r e I n i t ia t iv 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 ro 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 in 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 is io n P o in t s


Programme 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 re

E n d U s e r I n f ra s t ru c t u r e U p g r a d e

I 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 ia t iv e s

C o m p e t e n c y C e n t r e In i t ia 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



W AN infr astr uctu reI ntra net/ Mai l inf rast ruct ure

C ust om er S ervic eDat a Wa reho use

Gra phic al I S

B. U. B.U .

Do cu men t M ana gem en t

Sys tem s M an age me nt

Mid dle war e

N E T W O R K

P l a n n i n g / D e s i g n In i t ia t i v e s

I n f r a s t r u c t u r e I n i t ia t iv e s


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 ro 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 in g



K e y G r o u p D e c is io n P o in t s


BusinessOpportunity

Bus Strategy IT Strategy

Processes Content

SOA

Solution Design

andDelivery

Bridging the Gap Between Strategy and Delivery



“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 and IT domains

“neutral phrasing”: EA works at many

levels

EA provides reference material in

many forms

Enterprise Architecture: defines the building blocks needed to underpin the portfolio of programs



Current Enterprise Planning and Control

Business Drivers

Business Drivers

Project BProject B Project EProject E

Project DProject DProject AProject A

Project CProject C

ReportsReportsReportsReports

ProjectPlans

ProjectPlansProject

PlansProjectPlans




Models


ModelsGovernanceGovernanceTransition Planning

Transition Planning

Building blocks, rules,

patterns, constraints

ProjectProject

Projects

Are we still moving in the

right direction?

Are our target architectures still

right?

This is the way things should be

architected

Are we consistently viewing and reporting on

product architectures?

Project Prioritization &

Planning

Project Prioritization &

Planning

These are the things we should do

Are we doing these things the way we said we want them done?

Purpose, objective, vision, etc.

Purpose, objective, vision, etc.

Enterprise Architecture Solution Overview



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




Solution architecture aims to address specific problems and requirements, usually through the design of specific information systems or applications.

Enterprise Architecture is the formal organization (design or layout) of the components, structures and processes required or relevant to the attainment of the goals and visions invested or envisioned in an enterprise.

Enterprise Architecture vs. Solution Architecture



So we recognise two different types of IT Architect…

…Are responsible for ensuring the design of IT based business solutions meet the functional and non-functional requirements, within the constraints of budget, time, skills and other givens (such as IT Standards)

“Solution Architects”

…Are responsible for ensuring an IT Organisation approaches the identification, specification and implementation of these IT based business solutions in a co-ordinated and standardised manner, aligned to the Enterprise’s Business and IT Strategies.

“Enterprise Architects”

…Are generally not product specialists, although they must be able to work at a sufficient level of technological detail to be sure their architectures can be implemented.



Strategy

Architecture

Dev Program

Architecture

Project PP

Architecture

Design DDesign D

Infra. Proj

Arch

D DD


Program Architecture

Infrastructure Architecture

EA provides a context and guidance, keeping everyone “on the same road”



“How have we aligned technology investment with our

business objectives?”

“If we change our technology stack, what applications and organizations will be effected?”

Benefits (1): Analyze the Linkage Between Technology and Business, Communicate Actionable Information



Focus on Information

needed to make

a decision

What Happens If….?

Benefits (2): Analyze Change to Processes…



And only when we can ensure it’s “architecture all the way down”, will we be able to satisfy all our stakeholders

Maximise the overall ROI by aligning all change programs with each other and with the

enterprise's strategic direction

The BoardThose responsible for the overall

ROI for the Enterprise's (IT) investments and projects. (aka Programs Steering Committee)

Minimise project risk and integration challenges,

maximise value of available IT skills and resource. (i.e.

maximise chance of success)

Solution DevelopmentThose responsible for the design

and development of Business & IT systems associated with specific

business requirements

Minimise systems management challenges and product support issues, maximise value gained from IT infrastructure through

shared and flexible deployment.

IT OperationsThe folk who operate the

Enterprise's IT infrastructure

“The Bridge” “The Engineers” “The Engine Room”



Enterprise Architecture – Methodology



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



23

Information Systems

Technology

Strategy

Business


High-level business process blueprintthat supports the strategy

Infrastructure that supports the Information Systems

Define the enterprise strategy, goals and objectives.

Implementation of the business functions in the IT systems

Enterprise Architecture Defined



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



Enterprise Architecture Methods

Enterprise Architecture methods provide guidelines and templates for 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)




Technology Architecture

Governance

Strategic Gap Analysis

Transition

Enterprise Capabilities

IS Architecture

Current Environment

Workshop and Engagement Planning

ClientObjectives

EmergingOpportunities

IBM’s Enterprise Architecture (EA) Framework – Best Practice shows that successful EA Management follows an iterative approach of EA Design



© 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



What is TOGAF

TOGAF consists of the following :– Architecture Development Method (ADM)– Enterprise Continuum– Resource Base

The ADM is depicted as the ‘crop-circle’ and represents the core of the TOGAF specification. It is a method for deriving a specific enterprise architecture.

The Enterprise Continuum is a model for structuring a ‘virtual repository’of architectural assets such as patterns, models, & architecturedescriptions.

The Resource Base is a set of ‘good practice’ resources such as guidelines, checklists and templates provided to assist the architect when using TOGAF ADM.



Standard TOGAF (currently Version 9)

CapabilityRequirements

CapabilityRequirements

Strategy andDirection

Strategy andDirection

Processes, OrganizationProcesses,

Organization

Application,Systems, BPMS

Application,Systems, BPMS

NetworkInfrastructure

NetworkInfrastructure

PrioritizationPrioritizationPlanningPlanning

ChangeManagement

ChangeManagement



Initiates one iteration of the architecture process– Sets scope, constraints,

expectations– Required at the start of

every architecture cycle Validates business context Creates Statement of

Architecture work

Guiding Principles(according to IBM EA

Methodology) Architectural Decisions

(according to IBM EA Methodology)

In more Detail: Capabilities Content (Architecture Vision according to TOGAF - augmented)



In more Detail: Business Architecture Content (according to TOGAF augmented)

Organization structure Business Goals and Objectives Business Functions Business Services Business Processes Business Roles Correlation of organization and

functions. Enterprise Information Model

(according to IBM EA Methodology)



The fundamental organization of an IT system, embodied in– relationships to each other

and the environment, and the principles governing its design and evolution

Shows how the IT systems meets the business goals of the enterprise

In more Detail: IS Architecture Content (according to TOGAF)



The fundamental organization of an IT system, embodied in– its hardware, software

and communications technology

– their relationships to each other and the environment,

– and the principles governing its design and evolution

In more Detail: Technology Architecture Content (according to TOGAF)



Enterprise Strategy


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


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



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


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 g

E 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 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 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


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 g

E 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




Da ta W a rehouse



Graph ical IS



Middle ware

N ET W O RK

Pla nning /D e s ign In itia tiv e s




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




Programme ArchitectureGroup IT Arc hite cture De fin ition

In fra struc tur e De s ign & Pla nning

Esta 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




Da ta W a rehouse



Graph ical IS



Middle ware

N ET W O RK

















Outsourc e ne twork




Da ta W a rehouse



Graph ical IS



Middle ware

N ET W O RK

















Outsourc e ne twork




Da ta W a rehouse



Graph ical IS



Middle ware

N ET W O RK

















Outsourc e ne twork




Da ta W a rehouse



Graph ical IS



Middle ware

N ET W O RK










BusinessOpportunity

Business Strategy IT Strategy


Enterprise Capabilities


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



Along with the Technology Architecture, the IS Architecture represents the “digitised” elements of the EA

Technology Architecture Cha

nnel

s

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

CommonApplication

Services

DataClaim

Business Architecture 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


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 e






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




W A N in f ra s tr uc tu r e

I nt ra n e t/M a i l in f ra s tr uc tu r e

C u s to m e r S e rv ic eD a ta W a r eh o u s e

G ra p h ic a l I S

B .U . B . U .

D o c u m e nt M an a g e m e n t

S y s te m s M an a g e m e n t

M i dd l ew a r 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


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



K e y G r o u p D e c i s i o n P o i n t s

Enterprise Capabilities 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
















G ra p h ic a l I S

B .U . B . U .



M i dd l ew a r e

N E T W O R K









IS Architecture 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
















G ra p h ic a l I S

B .U . B . U .



M i dd l ew a r e

N E T W O R K









Strategic Intent and “value propostions” Capabilities to realise that intent Resources to enable these capabilities

Function, information and human elements of the business

Relationships between these elements

Automated elements of business functionality and business data

Relationships between these elements

Automated elements of infrastructure functionality and data.

Relationships between these elements.

Boundary of Automation

IT

Busi

ness



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




Claim


Info Objects


IT Architecture

TechnologyArchitecture

Enterprise Architecture Framework

Applications

Users

We can develop this way of thinking about an EA architecture framework a little more. First, let us highlight the nature of its layers…


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 Work Products guide and govern how Solution Work Products are constructed (Same Types of Work Products)

“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


UserArchitecture

ApplicationArchitecture

DataArchitecture

POLICY




Claim


Info Objects

UserArchitecture

ApplicationArchitecture

DataArchitecture

POLICY




Claim


Info Objects


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



Ensures AlignmentEnsures Vitality

Ensures Compliance

Strategy

BusinessOpportunity


BusinessStrategy


Strategy

ITArchitecture

ApplicationsDataTechnology


Transition Plan


ProcessesInformationPeopleLocations

Planning

Design andDelivery

Ente

rpris

e w

ide

focu

sPr

ojec

t foc

us Business Operating Environmentand IT Infrastructure

IT Solutions

Enterprise Architecture and Governance (see Architecture Management)

Enterprise IT Architectures Enterprise Architecture (EA ...00000000-10dc-ddaa-0000-00003996c… ·...

Documents

Transcript of Enterprise IT Architectures Enterprise Architecture (EA ...00000000-10dc-ddaa-0000-00003996c… ·...