1 P. Kathie Sowell Custom Enterprise Solutions, LLC SowellEAC Enterprise Architect Certification Program Enterprise Architecture’s Identity

1

P. Kathie Sowell

Custom Enterprise Solutions, LLC

SowellEAC Enterprise Architect Certification Program

www.SowellEAC.com

Enterprise Architecture’s Identity Crisis:a Caution Sign for the EA/IQ Partnership

Information Resource Management Association of Canada

April 20, 2011

2

Objectives of this presentation

To warn against a trend in Enterprise Architecture that could have a limiting effect on the symbiosis between Enterprise Architecture and the Information Quality profession

2

3

The Identity Crisis in a Nutshell:

4

Enterprise Architecture is having an identity crisis

• The Enterprise Architecture territory is being carved up into subspecialties – but they all call themselves “enterprise architects.”

• Things that are not even architecture are being called “architecture.”

3

(The profession is too young for a mid-life crisis)

There are 2 symptom of this crisis:

5

This crisis raises two questions:

1. If everyone is an enterprise architect – is anyone an enterprise architect?

2. Is there any such thing as an “enterprise architect?

6

John Zachman describes the crisis this way*

“This is what is killing Enterprise Architecture… every computer programmer, systems designer, software architect, solutions architect, technology architect, computer operator, PC owner, data architect, database architect, network architect, business analyst, systems analyst, enterprise architect, service architect, object architect, project manager and CIO calls whatever they want to or maybe, whatever they are doing, “Architecture.” It is chaos. ...”

- “Yes, Enterprise Architecture is Relative, But It’s Not Arbitrary ” copyright 2009 John A. Zachman, Zachman International www.zachmaninternational.com

• A LinkedIn EA discussion group started a discussion on this quote– There are over 1,000 comments and counting– Sad fact: Many commenters, some apparently unwittingly, do as much to solidify

the trend as to fight it

* “Everybody wants to get into the act” – Jimmy Durante4

7

Where is the “real” enterprise architect?

5

Data Architect

ApplicationArchitect

BusinessArchitect

SolutionsArchitectSOA

Architect

EnterpriseSystemsArchitect

EnterpriseApplications

Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect

EnterpriseSoftwareArchitect

ArchitectureArchitect

Standards

Architect

Reserved

for whatever

comes next

InfrastructureArchitect

Data Architect



Architect



Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect



Standards

Architect

Reserved

for whatever

comes next


s

BusinessArchitect

8

This identity crisis has two seemingly opposite negative effects

• It tends to separate the skill sets from each other– “Data architects” talk to other data architects, “technology architects” talk

to other technology architects.

• Conversely, it tends to confuse the skill sets– People confuse each of these “architects” with an “enterprise architect.”

A data architect is not an enterprise architect.

A network architect is not an enterprise architect

An infrastructure architect is not an enterprise architect.6

9

Who is an enterprise architect, then?

• An enterprise architect is someone who– Holistically examines an organization or other functioning

entity

– Diagnoses current or potential problem areas

– Recommends actions to alleviate or prevent problems or to improve performance.

+=

7

10

An Enterprise Architect’s area of concern is very broad

• An enterprise architect is concerned with all of these aspects of an enterprise– business goals– business processes– business organizations– data structure– data relationships– data standards– data flows– systems– interface standards– applications– services– current state/goal state/transition– performance measures

8

11

And most importantly, an enterprise architect is concerned with the relationships among all the various aspects of an enterprise

This is the hard part, and the most valuable part!

9And this is what makes an enterprise architect an enterprise architect!

So, yes, there is such a thing as an “enterprise architect!”

12

Enterprise Architect

So, what is wrong with this picture?

1) To clarify roles, there should be an (actual) Enterprise Architect who is concerned with the whole scope

10

Data Architect


BusinessArchitect


Architect



Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect



StandardsArchitect

Reserved

for whatever

comes next


Data Architect


BusinessArchitect


Architect



Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect



StandardsArchitect

Reserved

for whatever

comes next


2) To enhance symbiosis between IQ and EA, Data Architects should be aware of how IQ affects other specialties, and how IQ therefore interacts with the overarching discipline of EA

13

Excessive stovepiping of skill sets, and calling everything “architecture,” are bad for EA ...

• Obscures the true role of an Enterprise Architect as one who pulls together the analysis of the whole enterprise

• Makes “Architecture” look like the latest Pied Piper buzzword that everybody wants a piece of (and is therefore suspect)

11

14

This “EA identity crisis” is also bad for the synergy between IQ and EA

• More and more, IQ professionals are being encouraged to work with “Enterprise Architects” to find the true causes and remedies for IQ problems

• But “Enterprise Architecture” is often mistaken for “Information Architecture” (sometimes called “Data Architecture”)

• Information Architecture is only a part of Enterprise Architecture

• So, IQ professionals end up working with Data Architects instead of true Enterprise Architects

12

We risk overlooking the broader relationship between IQ and EA

15

Data Architects tend to emphasize certain aspects of data

13

INFORMATION EXCHANGE MATRIX

VALUE ADDED: INDIVIDUAL INFORMATION EXCHANGESASSOCIATED WITH EACH NEEDLINE, PERFORMANCE REQUIREMENTS FOR INFORMATION EXCHANGES-

NeedlineInformationExchange

ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob

N/A: clientis an external

node

Select ThemeBob

Criticality(1-3)

1

Client


node

N/A: Acceptance Activity outside scope of Activity

Model.Exchange shown only for context

NL 2Bob Ted

BobTed

2a

2-b

Consultationon Presentations


Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

NL 5 5-a Ted AliceSelectedLocation

Select andReserve Venue

ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both


ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node



NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both




ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node



NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both


ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node



NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both

Data Model:

Defines relevant

entities, in terms

of data structure

&

relationships

This

Maybe this

Not this

Not this

Not thisNot always this

Not this

Not this

16

But the true Relationship Between IQ and EA is broader than that

Data Model:

Defines relevant

entities, in terms

of structure &

relationships

IQ is

featured

here

IQ Professionals need to interact with Enterprise Architects toaddress all the ways data is involved in the enterprise 14




ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node

N/A: Acceptance Activity outside

scope of Activity Model.

Exchange shown only for context

NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both


ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node




NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both




ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node




NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both


ContentSending

NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

Client


node




NL 2Bob Ted

BobTed

2a

2-b



Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations

Solicitand Select

Presentations



ArrangeCatering

1

2

2

1

As-Is/To-Be

Both

Both

To-Be

To-Be

Both

IQ can be featured here:

IQ is featured here

IQ is featured here

IQ is featured here

IQ is featured here

IQ is featured here

IQ is featured here

17

Let’s take a closer look at where IQ intersects with EA

• Following slides illustrate some of the EA models referenced earlier and show in more detail how IQ needs to be addressed in each*– Activity Model

– Business Node Connection Model

– Information Exchange Matrix

– Scenario Sequence Model

* Data Model is not shown, because that is well known!

15

18

The Activity Model shows the relevant activities that take place in your enterprise

A0Perform Some

Action

A1Do This Part

of Some Action

A2Do That Part

of Some Action

A3Do Another Partof Some Action

A11

A21 A22 A23A112

A13

A24

A31

A32

A33

Successively decomposes the top-level action into its sub- actions All action names are

verbs A0Perform Some

Action

A1Do This Part

of Some Action

A2Do That Part

of Some Action

A3Do Another Partof Some Action

A11

A21 A22 A23A112

A13

A24

A31

A32

A33

Successively decomposes the top-level action into its sub- actions All action names are

verbs

Do This Partof

Some Action

Successively decomposes the top- level action into its sub- actions For each action of interest, a diagram illustrates the input/outputs between its sub- actions

Do Another Part

of SomeAction

Do That Partof

Some Action

Controls come inf rom the top…every box must have one Outputs go out f rom

the right...every box must have one

I nputs come in f rom the lef t

Mechanisms come inf rom the bottom & showwho or what performsthe action

A1

A2

A3

Do This Partof

Some Action

Do This Partof

Some Action

Successively decomposes the top- level action into its sub- actions For each action of interest, a diagram illustrates the input/outputs between its sub- actions

Do Another Part

of SomeAction

Do That Partof

Some Action

Do That Partof

Some Action

Controls come inf rom the top…every box must have one Outputs go out f rom

the right...every box must have one

I nputs come in f rom the lef t

Mechanisms come inf rom the bottom & showwho or what performsthe action

A1

A2

A3

Activity Hierarchy TreeActivity Flow Model

Information flows from activity to activity:

IQ: Is it the right data, produced by the right activity? 16

19

The Business Node Connection Model shows which enterprise participants need to interact with each other

Business Node 2

(Internal)

Business Node 1

(Internal)

Business Node 3

(External)

Needline 3’Needline 2’

Needline 1’

Needline 4

Needline 5

Subnode 3 Performs:• Action 2




Business Node 2

(Internal)

Business Node 1

(Internal)

Business Node 3

(External)

Business Node 3

(External)

Needline 3’Needline 2’

Needline 1’

Needline 4

Needline 5





Information flows from place to place/person to person:

IQ: Is it coming from the right place, going to the right place? 17

20

The Information Exchange Matrix captures the relevant quality (and other) characteristics of information as it is used in a given enterprise or scenario

14IQ: Is the required information quality being met?

Who needs what information, and the required information quality, may differ by scenario.

18

21

A Scenario Sequence Diagram shows a series of events, and the exchanges that occur in response the to events of a given scenario

Circumstances change in different scenarios.

IQ: How do the different scenarios affect the quality of the information?

TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3

INFORMATION EXCHANGED 1

time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n








GROUND TRUTH EVENT Atime 2

TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n









TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n









TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

Scenario Sequence Diagram

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n










TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n









TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n









TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n









TIME/EVENTS

NODESBUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3


time 1

time 3

time 4

time 5

time n


TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n










19

22

The Bottom Line

• Information Quality touches on all aspects of an enterprise, not just the parts that people think of as “Data Architecture” or “Information Architecture.”

• So does Enterprise Architecture

• There is a potentially rich symbiotic relationship between IQ and EA.

• To realize this potential, Information Quality professionals should team with Enterprise Architects, not only with “Data Architects.”

To solve Information Quality problems,Let’s exploit the full relationship between

IQ and EA!

To solve Information Quality problems,Let’s exploit the full relationship between

IQ and EA! 20

23

Post-Script on the “Enterprise Architecture Identity Crisis”

• There is reason for hope amid the swirling

• Organizations, such as the Center for the Advancement of the Enterprise Architecture Profession (CAEAP), are working toward a consensus definition of what it means to be an Enterprise Architect

• The profession is still relatively young

24

Remember...

“Any man who afflicts the human race with ideas must be prepared to see them misunderstood.

– H.L. Mencken

21

25

Contact Information

• [email protected]

• http://www.sowellEAC.com

mailto:[email protected]

http://www.sowelleac.com/

Documents

1 P. Kathie Sowell Custom Enterprise Solutions, LLC SowellEAC Enterprise Architect Certification Program Enterprise Architecture’s Identity