The LEA poster
Upcoming SlideShare
Loading in...5
×
 

The LEA poster

on

  • 2,134 views

The LEA poster put the entire LEA concept on one size D architecture drawing. This presentation is a walk through of this page

The LEA poster put the entire LEA concept on one size D architecture drawing. This presentation is a walk through of this page

Statistics

Views

Total Views
2,134
Slideshare-icon Views on SlideShare
2,110
Embed Views
24

Actions

Likes
2
Downloads
117
Comments
0

1 Embed 24

http://itlyderis.wordpress.com 24

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    The LEA poster The LEA poster Presentation Transcript

    • LEA Poster by John Chi-Zong Wu [email_address] www.liteea.com Version: 2/25/2012
    • Presentation Goals
      • Light Enterprise Architecture on one page poster for easy comprehension.
      • This presentation walk through the LEA poster for better understanding.
      • The audience should obtain a copy of the LEA poster in PDF.
    • LEA Poster
    • Organization to function as the whole
      • EA enables an organization to function as a whole which is much greater than the sum of the parts.
      • It adopts the scientific approach business for quantitative analysis.
      • This approach can be best illustrated by the Zachman framework
      • Zachman framework can be used as a thinking tool to analyze knowledge management, governance, human resources, risk and finance management.
    • Take three theoretical direction
      • Application is a simple system requires on vertical architecture theory.
      • Enterprise is a complex system it takes vertical, horizontal and circular architecture theory as shown in the following picture.
        • Notional architecture in top down and vertical direction.
        • Service Oriented Architecture in cross cutting architecture direction.
        • Adapting to constant change in circular Direction .
    • Put the EA parts as a whole
      • The definition of EA varies because every one only touch a part of EA and insist their righteousness.
      • The EA framework put all different parts of EA together to function as whole and win the edge of competition.
    • The big picture Business Architecture Notional Architecture Service Oriented Architecture Learn from the same line of business Segment Architecture Buy-in From Business Community Communication Collaboration Governance Solution Architecture Strategic Planning Business Performance Gaps due to change Investment Management Enterprise plan Drive Enable Agility Drive Enable Agility Drive Drive Identify the Line of business Govern Govern Drive Support The interaction of EA Parts Drive Drive
    • Who need EA?
      • Visualization, EA must be tangible and visible.
      • Enterprise is organic, EA does not only architect the enterprise mechanic but also facilitate the enterprise field of collaboration.
      Functions Senior managers Business Community Owners Planners Analysts Designers The big picture X X X X X X Knowledge X X X X X X Collaboration X X X X X X Business Architecture X X X X Alignment X x x x Reuse x X X X Strategic Planning X X X
    • EA deliver a stream of value See the big picture Knowledge Management Business Architecture Align to business need Reuse and consolidation Strategy to adapt change Bridging strategy and execution
      • EA deliver a stream of value from the beginning rather waiting for years for a frozen enterprise blueprint. It deliver the value of :
        • Facilitate collaboration
        • See the enterprise big picture.
        • Know the enterprise knowledge
        • Facilitate enterprise collaboration.
        • Business architecture
        • Alignment resources to business need.
        • Reuse and consolidation.
        • Strategy to adapt change.
        • Bridging strategy and execution.
      Facilitate collaboration
    • 1. Buy-in from business community
      • It is futile to design the enterprise architecture blueprint without by-in from business community.
      • EA can not be implement in a command and control approach.
      • Achieve buy-in from business community via:
        • Communication.
        • Facilitate collaboration.
        • Governance and compliance.
    • 1.1 Communication
      • EA model does not serve well with the business community.
      • LEA communicate with business community via :
        • traditional architecture drawing approach.
        • EA portal.
      • Proactive presentation.
    • 1.2 Collaboration
      • Collaboration enable the enterprise to function as a whole.
      • Collaboration by knowing human psychology and behavior.
      • Facilitate enterprise collaboration culture via see the big picture, master planning and managing enterprise knowledge.
    • 1.3 Governance
      • The political effort of Governance and compliance
      • Governance and compliance by building consensus.
      • The Zachmanish governance framework illustrate the different level of governance.
      • EA is not EA without knowing the enterprise.
      • EA people only touch one part and think the part they have touched is the whole.
      • It is a collaborative effort to know the enterprise.
      • Know the enterprise via
        • See the big picture
        • Manage enterprise knowledge.
      2.0 Know the enterprise
      • Enterprise mapping is the visualization of the logical and invisible enterprise.
      • People can not manage the thing they can not see.
      • It is a unique capability for EA professional to capture the abstraction and put it on paper.
      • Mapping the enterprise is a collaborative effort.
      2.1 Mapping the enterprise
    • 2.2 Managing the knowledge
      • To know the enterprise by managing the enterprise knowledge.
      • The Zachmanish knowledge management framework.
      • Managing the enterprise knowledge under the enterprise big picture.
      • Managing the knowledge is an collaborative effort.
        • The knowledge you know.
        • The knowledge you know that you do not know.
        • The knowledge that you do not know that you do not know.
    • 3. Business Architecture modeling
      • EA adopt the scientific approach to analyze and modeling the business for quantitative analysis.
      • It enable the management to see the whole and also know the detail.
      • It serve as the requirements to align enterprise wide IT, human resources, risk management and finance.
      • Business architecture to identify the line of business.
      • Analyze the business architecture from the aspect of mission, function, people, location and demand.
    • 3.1 Business Architecture Framework
      • The Business architecture framework lay out the scope of business architecture analysis.
      • It describe the enterprise with the following analysis.
        • Structure analysis
        • Connectivity analysis
        • Influence diagram.
      • In addition to the familiar structure and connectivity analysis, LEA also incorporate the influence diagram approach to model the business architecture.
    • 4. The Notional Architecture
      • Notional architecture is a enterprise wide high level and vertical architecture effort to align technologies with business.
      • Enterprise is defined by the big picture and enterprise knowledge.
      • It is a matter of how business takes advantage of technology evolution rather than how to design the technology.
      • Light EA is light because it only design the notional architecture rather than the enterprise wide solution architecture.
      • It is futile to design an enterprise solution architecture blueprint which become obsolete before the ink dry.
    • 4.1 IT centric Enterprise Architecture
      • The initial notional architecture aligns technology to business need. in the following layers as show on the picture.
        • business,
        • application,
        • information
        • and technologies.
    • 4.2 EA beyond IT
      • IT alone can not improve business operation, It requires matching processes, human resources, risk management and financing support.
      • EA is a method rather than a frozen architecture blueprint.
      • The same EA method applies to :
        • Enterprise process architecture.
        • Enterprise IT architecture.
        • Enterprise human resource architecture.
        • Enterprise risk management
        • Enterprise financial architecture.
      Business Architecture Business Processes Human Infrastructure Risk Management Mission Budget and Finance Data Application
    • 5. The Service Oriented Architecture
      • The service oriented architecture is a cross cutting architecture in horizontal direction.
      • It identify the common enterprise primitives and building blocks for service oriented architecture design.
      • It learn the right experience of the others via reference models.
      • The service oriented architecture is the engineering of reuse, consolidation, interoperability.
      • and the learning experiences of the others via reference models, reference architecture, the engineering of reuse, the engineering of consolidation, the politics of standardization and governance.
    • 5.1 Learn experiences from the same LOB
      • The service oriented architecture learn experiences from the same line of business.
      • The risk is to learn from the wrong experiences.
      • EA enable organization to learn the right experiences the reference models.
      • Reference model for EA communicating on the same page.
      • Reference models are the reference points between different organizations.
    • 5.2 Engineering of Reuse & consolidation
      • It is a paradigm shift from the traditional vertical architecture approach to architect in a horizontal direction to look for commonality.
      • LEA architects the Enterprise primitives and building blocks via cross cutting architecture effort in a horizontal direction.
      • The horizontal Agility Architecture is about reuse, sharing, interoperability, and the learning experiences of the others via reference models, reference architecture, the engineering of reuse, the engineering of consolidation, the politics of standardization and governance.
      • The is very different from the layers in vertical Architecture Approach.
    • 6. Adapting to change
      • Enterprise is Organic
      • EA to adapt change
      • EA to close the gaps between strategy and execution via.
        • Strategy
        • Segment architecture
        • Execution
      Segment Architecture Strategy Execution
    • 6.1 Bridging strategy and execution
      • Lack of robust strategic planning also contributes to the gaps between strategy and execution.
      • Close the gaps between strategy and execution via
        • Segment architecture.
        • Transition plan.
        • Investment management.
        • Acquisition.
        • Solution architecture.
        • Project management.
      Performance Gap Diagnosis Segment Architecture Strategic Planning Constant Change Investment Management Transition Plan Project Management Acquisition Agile Solution Architecture
    • 6.2 EA support strategic planning
      • Organization conduct strategic planning annually to adapt the constant changing world.
      • EA support enterprise strategic planning but EA is not the strategy.
      • Strategic planning
        • See the whole and know the detail.
        • Knowledge management to yield enterprise statistic pattern.
        • EA model to support impact analysis.
        • Learning from the other organization.
        • Envision the future.
    • 6.3 Adapting to change in three tiers
      • The following figure from OMB FEAPMO illustrates the relation between Notional architecture, segment architecture and solution architecture.
      • It clarifies the confusion of EA, Segment Architecture and solution architecture.
    • 6.4 Segment architecture
      • Segment architecture is driven by the demand of strategic planning to adapt change.
      • It is not a divide and conquer approach to slice a frozen architecture blueprint for engineering convince.
      • The scope of the segment is defined by the area of improvement.
      • The segment architecture must align with the enterprise notional architecture.
      • Segment architecture leverage on the establish building blocks of services.
    • 6.5 Enable Agile Solution Architecture
      • Solution architecture come into the application development paradigm to design and develop the application for use.
      • Application development has been the most established paradigm science the beginning of information age.
      • Organization adapting to change via agile application development in time for need.
      • There are many agile application development methods such the water fall, iterative, spiral and scrum.
      • EA enable agile application development by keeping it simple via service oriented architecture.
    • The Enterprise Architecture Tools
      • EA must take advantage of technology evolution by using different automation tools.
      • Initial EA is human centric and only need simple tools.
      • Advance EA need modeling and analysis tools.
    • EA organizations
      • Notional EA organization chart from “A Practical guide to Federal Enterprise Architecture”
      • EA roles should be evaluated based on the size of the organization, the complexity of the business and architecture, and other factors to effectively determine the correlation of roles assigned to personnel.
    • Governance Structure
      • Investment Review Board is the official reviewing body for information technology (IT) investments, including all major initiatives, funding, and expenditures.
      • The Technical Review Board ensures that proposed investments contribute to the enterprise strategic vision and mission requirements, employ sound IT investment methodologies
      • Change Control Board Changes to configuration items will occur throughout the project caused by a range of event such as changes in a requirement, changes in available technologies and products, and so on.
    • Oversight organizations
      • A chief executive officer (CEO) or chief executive is one of the highest-ranking corporate officer (executive) or administrator in charge of total management.
      • The chief financial officer (CFO) of a company or public agency is the corporate officer primarily responsible for managing the financial risks of the business or agency.
      • As information technology and systems have become more important, the CIO has come to be viewed in many organizations as a key contributor in formulating strategic goals.
    • Conclusion
      • EA adopt scientific approach on business paradigm to integrate the power of left/right brain.
      • EA is a holistic approach for organization overcome the limitation of stovepipe culture.
      • EA does not only architect the enterprise mechanic but also architect the enterprise collaboration culture.
      • EA in a nut shell
        • EA to know the enterprise.
        • Analyze and modeling the Business need.
        • Three steps to overcome architecture buy-in.
        • Three architecture dimension.
        • Three architecture tier.