Enterprise Architecture Business Discipline, NOT Religious ...archive.opengroup.org/public/member/proceedings/q... · The structure of an organization’s logical and physical data

Architecting the Enterprise Limited Copyright © 20099Business Driven Strategic Planning with TOGAF 9

SLIDE 1 of 31

Mike Lambert

Chief Technical Officer

Architecting the Enterprise Limited

[email protected]

Enterprise Architecture

Business Discipline, NOT Religious Ritual


For Millennia People have been puzzled by Stonehenge!

SLIDE 2 of 31


Let’s see whether we can build a level of abstraction

SLIDE 3 of 31


Schematically …

SLIDE 4 of 31

C

Information

System

Architectures

C

Information

System

Architectures


It’s the broken remnants of an EA process

SLIDE 5 of 31

H

Architecture

ChangeManagement

H

Architecture

ChangeManagement

GImplementation

Governance

GImplementation

Governance

E

Opportunities

& Solutions

E

Opportunities

& Solutions

D

Technology

Architecture

D

Technology

Architecture

C

Information

System

Architectures

C

Information

System

Architectures

C

Information

SystemArchitectures

C

Information

SystemArchitectures

BBusiness

Architecture

BBusiness

Architecture

A

Architecture

Vision

A

Architecture

Vision


SLIDE 6 of 31

H

Architecture

ChangeManagement

H

Architecture

ChangeManagement

GImplementation

Governance

GImplementation

Governance

F

Migration

Planning

F

Migration

PlanningE

Opportunities

& Solutions

E

Opportunities

& Solutions

D

Technology

Architecture

D

Technology

Architecture

C

Information

System

Architectures

C

Information

System

Architectures

C

Information

SystemArchitectures

C

Information

SystemArchitectures

RequirementsManagement

RequirementsManagement

BBusiness

Architecture

BBusiness

Architecture

A

Architecture

Vision

A

Architecture

Vision

PreliminaryPreliminaryThe original intent is lost

The detailed requirements are lost

The practical usage is lost


All we are left with is some broken building blocks… and some rituals

SLIDE 7 of 31


How does your Business view Architecture?

► Driven by the Business

► Something that is core to the

strategic planning of the

enterprise

► Business activity driven by

highly respected professionals

► A flexible discipline that

reacts to the needs of the

business

SLIDE 8 of 31


Or maybe …

SLIDE 9 of 31

► Driven by The IT people

► Something that IT does

► Some kind of strange ritual

that happens in an office

somewhere in IT

► A straightjacket that gets in

the way of doing the “right

thing”

► Will you be left with some

broken building blocks and a

set of rituals?


Some important questions

►Where are the solutions?

►Must we do it just because EA

says so?

► Is the architecture always right?

► How do we make the right

decisions?

SLIDE 10 of 31


What about TOGAF?

► TOGAF started life as

■ A prescriptive process

■ Technology focussed

► TOGAF 9

■ Flexible process

■ Business driven

► Rather like old wallpaper, history

sometimes shows through

SLIDE 11 of 31


Some echoes from the past …

SLIDE 12 of 31

First phase directly concerned with how the Target Architecture will be implemented

It is important to note that this effort is not

concerned with database design

It is important to note that this effort is not

concerned with applications systems design.


But TOGAF 9 is Pragmatic and Business Less

SLIDE 13 of 31

► I am going to use extracts from the

TOGAF 9 specification to illustrate my

arguments

■ Definitions

■ Process

■ Models


Solutions – The Elephant in the Living Room for Architects

► We often know the preferred solution

before we start the process

► Often, an existing “legacy” system is not

subject to change

► We are constrained by the structure of

products available in the market

► It is the Data and Application Solutions

that establish requirements for

infrastructure

SLIDE 14 of 31


Evidence from TOGAF 9 – The Process

SLIDE 15 of 31

Select Reference Models, Viewpoints and Tools

Develop Baseline Business Architecture Description

Develop Target BusinessArchitecture Description

Perform Gap Analysis

Define Roadmap Components

Resolve Impacts across theArchitecture Landscape

Conduct Formal Stakeholder Review

Finalize the Business Architecture

Create Architecture Definition Document

� Define roadmap components appears in every phase (not just in phase E)

� At every phase we are thinking about the deployment of the architecture� Business process changes� Changes to database� Changes to applications� Changes to technology


Evidence from TOGAF 9 – Definitions

SLIDE 16 of 31

Data Architecture

The structure of an organization’s logical and

physical data assets and data management resources

Applications Architecture

A description of the major logical grouping of

capabilities that manage the data objects necessary to process the data and support the business.


Evidence from TOGAF 9 – The Metamodel

SLIDE 17 of 41


Evidence from TOGAF 9 – The Metamodel

SLIDE 18 of 31


The (almost) unstated question

SLIDE 19 of 31

Services

LogicalComponent

How are services groupedinto logical components?


The (almost) unstated answer

SLIDE 20 of 31

Services

LogicalComponent

Physical

Component

Deployed

Solution

How are services groupedinto logical components?

�Products available in the market

�Structure of existing components to be carried forward


Must we do it just because EA says so?

► That is what ACMM level 5 says,

right?

SLIDE 21 of 31

� No unplanned IT investment or

acquisition activity.

� Architecture documents are used by

every decision maker in the

organization for every IT-related

business decision.

� Architecture process metrics are used

to optimize and drive business linkages.

Business involved in the continuous

process improvements of Enterprise

Architecture.

US Department of Commerce (DoC) enterprise Architecture

Capability Maturity Model (ACCM Version 1.2 December 2007)


Must we do it just because EA says so?

► Wrong !!

SLIDE 22 of 31

� No unplanned IT investment or

acquisition activity.

� Architecture documents are used by

every decision maker in the

organization for every IT-related

business decision.

� Architecture process metrics are used

to optimize and drive business linkages.

Business involved in the continuous

process improvements of Enterprise

Architecture.

� A standards and waivers process is

used to improve the architecture

development process.

US Department of Commerce (DoC) enterprise Architecture

Capability Maturity Model (ACCM Version 1.2 December 2007)


Can you relate to this?

► We follow the TOGAF Architecture

Development Method

► We build a long list of projects that would

result in the perfect architecture

► We ask for a gazillion dollars to complete

the implementation

► We are surprise when the money is not

forthcoming

SLIDE 23 of 31


The EA Process Defines the Ideal Target State

► At every stage, the EA process establishes

the way we would like to operate

■ Consistent business processes

■ Integrated databases

■ Common use applications

■ Shared infrastructure

SLIDE 24 of 31


At every stage, we have two decisions

► What is the strategic approach for the future?

► Is there a business case for tidying up the legacy

of the past?

■ Building the business case is a non-trivial task

■ How do we quantify the future value of synergy

► Some considerations

■ Expected life-time of system

■ Relationship to core of business

■ Stability of business area supported

SLIDE 25 of 31


Every decision is business driven

► Will it help us increase revenue?

► Will it help us reduce costs?

► Will it help us improve customer service?

► What is the impact on the share price?

SLIDE 26 of 31


Is the architecture always right?

► May not be practical

■ Very expensive, no business value

■ May not be possible to implement

► May be too forward looking

■ Particularly non-functional qualities,

such as volumes and performance

► May be simply wrong

■ Simply doesn’t achieve objectives

SLIDE 27 of 31


A Practical Architecture Needs A Dispensation Policy

► Used to ensure that service and operational

levels are met while providing flexibility in

their implementation and timing

► Granted for a given time period and set of

identified service and operational criteria

that must be enforced during the life-span of

the dispensation

► Not granted indefinitely, not granted

automatically

► Time-bound nature ensures that they are a

major trigger in the compliance cycle

► Patterns of dispensations drive architecture

change

SLIDE 28 of 31


How do we make the right decisions?

► To be effective, and Enterprise Architecture must be SEEN to be

REALISABLE and REALIZED

■ Must be visible

■ Must be practical .. Which is why considering potential solutions is so

important

■ Most be a discipline that is followed

■ Every decision must be a considered decision

■ Everyone needs to know what decisions they may make and which they may

not

SLIDE 29 of 31


Much of this is NOT NEW

► There are people in our Enterprise who are

good at this

■ Business planners

■ Risk managers

■ Project and Portfolio Managers

► Enterprise Architecture must be integrated

into established business disciplines

► We must have a framework to ensure

consistency of decisions

■ Trade-offs

■ Compliance policy

● When dispensatioms may be granted

SLIDE 30 of 31


Governance

► Decisions need to be taken in a

controlled way

► Must consider the value to the

enterprise, not just to one single

organization unit, not just within a

single project

► Must have the basis for taking

difficult decisions in place BEFORE the

decision has to be taken

SLIDE 31 of 31

CorporateGovernance

ArchitectureGovernance

ITGovernance


SLIDE 32 of 40

Actioning Architecture Governance in the ADM

HArchitecture

Change

Management

HArchitecture

Change

Management

G

Implementation

Governance

G

Implementation

Governance

F

Migration

Planning

F

Migration

PlanningE

Opportunities

& Solutions

E

Opportunities

& Solutions

D

TechnologyArchitecture

D


C

Information

SystemArchitectures

C

Information

SystemArchitectures

CInformation

System

Architectures

CInformation

System

Architectures

Requirements

Management

Requirements

Management

B

Business

Architecture

B

Business

Architecture

A

ArchitectureVision

A

ArchitectureVision

PreliminaryPreliminary� Architecture Governance

Framework is implemented

which identifies processes,

artifacts, controls and

environment

� Cross-organizational

Architecture Board established

to oversee the implementation

of the IT governance strategy

� An Architecture Compliance

strategy is adopted with specific

measures to ensure compliance

with the architecture


SLIDE 33 of 40


HArchitecture

Change

Management

HArchitecture

Change

Management

G

Implementation

Governance

G

Implementation

Governance

F

Migration

Planning

F

Migration

PlanningE

Opportunities

& Solutions

E

Opportunities

& Solutions

D


D


C

Information

SystemArchitectures

C

Information

SystemArchitectures

CInformation

System

Architectures

CInformation

System

Architectures

Requirements

Management

Requirements

Management

B

Business

Architecture

B

Business

Architecture

A

ArchitectureVision

A

ArchitectureVision

PreliminaryPreliminary

� Each phase is governed by

Principles applicable to the

activities of the phase.


SLIDE 34 of 40


HArchitecture

Change

Management

HArchitecture

Change

Management

G

Implementation

Governance

G

Implementation

Governance

F

Migration

Planning

F

Migration

PlanningE

Opportunities

& Solutions

E

Opportunities

& Solutions

D


D


C

Information

SystemArchitectures

C

Information

SystemArchitectures

CInformation

System

Architectures

CInformation

System

Architectures

Requirements

Management

Requirements

Management

B

Business

Architecture

B

Business

Architecture

A

ArchitectureVision

A

ArchitectureVision

PreliminaryPreliminary� Recommendations are

formulated for each project

� Used to construct an

architecture contract to govern

system implementation and

deployment

� Compliance reviews carried out

at key milestones


Establish Cross-Enterprise Architecture Board

► Ensures all decisions are based on the interests of the

enterprise not one group with a vested interest

► Probably a hierarchical structure of such boards

► Representative of major stakeholders

► Establishes clear responsibilities and accountabilities

SLIDE 35 of 31

Regulatory/legal bodies

Demand forecasting Standards organisations

Organisation management

Governance working groupsService provider(s)

Global/regional governanceboards

Asset/contract management

Repository management

Service/technologyproviders

Tracking

Control andguidance

Guidance

GuidelinesFinancial

Transition/transformationmanagement

Service provision

Change

managementConformance

Enablementand

validation

Provision monitoring

Cost

effectiveness

Governance organisation

Escalation anddispensation

Compliance

Integrationand

Reporting

Expertise andCostStatutory

Obligations

EnterpriseGovernance


Some important questions



says so?



decisions?

SLIDE 36 of 31


Some important answers


■ Solutions are everywhere and

guide thinking towards practical

architectures


says so?

■ No, not if it doesn’t make business

sense


■ No, architects are human


decisions?

■ Business driven governance

SLIDE 37 of 31


SLIDE 38 of 31

Mike Lambert

Chief Technical Officer

Architecting the Enterprise Limited

[email protected]

Enterprise Architecture

Business Discipline, NOT Religious Ritual

Enterprise Architecture Business Discipline, NOT Religious ...archive.opengroup.org/public/member/proceedings/q... · The structure of an organization’s logical and physical data

Documents