|
Coherent Enterprise Architecture (CEA)
|
| The
draft version of Coherent Enterprise Architecture (CEA) suggests that EA
is the effort to align information solution to enterprise
business. EA is the mapping between technology and
business. It is not about technology nor does it about
business either. LEA is light by looking at enterprise
commonality rather the heavy approach of central planned
dictatorship. It is a the discipline to
see the big picture and know the enterprise business, learning experiences
of the others and establish common foundation and
building blocks to enable the agility and
simplicity of business transformation as shown in the following
chart. The goal is to support business transformation in time
of need rather drawing pie in the sky. It is a very different direction from the
concept that EA is to "Architect the
Enterprise", but it makes more sense. Because of
that the challenge of
business transformation is due to lack of agile and simple
solution rather than lack of another business
transformation method in addition to industry
engineering, information engineering, business process
reengineering, continuous improvement, enterprise engineering
and more. Hopefully, EA do not share the same "come
and go" fade as many business improvement initiative. Please
click on the following figure to go the draft e-book. |
|
|
|
Part 0 : The EA paradigm
|
|
Light Enterprise Architecture include the discipline to see the big picture and
know the enterprise. It enable agility and simplicity of automation by establish common foundation and building blocks via
the engineering of reuse and sharing. It is an effort to help the business
owners to learn experience of the others and locate reusable resources via
reference models.
|
|
Part 1
: LEA Methodologies
|
|
EA industry use frameworks and Models to describe EA
methodologies. This section describe several popular EA
methodologies. LEA distinguish different categories EA models, EA artifact
framework and EA design framework and EA operation framework. A
set of LEA framework and models are developed to describe the LEA
methodologies.
|
|
Part 2
: LEA to overcome the
challenge of buy-in
|
|
Buy-in from the stakeholders is the major challenge of EA. LEA suggest to
overcome the challenge with Governance to establish standards via consensus and
compliance to enforce the standards. The governance processes establish EA standards which include
performance, business processes, application services, data and technology
standards. The compliance processes consist of the integrated Capital
investment, project management, procurement, configuration management
and system lifecycle development. Enterprise Architecture is not a static
architecture, it evolves via the governance and compliance processes to support
the enterprise strategic direction. EA is known to be stealth due to lack of proper communication mechanism. LEA
suggest to adopt the traditional architecture drawing approach where each
architecture, in modern language, serve as a container to convey architecture in a comprehensive and certifiable manner. Many LEA
architecture drawing sets are developed such as the EA Map set, Business
architecture set, Application architecture set, Data architecture sets and the
technology architecture sets.
|
|
Part
3 : Know the enterprise
and see the big picture
|
|
The key of EA for the
challenge of stovepipe system is to see the big picture and know the
enterprise business. Enterprise is large and beyond comprehension, EA
use Models, framework and enterprise topology and business architecture to
render the invisible enterprise for every one to comprehend.
An important value is to preserve the enterprise knowledge by tracking the
enterprise environment similar to a radar screen, Take the snap shot to maintain
the enterprise baseline and analyze the enterprise statistics for cost
estimation and risk management.
|
|
Part
4 : Analyze Enterprise
Business Architecture
|
|
Business architecture is the effort to analyze the enterprise in a systematic
approach to identify the structure of enterprise missions, functions,
information, people, location and workload . The business architecture
further analyze the relation between the enterprise attributes. The
business architecture ,on one hand , serve as the engineering requirements for
solution architecture. On the other hand, the business architecture subject to
business transformation effort which is a different paradigm.
|
|
Part
5 : EA enable agile and simple information age solution
|
|
Stovepipe systems requires significant time and effort due to redundant effort.
EA enable agility and simplicity of automation solution by learning experience
of the others, the engineering of reuse via standardization, the engineering of
consolidation via common foundation. Human have the unique capability to learn experience of the others but
decline to do so. EA is the discipline to awake the capability of leaning
the experience of the others. Enterprise architects have established broad
knowledge of reuse and sharing resources and specialized in facilitating the
business owners to know and make use of experience of others. EA have
created many different reference models, for example, the US OMB FEAPMO
reference models of BRM, SRM, DRM and TRM.
|
|
Part
6 : The engineering of Reuse
|
|
Reuse does not just happen, it is the result of engineering. Reuse is
based on repeatable patterns via standardization over technical standards,
application standards, data standards and process standards. The
engineering of reuse is an logical architecture effort.
|
|
Part
7 : The Engineering of Consolidation
|
|
Consolidation is the effort to establish common services which does not consist
of infrastructure services but also application services (SOA) and data
resources. The engineering of consolidation is a physical architecture
effort driven by workload analysis and performance requirements.
|
|
Part
8: Stakeholder earn agility and simplicity via compliance
|
Agility and simplicity must be earned via compliance to enterprise standards
and sharing common resources. EA governance and compliance is not a burden, it
is the price to pay for the convenience for agile and simple approach to
leverage on technology evolution and overcome the complexity of large system
architecture.
|
|
Part 9 :
Incremental Enterprise Architecture Approach
|
|
Light EA is a continuous EA approach. The high level Target architecture serve as the enterprise framework rather than
the enterprise blueprint. The enterprise carry out the target
architecture plan base on their business performance gap by identifying their
segment of weakness. Upon which, the architect design the target segment
architecture, analyze the architecture gap and plan the segment architecture
transition.
|
|
Part A
: LEA Management
|
|
The EA roadmap lay out the stages of EA which include the EA initiation, EA
preparation and EA operation
|
|
Part B
: LEA Management Planning
|
|
EA management is the effort to manage the EA program which initiate the EA
program office, establish EA resources which include EA budget, funding and EA
skill. EA management deliver the value of EA to the stakeholders and mange
culture transition from stovepipe culture to EA culture.
|
|
Part
C : LEA
Management Leverage on automation
|
|
LEA Management, to eat their own dog food, leverage on automation with the integration of EA repository and the EA
management, governance processes and compliance processes automation. LEA
management automation eliminate the delay and burden of governance and
compliance processes. It is consider as the LEA management
infrastructure.
|
|
Part
D : The initial phase of
LEA
|
|
The initial phase to EA started by knowing the enterprise, EA awareness, plan
the high level target architecture, learn the right experience from the other,
establish initial standards and common resources, deliver the initial
benefit of EA to stakeholders.
|
|
Part
E : The EA operation phase
|
|
EA is an incremental and continuous operation rather than a specific project
as an application development project.
|
|
Part
F : Address business need with segment architecture
|
|
LEA operation is the continuous to address enterprise business performance gap
via segment architecture.
|
|
Part
G : LEA operation via governance and compliance
|
|
LEA operation consist of the governance activity to establish architecture
standards and the compliance activity to enforce the standards for the purpose
of agile simple approach in taking advantage of information technology
evolution.
|
