Enterprise Architecture's Identity Crisis: Caution Sign ...mitiq.mit.edu/IQIS/Documents/CDOIQS_201077/Papers/01_05_T2C.pdf · Enterprise Architecture's Identity Crisis: Caution Sign

Enterprise Architecture's Identity Crisis: Caution Sign for the EA/IQ Relationship ABSTRACT The professions of Enterprise Architecture and Information Quality have a potentially rewarding, symbiotic relationship. But that relationship may be threatened by a trend the author has observed within, and on the periphery of, the Enterprise Architecture world. That trend takes the form of a growing identity crisis: In the beginning it seemed that outsiders didn’t know who we Enterprise Architects were; now it almost seems that we ourselves don’t know who we are. Who is one and who is not one? Almost every job title now has the word “architect” added onto it. Does anybody care? Yes! The author cares, for this reason, among others: When so many job titles are called “architect,” there is confusion between Enterprise Architects and everyone else. Everyone who examines at least one aspect of an enterprise (e.g., the data, or the systems, or the business processes) is likely to be considered an Enterprise Architect. But the true Enterprise Architect looks at the whole, well... enterprise. In the same way, Information Quality permeates many, if not all, aspects of an enterprise. In order to take advantage of all the synergies between Enterprise Architecture and Information Quality, Information Quality professionals need to seek out and interact with true Enterprise Architects, who have the full picture of an enterprise, in addition to working with the data architects and data modelers. BIOGRAPHY P. Kathie Sowell President Custom Enterprise Solutions, LLC Ms. Sowell is a recognized leader in Enterprise Architecture, having been the principal author of the Department of Defense’s original architecture framework, the C4ISR Architecture Framework (later renamed the DODAF), and a principal developer of other frameworks for Government and Industry. She has been named one of the five Pioneers of Enterprise Architecture by the Society for Information Management. She retired from The MITRE Corporation, where she performed a leadership role in Enterprise Architecture for many Government clients. Her expertise has been tapped by NATO Headquarters, the Australian Ministry of Defence, Canadian corporations, the Danish Embassy,

The Fourth MIT Information Quality Industry Symposium, July 14-16, 2010

120

the Swedish military, and State and local governments. She is a frequent speaker at EA conferences. For five years she served as a curriculum developer, Technical Director, and Director of the DoD Division of the Federated Enterprise Architecture Certification Institute (FEAC). For the past several years her SowellEAC program has been providing Enterprise Architect Certification through her company, Custom Enterprise Solutions, and National-Louis University.


121

The MIT 2010 Information Quality Industry Symposium

1

P. Kathie SowellCustom Enterprise Solutions, LLC

SowellEAC Enterprise Architect Certification Programwww.SowellEAC.com

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


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


122


3

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)

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

Is there any such thing as an “enterprise architect?”


4

John Zachman describes it 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, objectarchitect, 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 657 comments and counting– Sad fact: Many commenters, some apparently unwittingly, do as much to solidify

the trend as to fend it off

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


123


5

Where is the “real” enterprise architect?

Data Architect

ApplicationsArchitect

BusinessArchitect

SolutionsArchitectSOA

Architect

EnterpriseSystemsArchitect

EnterpriseApplications

Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect

EnterpriseSoftwareArchitect

ArchitectureArchitect

StandardsArchitect

Reservedfor whatevercomes next

InfrastructureArchitect

5


6

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 network architect is not an enterprise architect.A data architect is not an enterprise architect.An infrastructure architect is not an enterprise architect.

6


124


7

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


8

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


125


9

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!


10

Data Architect

ApplicationArchitect

BusinessArchitect


Architect



Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect



StandardsArchitect



Data Architect

ApplicationArchitect

BusinessArchitect


Architect



Architect

ObjectArchitect

TechnologyArchitect

NetworkArchitect

SoftwareArchitect



StandardsArchitect



So, what is wrong with this picture?

1) There should be an (actual) Enterprise Architect who is concerned with the whole scope

2) The Data Architect should be connected to every other specialty

Enterprise Architect

10

s


126


11

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


12

It is also bad for the synergy between IQ and EA

• By separating “Data Architects” from “Enterprise Architects,” (or by falsely equating the two disciplines) we risk focusing on a too-narrow definition of data/information

• We then risk overlooking the broad nature of the relationship between IQ and EA

12


127


13

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-

Needline InformationExchange Content Sending

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

ClientN/A: client

is an externalnode

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


NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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




NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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


NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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 this

Not this

Not this


14

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




NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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


NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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




NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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


NodeReceiving

NodeSendingActivity

ReceivingActivity

NL 1 1-a

1-b

Requirements

Agreement with

requirements

Client

Bob


node

Select ThemeBob

Criticality(1-3)

1

ClientN/A: client

is an externalnode




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


128


15

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


16

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 infrom the top…every box must have one Outputs go out from

the right...every box must have one

Inputs come in from the left

Mechanisms come infrom 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 infrom the top…every box must have one Outputs go out from

the right...every box must have one

Inputs come in from the left

Mechanisms come infrom the bottom & showwho or what performsthe action

A1

A2

A3

Activity Hierarchy Tree Activity Flow Model

Information flows from activity to activity:

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


129


17

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


18

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

14IQ: Is the required information quality being met?

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

18


130


19

A Scenario Sequence Diagram shows a series of events, and the information 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

NODES BUSINESSNODE 1

BUSINESSNODE 2

BUSINESS NODE 3

INFORMATION EXCHANGED 1time 1

time 3

time 4

time 5

time n

TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n

INFORMATION EXCHANGED 3







GROUND TRUTH EVENT Atime 2

TIME/EVENTS


BUSINESSNODE 2

BUSINESS NODE 3


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


BUSINESSNODE 2

BUSINESS NODE 3


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


BUSINESSNODE 2

BUSINESS NODE 3


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









Scenario Sequence DiagramTIME/EVENTS


BUSINESSNODE 2

BUSINESS NODE 3


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


BUSINESSNODE 2

BUSINESS NODE 3


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


BUSINESSNODE 2

BUSINESS NODE 3


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


BUSINESSNODE 2

BUSINESS NODE 3


time 3

time 4

time 5

time n


TRIGGERING EVENT 4

TRIGGERING EVENT 3

TRIGGERING EVENT 2

TRIGGERING EVENT 1

TRIGGERING EVENT n










19


20

Bottom Line

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

• This is a potentially rich symbiotic relationship between IQ and EA

• To fully realize this potential, Information Quality experts should team with Enterprise Architects, not just with “Data Architects.”

Let’s exploit the full relationship between IQ and EA!Let’s exploit the full relationship between IQ and EA!

20


131