|
|
|
By John Wu |
|
WWW.liteEA.com |
|
Peaitce@yahoo.com |
|
|
|
|
|
A coherent EA is |
|
The
effort to align IT solutions with information age Enterprise and provide EA
value at the right time. It is not only about architecture plan but also
the capability to manage ambiguity. |
|
|
|
|
|
|
|
|
|
|
|
|
EA is the coherence of business transformation,
system architecture and enable agility. |
|
System architecture centric resulted “paralysis
by analysis”. |
|
Business transformation centric to “come and
go”. |
|
Agility is enabled based on business and
solution. |
|
EA value is delivered incrementally via segment
architecture |
|
|
|
|
High level business modeling and solution
alignment effort to enable ability |
|
Enable agility by establishing common standards and building blocks |
|
Identify the standards and building blocks from
the same line of business. |
|
Deliver the value of EA by segment architecture
based on business need. |
|
|
|
|
|
|
US OMB FEAPPMO approach with consolidate
reference models and segment architecture approach. |
|
|
|
|
A coherent EA is modeled in the dimension
of Enterprise definition, Align
solution to business, and enable agility. |
|
The three direction work toward the same goal. |
|
|
|
|
|
|
|
Coherent approach by coordinating the proper
level of effort in business architecture, solution alignment and the agility at the high level planning
and drill down by segment architecture. |
|
The Coherent Approach |
|
High level Business Architecture to identify the
common line of business. |
|
High level Solution Alignment to establish the
master solution plane. |
|
Establish standards and building blocks form the
same line of business. |
|
Elaboration business architecture and solution
alignment by each segment based on business need. |
|
|
|
|
|
|
|
|
|
|
|
EA must know the enterprise and see the forest. |
|
See the forest is a collaboration effort
because: |
|
Enterprise is large. |
|
Enterprise is logical. |
|
|
|
|
|
|
Business Modeling |
|
Business transformation to information age
enterprise. |
|
High level effort to identify common Line of
Business (LOB) for commonality. |
|
|
|
|
|
|
|
|
Align IT solution to business need. |
|
High level Solution alignment to establish the
master plan for commonality. |
|
|
|
|
Align IT solution to business need. |
|
High level Solution alignment to establish the
master plan for commonality. |
|
|
|
|
|
|
Agility to manage ambiguity. |
|
Agility to EA practicality for in time need. |
|
Agility, simplicity and practicality do not just
happen, it must be designed. |
|
Agility is established via cross-cutting solution. |
|
|
|
|
|
|
|
|
|
Cross-cutting solution among different
stakeholders raise the following
challenges. |
|
Communication. |
|
Learn experience of the others. |
|
Reuse. |
|
Consolidation. |
|
Buy-in from the stakeholders. |
|
|
|
|
|
|
|
|
Learning experience of the other is the key for
agility. Do not reinvent wheel ! |
|
Human have the unique capability to learn
experiences of the others but decline to do so. |
|
Learn Experience base on enterprise line of
business from the high level business architecture. |
|
|
|
|
|
|
Learn Experience from the similar LOB enterprise
in the high level business
architecture. |
|
Learning the right experience of the other via
reference models. |
|
|
|
|
|
|
Enable agility & simplicity via engineering
of reuse and consolidation. |
|
Engineering of reuse via repeatable pattern and
standardization. It is more logical architecture. |
|
Engineering of consolidation base enterprise
wide workload and performance requirements, it is more physical
architecture. |
|
|
|
|
Engineering of reuse via repeatable pattern. |
|
Implement reuse via standardization. |
|
Standardization for interoperability. |
|
|
|
|
Reuse based on repeatable pattern. |
|
Implement reuse via standardization. |
|
Standardization for interoperability. |
|
EA establish standards via building consensus
similar to the political process to establish the law. |
|
Establish standards base on business need. |
|
Establish the enforceable standards. |
|
|
|
|
|
|
Engineering of Consolidation base on workload and performance
requirement. It is more
physical architecture. |
|
Agility and simplicity increase with the level of common foundation. |
|
|
|
|
The service oriented EA consist of the
application services, infrastructure services and the data services similar
to the hot dog and bun. |
|
In the analogy of a city, the infrastructure
service is analogy to the roads, the application service is analogy to the
buses and the data services is analogy to water company. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|