|
|
|
Present to |
|
The Association of Enterprise Architects , DC |
|
By John Chi-Zong Wu |
|
August 13 , 2008 |
|
WWW.CoherentEA.com |
|
Peaitce@yahoo.com |
|
|
|
|
|
The presentation goal : |
|
Suggest the Coherent Enterprise Architecture
method to build consensus on EA definition. |
|
Establish the future direction of EA. |
|
|
|
Scope of presentation : |
|
The CEA Model (Why) |
|
The CEA framework (What) |
|
The CEA approach (How) |
|
Segment Architecture |
|
|
|
|
|
Webster's definition of an architecture is "an
orderly arrangement of parts." |
|
Coherent is “having a natural or due agreement
of parts; harmonious: a coherent design.” |
|
Coherent EA
is defined as |
|
“ CEA is the coherence between Business
Architecture, Alignment Architecture and Agility Architecture. It is an
incremental and continuous effort to architect Enterprise businesses, align solution to business and enable
Agility to manage change in time of need.” |
|
|
|
|
EA has not evolved as expected due to lack of
consensus on EA definition. |
|
CEA builds consensus on EA definition by putting
the Business Architecture, System Architecture, Agility Architecture,
Strategic Planning and Segment Architecture into the proper aspect. |
|
EA is the coherent effort of different EA
directions with proper level of effort instead of business centric or Information Technology centric. |
|
|
|
|
The CEA model illustrate the concept of CEA
which consist of Business Architecture (X), Alignment Architecture (Y) and
Agility Architecture (Z). |
|
|
|
Segment Architecture carry out EA in a
incremental and continuous manner to closed business performance gaps. |
|
|
|
|
Enterprise Architecture (EA) has a very
different characteristic from System Architecture (SA) as shown in the
following table. |
|
|
|
|
|
|
Amoeba keeps changing to find food, Enterprise also keeps evolving to win
competitive edge. |
|
It is futile to design EA in a big bang approach
which become obsolete before the ink dry. |
|
Enterprise Architecture is to architect with
holistic consideration rather design the big house for enterprise. |
|
Enterprise Architects must understand the nature
of changing in an Enterprise while applying architecture principle to
business. |
|
|
|
|
Agility Architecture which align services to
business need, is the effort to manage change in time of need. |
|
It covers the engineering of reuse and
consolidation via reference models, service oriented architecture (SOA) and
reference architecture. |
|
Traditional EA approach embed the design of
agility in term of reuse as the sidekick of EA. |
|
CEA incorporate the architecture of agility as
one the three pillar of EA. |
|
|
|
|
|
|
CEA Framework is derived form the CEA model. |
|
It lay out the attributes and structure of
business architecture, Alignment Architecture and Agility Architecture. |
|
Leverage on the traditional Enterprise
Architecture framework. |
|
Introduce the Architecture of Agility. |
|
The following slides elaborate each dimension. |
|
|
|
|
Business Architecture to see the big picture,
know the enterprise and transform the business. |
|
Define the enterprise from mission, function
information, organization, location and
performance requirement . |
|
Business architecture analyze the relation and
structure of enterprise attributes. |
|
Business processes provide the process solution
to Enterprise mission. |
|
Business performance gap analysis is part of
Business Architecture effort. |
|
|
|
|
|
|
|
|
|
Alignment architecture is the effort to align IT
solution with business need . |
|
Align Business processes to business. |
|
Align Application to business. |
|
Align Data to business. |
|
Align Technology to business. |
|
|
|
|
Agility architecture enable agility by learning
from the same line of business. |
|
Enable agility via cross-cutting solution. |
|
Cross-cutting solution via the engineering of
reuse and consolidation. |
|
Stakeholders comply with standards to earn
agility. |
|
|
|
|
|
|
|
|
Enterprise change at different level. Similar to
water flow in a open channel. |
|
The high level target EA remain steady similar
to a city plan. |
|
The segment EA, respond to business performance
gaps, change incrementally and gradually. |
|
The solution architecture change rapidly due to
the rapid technology evolution. |
|
Agility Architecture to establish the building
blocks which change slowly. |
|
|
|
|
|
CEA approach is based on the profile of
enterprise change. |
|
Develop the notional Enterprise Target
Architecture |
|
Enable agility and simplicity via learning
experiences from the same line of business. |
|
Business performance gap analysis is a
continuous effort. |
|
Segment architecture to elaborate the notional
target architecture and close business performance gaps. |
|
|
|
|
Enterprise Target Architecture is notional as
the high level master plan for the
enterprise rather than the enterprise architecture blueprint. |
|
Analogy to a city plan, it is the fundamental
principle for the Enterprise. |
|
The notional Enterprise Target Architecture
consist of the conceptual business architecture, data architecture and
application architecture. |
|
|
|
|
|
|
Enable agility and simplicity via establishing
common services as shown in the following figure. |
|
Agility increase with the level of common
services. |
|
Establish common services by learning
experiences from the same line of business. |
|
|
|
|
|
|
Segment Architectures are initiated to close
business performance gaps. |
|
It is not an effort of architecture convenience
to put similar effort together in a
“Birds of the same feather” approach. |
|
Enterprise analyze performance gap continuously. |
|
The 1993 Government Performance and Results Act
(GPRA) requires performance based strategic planning. |
|
|
|
|
|
|
|
|
The following figure from OMB FEAPMO illustrate
the relation between enterprise architecture, segment architecture and
solution architecture. |
|