Enterprise architecture prepare enterprise map and the notional EA in parallel. They see prepare the enterprise map by extracting the information on the notional architecture and
. Prepare the initial notional architecture set.
. Prepare the one enterprise map by summarize the notional architecture.
. Use the draft enterprise map for collaborate input.
. Update the notional architecture accordingly.
Stealth EA in complicate computer model and heavy volumes of document does not appeal to stakeholders. The discussion of
John Silva said
I have run across many EA “experts” that, while certified, cannot produce even the most basic artifacts. They can read and make sense of them, but can’t even begin to update them, let alone create new artifacts from scratch.
EA should be intuitive for both business and technical community to comprehend. LEA adapt architecture drawing approach to communicate with stakeholders like the traditional architects do. Architecture drawing has a proven method for architecture to communicate business owners for many thousands of years. Although Technologies have evolved rapidly, human have not evolved much . The capability to comprehend is still the same.
EA have the reputation of “The Stealth EA” because the profound Enterprise architecture have focused on modeling the enterprise with heavy volumes of documents. It is invisible not only to the business community but also to the IT community. EA professional have a difficult time to show “what is EA?” without tangible EA artifacts. The major challenge of EA is to define “What is EA?”. A set of EA architecture drawing can be very helpful to see the clear the EA identity by see the unseen enterprise. EA (or any architecture) may not be about drawing pretty pictures, but pictures are meant to visualize, communicate and connect. Despite the rapid evolution of technology, It is a biological limitation that human can not manage what they can not see. People can not comprehend thing that is to large for them to see and people can not comprehend thing that they can not see. A important training in any architecture practice is see the unseen and all architects and engineering education requires training in architecture drawing.
The LEA portal LEA is a human centric EA approach to serve both business and engineering community. It utilize the latest web technology to develop the LEA portal for stakeholders to drill down their enterprise architecture from the enterprise architecture framework. It also adopt the traditional architecture drawing approach to deliver tangible EA products. Although technology evolved rapidly, human have not biologically evolved significantly. Architecture drawing still serve as the fundamental for architecture communication. for example : The LEA portal. It is a interactive EA portal which can be drill down to detail EA informstion. Please click on the framework to drill downThe LEA tangible artifacts consist of
Enterprise map is effort to visualize the Enterprise. It is fundamental to Enterprise Architecture practice similar to geographical survey to Architects and Engineering.
Enterprise map has served well to address the question of “What is EA?”. The EA maps has been a very effectively explain “what is EA?” to the business community.
As the foundation of EA, the Enterprise map:
1. See the unseen enterprise. 2. See the true enterprise big picture. 3. Bring Enterprise Architects on the same page. 4. Enterprise map is not only for documenting as-is but also to plan for the future.
The Enterprise Map is developed based on Zachman framework. It illustrate the layer of Business architecture, application architecture, information architecture and technology architecture base on the attributes of what, how, who, where, when and why. It is the Enterprise Architecture in a nutshell.
The master plan drawings
The Initial EA describe the high level and holistic view of Enterprise Topology, Business Architecture and the Notional Target architecture.
The Reference Architecture drawings
Agility EA is delivered via the baseline standard map which describe the pattern, standards and the consolidation for application, data and infrastructure.
The LEA portal
LEA is a human centric EA approach to serve both business and engineering community. It utilize the latest web technology to develop the LEA portal for stakeholders to drill down their enterprise architecture from the enterprise architecture framework. It also adopt the traditional architecture drawing approach to deliver tangible EA products. Although technology evolved rapidly, human have not biologically evolved significantly. Architecture drawing still serve as the fundamental for architecture communication. for example :
The LEA portal. It is a interactive EA portal which can be drill down to detail EA informstion. Please click on the framework to drill down.
The Enterprise Maps approach is developed based on the author’s experience in the cross training of Civil Engineering and Computer Science. The architects and engineers have communicate with stakeholders with architecture drawings for many centuries. Enterprise Architecture, which is an holistic architecture practice, can also leverage on the well developed method to communicate with stakeholders. Although the Enterprise Map is a innovative effort, the concept to map the enterprise is not unprecedented. To avoid the effort in reinventing wheel, the author have discovered and learned from the Enterprise Maps method by :
Alex Osterwalder business model canvas
Recently Alex Osterwalder propose a comparable method in business architecture modeling. He suggest the business canvas approach. It propose a single reference model based on the similarities of a wide range of business model conceptualizations.
The Business canvas has been presented in :
. Business model Canvas Book Business Model Generation,
. Business model Canvas Training Bhsiness model canvas game.
. Business model canvas tools The are several business model canvas tool. Here is one from BM designer. Business model Canvas tool
Model http://en.wikipedia.org/wiki/Business_Model_Canvas and the online tool that support it, such as BMDesigner http://bmdesigner.com.
1. Enterprise map by Burton, Herbert O, Pennotti, Michael C.
“Abstract: This article describes how senior leaders can use the tools and techniques of systems analysis to develop a top-level process architecture that identifies the key processes of a business and specifies the critical interconnections and interrelationships between them. We call this top-level architecture an enterprise map and we believe it represents an important addition to a senior management toolkit, complementing other popular, performance-enhancing tools like process maps (Eckes, 2001) and the balanced scorecard (Kaplan and Norton, 1992).”
There are many graphic representation effort in IT architecture practice, the Enterprise Maps leverage on the concept and the effort from the following :
2. Bernard H. Boar’s effort
The Enterprise Maps is developed under the influence of Mr. Bernard H. Boar. He is Director of Strategic Solutions for RCG Information Technology in Iselin, New Jersey. He is an internationally recognized expert on IT strategy, and the author of several successful books on the subject, including Practical Steps for Aligning Information Technology with Business Strategies and The Art of Information Technology Strategy, both of which are available from Wiley.
“This book is the answer to hundreds of CIOs who have asked me how IT can be used to disrupt their market and change the rules of competition. If you live in a hypercompetitive world, CIOs will find this book an invaluable resource.” —Richard A. D’Aveni, author of Hypercompetition “I wish Bernie Boar had written this book 20 years ago. And I wish every IT manager and architect had read it and placed his hand on it and sworn by it 20 years ago. Then we wouldn’t be in the pickle we find ourselves in today!” —John A. Zachman Constructing Blueprints for Enterprise IT Architectures Recently deployed within a unit at AT&T, Enterprise IT Architecture Blueprinting (EAB) lets you blueprint your system designs with a degree of precision long taken for granted by engineers and architects. In fact, it’s the first standardized methodology of its kind. In this book, expert Bernard Boar introduces you to the principles behind EAB and all of its features by walking through the entire design process for developing conceptual, functional, logical, and physical blueprints complete with useful icons, diagrams, and page templates.
3. C4ISR products
DoDAF v1.0 listed the following products as the “minimum set of products required to satisfy the definition of an OV, SV and TV.” One note: while the DoDAF does not list the OV-1 artifact as a core product, its development is strongly encouraged. The sequence of the artifacts listed below gives a suggested order in which the artifacts could be developed. The actual sequence of view generation and their potential customization is a function of the application domain and the specific needs of the effort.
AV-1 Overview and Summary Information AV-2 Integrated Dictionary OV-1 High Level Operational Concept Graphic OV-5 Operational Activity Model OV-2 Operational Node Connectivity Description OV-3 Operational Informational Exchange Matrix SV-1 System Interface Description TV-1 Technical Standards Profile
4. Unified Modeling Language
UML 2.0 has 13 types of diagrams, which can be categorized hierarchically as follows:
Structure diagrams emphasize what things must be in the system being modeled:
Activity diagram State Machine diagram Use case diagram Interaction diagrams, a subset of behavior diagrams, emphasize the flow of control and data among the things in the system being modeled:
Communication diagram Interaction overview diagram (added in UML 2.x) Sequence diagram Timing diagram (added in UML 2.x)
Coherent EA approach adopt the traditional architecture/engineering drawing approach to develope, communicate, certify and deliver EA artifacts. The CEA architecture has developed the following Enterprise Architecture drawing sets :
. EA Maps : To describe enterprise business in a nutshell. . Business Architecture drawing set : To analyz the structure of enterprise from the aspect mission, function, information, organization, location and performance requirements. . Data Architecture drawing set. : To align enterprise information with business architecture and analyze enterprise information structure. . Application Architecture drawing set. : To align enterprise application serivces with business architecture and analyze the enterprise application service structure. . The enterprise technology architecture baseline. : To illustrate the enterprise technology architecture baseline for every technology domain defined in the Technical reference model.
Why EA architecture drawing
. EA is known to be stealth due to lack of practical communication mechanism.
. Significant EA work become hidden treasure in the repository.
. Communicate Enterprise Architecture design with architecture drawings instead of volumes of document.
. Architecture drawing has been the proven architecture communication mechanism.
Architecture drawings serve as a communication package
The architecture drawings serves as the EA communication package to contain defined EA artificats.
The Utilization of EA architectrure drawings :
. To know the enterprise via architecture drawings. . Develope EA via architecrure drawing. . Communicate EA via architecture drawings. . Certify EA via architecture drawings. . Deliver EA via architecrure drawing.
Drawing oriented EA approach
The CEA method adopt the traditional architecture by developing EA from the drawing board in the follow approach:
. Step 1: To see the big picture and know the enterprise via EA Map which analogy to geographical survey. I have developed this method from the swim-lane model for more than ten years. This is version 3, please review the method in the EA Map blog.
. Step 2: To analyze the Enterprise Business Architecture with business architecture drawing room the aspect of Mission (Why), Function (How), Information (What), Organization (Who), Location (Where) and Performance requirement (When). The drawings are backed up with much architecture analysis.
. Step 3. To analyze the application architecture with the application architecture drawing which align application system to support business.
. Step 4. To analyze the data architecture with the data architecture drawings which align data resources to support business.
. Step 5. Establish Enterprise technology architecture baseline with the technology architecture baseline drawings, which illustrate the enterprise technology baseline environment.