<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>Light  Enterprise Architecture Web</title>
    <link></link>
    <description>Coherent Enterprise Architecture</description>
    <language>en-us</language>           
    <generator>Nucleus CMS v3.24</generator>
    <copyright>©</copyright>             
    <category>Weblog</category>
    <docs>http://backend.userland.com/rss</docs>
    <image>
      <url>/nucleus/nucleus2.gif</url>
      <title>Light  Enterprise Architecture Web</title>
      <link></link>
    </image>
    <item>
 <title>LEA poster</title>
 <link>index.php?itemid=788</link>
<description><![CDATA[I have created a D size drawing to shar the concept of Light Enterprise Architecture. I also prepare a presentaion to walk through this poster.  Please review and comment. <br />
<br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20120224-poster.jpg">poster</a>  <br />
<br />
The LEA poster in PDF <a href="http://www.liteea.com/nucleus3.24/media/1/20120224-Visio-lea_poster.pdf">The LEA Poster</a><br />
<br />
<a href="http://www.slideshare.net/wuchizong/the-lea-poster">The LEA poster presentation </a>]]></description>
 <category>General</category>
<comments>index.php?itemid=788</comments>
 <pubDate>Fri, 24 Feb 2012 08:11:37 -0700</pubDate>
</item><item>
 <title>What is EA?</title>
 <link>index.php?itemid=787</link>
<description><![CDATA[Instead of debating and arguing "what is EA?" as we have done in many EA discussions, this article, take the advice from the story of "blind man and the elephant" ,  suggest to put together the parts of EA to see what is the big elephant of EA looks like rather than trying  to convince each other on "what is EA?".  As a matter of fact, this is a modern day version of this story. We are relatively blind to the large, logical and invisible enterprise and we all touch a part of enterprise. and we also think the part we have touched is the whole as shown in these EA discussion threads. <br />
<br />
The question of "What is EA?" is not a matter who is right or wrong. The truth is that every one is partially right on "What is EA?" and there is no need to argue.  The challenge is how to put together the parts so that is look like a real elephant.  Here is my shot to put the parts of EA together to see the big elephant of EA.  With the big picture of EA, the EA community will understand how to work together for EA to become an emerging paradigm.  <br />
<br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20120212-ea_bigpicture.jpg">big picture</a><br />
<br />
<br />
The EA big picture is constructed based on the concept that Enterprise is organic, it does not only consist of the enterprise mechanic but also the enterprise dynamic fields of collaboration. After all the hard work to architect the enterprise blueprint, the EA community  discovered that the real challenge is  "lack of buy-in from stake holder". Enterprise is organic, it is futile to architect a frozen blueprint which become obsolete before the ink dry. EA enable the enterprise to adapt change via agility and simplicity. Instead of a  simple vertical architecture approach, The LEA take the vertical top down , horizontal cross cut and iterative segment architecture to adapt change in time of need. <br />
<br />
1. EA must know what is the enterprise. <br />
2. EA does not only architect the enterprise mechanic but also facilitate collaboration, total participation and buy-in.  <br />
3. Adopt structure method to analyze business architecture,<br />
4. The alignment architecture to align business process, human resources and technologies to business need in a vertical direction. EA is not all about IT.  <br />
5. The Cross cutting architecture analyze the enterprise in horizontal direction Reuse, consolidation and enable enterprise agility with SOA.  <br />
6. Adapting to change is a continuous and iterative architecture effort. <br />
7. EA Support strategic planning in adapting to change.<br />
8. EA design the segment architecture based on the demand of strategic direction under the umbrella of the enterprise master plan.<br />
9. EA Close the gaps between strategy and execution. <br />
<br />
The EA big picture put all the parts together to how these parts function as a the whole for an organization to win the edge of competition. ]]></description>
 <category>General</category>
<comments>index.php?itemid=787</comments>
 <pubDate>Sat, 11 Feb 2012 03:08:24 -0700</pubDate>
</item><item>
 <title>Why EA to facilitate collabrative culture?</title>
 <link>index.php?itemid=786</link>
<description><![CDATA[LEA propose t the direction for EA to facilitate enterprise collaboration.  Industry lack of  the power of collaboration to win the competitive edge and do not have a systematic approach to do so.  From the title of "Enterprise Architecture", talking about EA to facilitate collaboration seems off topic. However, from the purpose of EA to overcome the challenge of stovepipe system, EA is definitely tightly couple with facilitating collaboration.  EA facilitate collaboration in a systematic approach where architecture method is the mean not the end. Facilitating collaboration is a unique value of EA to become a emerging paradigm. It is unique compare to all the other business improvement initiative. Light EA suggest that enterprise architects are the "glue" for every one to work together. It is very different from the "Guru" concept to architect the enterprise in a command and control approach.  The "Guru" approach only create bigger stovepipe rather resolving stovepipe system.  The benefit include:<br />
<br />
. Overcome the challenge of stovepipe system at business process, information, application, human resources and security management.<br />
. EA for total participation rather than just supporting strategic planning for the senior executives. <br />
. Facilitating collaboration is human centric and does not requires complicate EA tools. <br />
. Facilitating collabortion is a unique value for EA to become emerging paradigm. <br />
<br />
]]></description>
 <category>General</category>
<comments>index.php?itemid=786</comments>
 <pubDate>Tue, 24 Jan 2012 14:33:30 -0700</pubDate>
</item><item>
 <title>The unique value of EA</title>
 <link>index.php?itemid=785</link>
<description><![CDATA[EA must provide unique value to become an emerging paradigm. LEA suggest that EA was initiated to overcome stovepipe systems in business processes, application system, data and technology solutions where architecture is the mean not the end, The ultimate goal is to close the gap between strategy and execution. The unique value of EA is to facilitate enterprise collaboration.<br />
<br />
The EA community is moving away from the IT centric EA and leading in to direction of supporting business strategic planning. The only concern is that supporting strategic planning is not a unique EA capability. although EA serves well in supporting strategic planning via modeling and impact analysis, but it is not a unique capability of EA. There a numerous strategic planning support initiative and business community always demanding new ways for strategic planning and decision making support. The problem is that strategic planning is more art than science and methods to support strategic planning also change continuously. EA, as a method to support strategic planning will also subject to the fate of come and go as the other business improvement initiatives did. <br />
<br />
On the other hand, facilitating  collaboration is a unique EA capability.  EA was initiated to overcome the challenge of stovepipe systems at business processes, data, application and technologies. It is a cross cutting architecture approach which requires total participation. The EA professional serve as the glue for support the cross cutting architecture approach. <br />
<br />
Facilitating  collaboration is unique to EA because EA professionals serve as the "Glue" not the "Guru". They are the glue to facilitate enterprise collaboration rather than the "Guru" to architect the enterprise blueprint for every one to follow in a "command and control" approach. It only create a larger stovepipe system. <br />
<br />
It is a unique EA capability because the EA profound community enjoy the self satisfaction to be the "Guru" than be the "Glue". They like to define EA based on the title to architect the enterprise rather base on the goal to overcome stovepipe systems. It is also very difficult for people to agree on the definition of EA for the same reason. <br />
<br />
For EA to become an emerging paradigm, it is essential for EA professional to adjust the "Guru" mind set into the "Glue" mind set. Without changing the basic mind set, the EA community will never come up an common EA definition. The problem is changing our mind set rather than how well EA is defined. <br />
<br />
]]></description>
 <category>General</category>
<comments>index.php?itemid=785</comments>
 <pubDate>Sun, 22 Jan 2012 17:05:51 -0700</pubDate>
</item><item>
 <title>EA to facilitate enterprise collaborative culture</title>
 <link>index.php?itemid=784</link>
<description><![CDATA[An important value of Enterprise Architecture is to facilitate enterprise collaborative culture.  The power of collaboration is something that can be overstated. However, collaboration is a human gift but not a human nature. Although the power of collaboration is well recognized, but it is a human nature to create stovepipe system at every level from IT solution, business processes to human resources.  A collaborative culture must be cultivated and It is a big challenge. <br />
<br />
EA is similar to a iceberg, looking at the tip, on the visible part,  the value of EA appears to support enterprise strategic planning. However, EA can not stay afloat without a collaborative environment in the bottom which is not visible and frequently overlooked.  While the EA community have focused on EA value to support strategic planning, LEA recognize the EA value to facilitate enterprise collaboration environment. <br />
<br />
Enterprise is organic, it consist not only the enterprise mechanic but also the enterprise field of collaboration.  The EA community has devoted most for their effort to the enterprise mechanic, The LEA approach add the unique value to facilitate collaboration.  <br />
<br />
LEA takes a systematical approach to facilitate collaborative culture with a collaborative framework.  The column of the framework is composed of the attributes of visualization, communication, consensus, human psychology, politic and technology. The row of framework include the owner, planner, designer and executors. EA professionals divide and conquer the complex system of collaboration by each cell in the framework. <br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20120119-collartive framework.JPG">collaborative frame work</a><br />
<br />
<br />
In additional to the framework, LEA facilitate collaborative culture by actual practice. All the LEA approaches  such as see the big picture, master planning, knowledge management and cross cutting architecture method are based on collaborative concept. This practice does not only achieve these goal of see the big picture, master planning and knowledge management but also resulted a collaborative environment. <br />
<br />
For more information please visit the <a href="http://www.slideshare.net/wuchizong/cultivate-collaboration-culture">presentation in slideshare<br />
<br />
</a><br />
<br />
<br />
<br />
]]></description>
 <category>General</category>
<comments>index.php?itemid=784</comments>
 <pubDate>Thu, 19 Jan 2012 16:14:03 -0700</pubDate>
</item><item>
 <title>LEA 2012</title>
 <link>index.php?itemid=783</link>
<description><![CDATA[The challenge of stovepipe phenomenon is not unique to IT, it occurred on every aspects of enterprise operation. Although EA was initiated to overcome the challenge of stovepipe system. it is also an generic process to overcome all aspect of stovepipe system.  It applies not only the vertical alignment  but also the horizontal and crosscut architecture solution.  Most importantly it recognize that enterprise is organic and capable to adapt organic change in a coherent approach. This EA approach also applied to resolve the challenge of stovepipe system in the business process, data, human resources, security, financing and supply chain.  In 2012,  LEA suggest the extended EA model. In this model,  under a holistic  approach.  the key is to see the enterprise big picture and analyze the enterprise business function from the aspect of function  structure, connectivity and influence. Along the business function, it also analyze the enterprise information which include data, records, documents, information, knowledge.   The business function and information very much constitute the business definition. Under this holistic enterprise definition, the EA professional can overcome all aspect of stovepipe system which include business process, IT, human resources, security, financing as shown in the follow: <br />
<br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20120109-lea_2012_fit.JPG">null</a><br />
<br />
]]></description>
 <category>General</category>
<comments>index.php?itemid=783</comments>
 <pubDate>Mon, 2 Jan 2012 05:45:11 -0700</pubDate>
</item><item>
 <title>EA is not a matter of to IT or not to IT</title>
 <link>index.php?itemid=775</link>
<description><![CDATA[Let get beyond the not very constructive debate of IT or not IT. From business point of view, What the enterprise need is an architecture approach to close the gaps between strategy and execution, facilitate collaboration and knowledge sharing.<br />
<br />
EA is really a matter of stovepipe and holistic rather than a IT or not IT. EA was initiated to overcome the challenge of stovepipe system in the information age, as we should respect the origin. It is easy to have the perception the EA is all about IT in the analogy that a chicken, hatched and raised in by a duck, will think it is a duck.<br />
<br />
EA is really a matter of planning or solution rather than a matter of IT or not IT. Enterprise Architecture is a planing effort rather than a solution effort as many EA approach is leading to. The concept of EA as an enterprise solution provide a lot of self satisfaction of for one person to take on the entire enterprise but serve limited value because the enterprise blueprint become obsolete before ink dry in the changing world. The other challenge is lack of buy-in from stakeholders due to the notion of Not Invent Here.<br />
<br />
The EA method provides more value to as the enterprise master planning in a architecture approach rather than a piece of out of date enterprise architecture blueprint. The enterprise master planing in architecture method is not only in IT but also on human resources, financing. ]]></description>
 <category>General</category>
<comments>index.php?itemid=775</comments>
 <pubDate>Mon, 1 Aug 2011 06:19:51 -0600</pubDate>
</item><item>
 <title>How EA related to collaboration and knowledge sharing?</title>
 <link>index.php?itemid=771</link>
<description><![CDATA[How EA related to collaboration and knowledge sharingcollaboration and knowledge sharing? Most of EA community only focused on the enterprise mechnical architecture. Under the mechanical Enterprise Architecture culture, faciliate collaboration and knowledg managment is not in the EA job discription. <br />
<br />
However, the Modern physics recognize that classical descriptions of phenomena are lacking, and that an accurate, "modern", description of reality requires theories to incorporate elements of quantum mechanics and field theory. <br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20110706-moder physics.JPG">null</a><br />
<br />
In the same token, LEA does not architect the enterprise mechanical architecture but also faciliate collaboration and knowledge sharing as the dynamic energy fields. Enterprise is organic which does not only composed of the mechanical structure but also contain the dynamic energy fields.The classical mechanic architecture alone is not sufficient to accurately  describe the enteprise reality, it must  take collaboration and knowledge sharing into consideration. And EA is highly related to enterprise collaboration and knowledge management. <br />
<br />
As a matter of fact, facilitating enterprise collaboration, knowledge sharing and bridging the gaps between business strategy and execution serve better as  the selling points for the future of EA. <br />
How EA related to collaboration and knowledge sharing collaboration and knowledge sharing? Most of EA community only focused on the enterprise mechanical architecture. Under the mechanical Enterprise Architecture culture, facilitate collaboration and knowledge management is not in the EA job description. <br />
<br />
]]></description>
 <category>General</category>
<comments>index.php?itemid=771</comments>
 <pubDate>Wed, 6 Jul 2011 06:56:38 -0600</pubDate>
</item><item>
 <title>LEA provides a stream of value.</title>
 <link>index.php?itemid=757</link>
<description><![CDATA[Light Enterprise Architecture is a light weight EA approach by establishing the Enterprise Primitives instead of a heavy approach to design the entire enterprise blueprint.  The reason is that It is futile to design a frozen Enterprise print which become obsolete before the ink dry due to constant change.  To be practical, the goal of LEA is  addapting to change by bridging the gaps between strategy and execution via the foundation of Enterprise Agility. The Light EA approach provide value from the begining by faciliating collabortion, see the unseen enterprsie, presering enterprsie knowledge, conducting Enterprise Master planning like a city planner and enable agility  as shown on the follwoing value chain.  <br />
<br />
<a href="http://www.liteea.com/nucleus3.24/media/1/20110517-lea_value_sam.JPG">null</a>]]></description>
 <category>General</category>
<comments>index.php?itemid=757</comments>
 <pubDate>Tue, 17 May 2011 13:49:39 -0600</pubDate>
</item><item>
 <title>Enterprise Map presentation for AEA on May 4th, 2011</title>
 <link>index.php?itemid=752</link>
<description><![CDATA[John Wu presented the Enterprise Map approach for the Association of Enterprise Architects DC on May 4th, 2011. The enterprise map offer an tangible enterprise map to keep every one on the same page.  <br />
<br />
1. <a href="http://www.slideshare.net/wuchizong/enterprise-map-ee-the-unseen-enterprise">The presentation </a><br />
<br />
2. <a href="http://www.slideshare.net/wuchizong/enterprise-map-step-by-step-approach">The Step by step approach</a><br />
<br />
<br />
There are many follow up after the presentation. The following comment serve as a good summary. <br />
<br />
"Thank you for a very informative seminar on the merits of the enterprise map. I can see now how the Enterprise Map can put the enterprise on paper in a holistic view and how you can use the strawman technique to engage the various stakeholders to fill out the map. It is very interesting your approach to use the PDF version to fill out the map and it’s various stages of development."  ]]></description>
 <category>General</category>
<comments>index.php?itemid=752</comments>
 <pubDate>Thu, 5 May 2011 14:04:03 -0600</pubDate>
</item>
  </channel>
</rss>
