Your SlideShare is downloading. ×
0
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Enterprise Architecture
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Enterprise Architecture

1,866

Published on

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,866
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
103
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Taking on Challenges With a Passion for Invention At Lockheed Martin we have a passion for invention and innovation – the ability to provide a new perspective, to look at any problem, any solution from all sides. It’s how we offer our customers new ways to improve a product or create a new one. The goal: to redefine what is possible. The U.S. government and its allies look to us to provide innovative solutions to some of the world’s most difficult problems, and we take that responsibility very seriously. Lockheed Martin holds more than 2,500 active patents.
  • Our Four Business Areas
  • We would not think of building an aircraft or spacecraft without detailed architectural descriptions. We couldn’t maintain it, modify it, and would have to start from scratch if we were to build a new one. This same logic applies to our complex information systems environment.
  • Best viewed in presentation mode Note: “Corporate Products” only include products of the first three types below -- 1. Standard Corporate Component products 2. Game Changing products (i.e., critical enablers) 3. Must / Must-not products ------------------------------------------------------------------------ 4. All other product types managed locally
  • Best viewed in presentation mode Note: “Corporate Products” only include products of the first three types below -- 1. Standard Corporate Component products 2. Game Changing products (i.e., critical enablers) 3. Must / Must-not products ------------------------------------------------------------------------ 4. All other product types managed locally
  • Update pictures, turn text on complete and target date
  • Transcript

    • 1. Enterprise Architecture (EA) A Journey in Building a Corporate-wide EA Practice Edwin Nassiff Deputy CTO and Director of Architecture May 15, 2008
    • 2. <ul><li>Topics </li></ul><ul><li>Lockheed Martin (LM) Corporation </li></ul><ul><li>LM Enterprise Architecture (EA) Concept </li></ul><ul><li>EA Background at Lockheed Martin (LM) </li></ul><ul><li>LM Enterprise Architecture Framework (LEAF) </li></ul><ul><li>Challenges </li></ul><ul><li>Harmonization Example </li></ul>
    • 3. <ul><li>140,000 Employees </li></ul><ul><li>70,000 Scientists and Engineers </li></ul><ul><ul><li>25,000 IT Professionals </li></ul></ul><ul><li>Operations in 1,000 Facilities, 500 Cities, 46 States and 63 Countries </li></ul>Lockheed Martin - Demographics
    • 4. Building a Better Workforce <ul><li>Top Corporation for Multicultural Business ( Diversity Business) </li></ul><ul><li>Number 1 – “Ideal Employer” ( Universum Undergraduate Survey) </li></ul><ul><li>Number 1 – “Best Place to Work” ( Woman Engineer ) </li></ul><ul><li>Number 2 – “Best Places to Launch a Career” ( Business Week ) </li></ul><ul><li>Number 4 – “Top 100 Employers” ( Black Collegian) </li></ul><ul><li>Number 5 – “Top 100 Best Places to Work” ( Training Magazine) </li></ul>Recognized as “Employer of Choice” and Industry “Diversity Leader”
    • 5. Executing Complex Projects … Requiring Integrated Solutions … With Advanced Technology and Systems Integration Skills … Across Lockheed Martin and With Our Partners … For Our Government Customers Delivering Products and Services That Perform … with Extraordinary Reliability Distinguished by Whole-Systems Thinking (Holistic Approach)
    • 6. Redefining What Is Possible Return of Crew Space Exploration Biometrics Hypersonics Unmanned and Autonomous Systems Information Fusion Persistent Surveillance A Passion for Invention
    • 7. Lockheed Martin Business Areas Electronic Systems $12.1B Space Systems $7.9B Aeronautics $11.1B Information Systems & Global Services $10.1B 2007 Total Sales - $41.2B
    • 8. Enterprise and Architecture Definitions <ul><li>Enterprise : any organization that exists to perform business activities for some purpose or mission. For Lockheed Martin, examples include: </li></ul><ul><ul><li>Lockheed Martin as a corporate entity </li></ul></ul><ul><ul><li>Business Areas/Business Units </li></ul></ul><ul><ul><li>Business Functions </li></ul></ul><ul><ul><li>Programs (including customers, business partners, and suppliers) </li></ul></ul><ul><ul><li>Any subset or combination of the above </li></ul></ul><ul><ul><li>In our case- the subject of an architecture analysis pertains to achieving a business objective </li></ul></ul><ul><li>  </li></ul><ul><li>Architecture: “The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution” (ANSI/IEEE Std 1471-2000) </li></ul>
    • 9. Enterprise Architecture Defined <ul><li>Enterprise Architecture (as a practice): A business discipline of analytical tasks and techniques that use a business centric approach to documenting and analyzing an enterprise in its current and future states from an integrated business and technology perspective. </li></ul><ul><li>Enterprise Architecture (as models): A holistic set of descriptions of an enterprise covering the perspectives of Business, Applications, Data, and Technical Infrastructure, the relationships between those descriptions, and the principles and guidelines governing their design and evolution over time. </li></ul><ul><li>Systems Architecture : A decomposition of the technology architecture (IT computing systems) into System, Subsystem and Component Levels </li></ul>
    • 10. Traditional IT Systems Engineering Approach Business Engages IT Business Identifies Need Business Plans Changes IT Implements System Business Perspective IT Systems Perspective Develop Design Deploy IT Verifies Design
    • 11. Results in Separately Developed Local Solutions Create Significant Integration Challenges
    • 12. Why Do EA? <ul><li>Align IT to business needs </li></ul><ul><li>Facilitate dialogue among stakeholders and strategy execution </li></ul><ul><li>Improve investment decisions, success rate, and reduce risk </li></ul><ul><li>Create better business agility and lessen project development duration </li></ul><ul><li>Produce more accurate project schedules </li></ul><ul><li>Leverage the scale of our enterprise by reducing duplicative efforts </li></ul><ul><li>Uncover and flag problems before it is too late </li></ul><ul><li>Eliminate high operation and maintenance costs (85% of costs are in O&M) </li></ul><ul><li>Ensure that new systems are the right ones </li></ul><ul><li>Avoid consulting services </li></ul><ul><li>Take advantage of inside/out opportunities </li></ul><ul><li>Provide comprehensive documentation of the enterprise </li></ul>
    • 13. EA Background at LM <ul><li>John Zachman assigned to Lockheed Aircraft facility in Burbank, CA - 1980’s </li></ul><ul><li>Stove-pipes - EA widely practiced throughout LM - 1990’s </li></ul><ul><li>Clinger-Cohen Act of 1996 – mandates EA for government activities </li></ul><ul><li>IT Architecture Framework (ITAF) published - 1998 </li></ul><ul><li>LM EA Community of Practice - Council of IT Architects (CITA) – 2003 </li></ul><ul><li>Executive interviews on EA - May - September 2007 </li></ul><ul><li>Spiral 1 - LM Enterprise Architecture Framework (LEAF) – May 2007 </li></ul><ul><li>Formation of new governance councils with architecture orientation – February 2008 </li></ul><ul><li>LEAF EA Certification Training - April 2008 </li></ul>
    • 14. Enterprise Architecture ConOps Information Systems Architectures Architecture Repository Use harmonized ABD, SEP, etc. Enterprise Architectures Support Training Tools LEAF ADM ADL ARM EA Governance
    • 15. LEAF Components Architecture Development Language Architecture Development Methodology Architecture Reference Models Architecture Governance Processes
    • 16. LEAF - Intended to Be Best in Show LEAF ADM LEAF ARM Artifact Guidance Methodology Guidance Low High The Open Group Architecture Framework (TOGAF) DoD Architecture Framework (DODAF) Zachman Framework Information Content Guidance Medium TOGAF ZACHMAN DODAF Federal Enterprise Architecture Framework (FEAF) FEAF Reference Models Lockheed Martin Enterprise Architecture Framework (LEAF) LEAF ADL
    • 17. Goals & Objectives <ul><li>Goals </li></ul><ul><ul><li>Widespread reuse of architectural artifacts </li></ul></ul><ul><ul><li>Improved agility and integration </li></ul></ul><ul><ul><li>Optimize business alignment and return on IT investments </li></ul></ul><ul><li>Objectives </li></ul><ul><ul><li>Establish a common EA discipline used in the development of business-aligned internal-facing enterprise IT systems </li></ul></ul><ul><ul><li>Harmonize with other corporate processes (e.g., ABD, SEP, LM21, etc.) to facilitate the alignment of IT to business requirements </li></ul></ul><ul><ul><li>Revise IT governance to appropriately guide IT architecture </li></ul></ul><ul><ul><li>Provide EA tools and services to support the above objectives </li></ul></ul>
    • 18. EA Critical Success Factors <ul><li>Executive sponsor support </li></ul><ul><li>Participation by key BA stakeholders in development of reference architectures </li></ul><ul><li>Adoption of LEAF and widespread reuse of architectures </li></ul><ul><li>Staffing and retaining sufficient architects with requisite EA skills </li></ul><ul><li>Harmonization with other related architecture processes </li></ul>
    • 19. Views in the LEAF ADL Motivational View Identifies what the enterprise wants to achieve, how it measures success - Strategy View Translates highest - level requirements into strategy requirements Strategy View Identifies guidance that is in place to ensure success Business View Translates goals, principles, measures of success, and strategy requirements into business requirements Identifies what the enterprise does, its information and information exchanges Systems View Translates business requirements into technology performance requirements Systems View Associates HW/SW with actions, organizations, business nodes, information exchanges Information View Translates all other requirements into data/information requirements Information View Identifies data entities and relationships, definitions, information production in the enterprise Business strategies that reflect goals and architectural principles Actions, organizations, roles, business nodes, information exchange needs Technology used and interface standards Enterprise goals, principles, and measures of success Data entities Data entities Data entities Business needs Systems strategies that reflect goals and architectural principles Systems needs Systems needs Data entities Data entities Data entities Data entities Data entities Business needs
    • 20. Architecture Environment Portfolios Principles Strategies Roadmaps Standards Patterns Products Services Processes Reference Architectures Enterprise Wide Business Specific Support Services Training Consulting Tools
    • 21. (Content) Corporate Reference Architectures Roadmaps Processes Corporate Products Strategies Services Architecture Building Blocks Governance: Idea to Implementation Scenario Other Reference Architectures Standards Metadata Reference Architecture Core Artifacts Mission and Vision Statement Architecture Plan and Justification Business Concept Graphic Business Actions Model Business Node Connection Model Information Exchange Matrix Implementation Roadmap System Connection Model Human Actions/System Actions Matrix
    • 22. Reference Architecture Metadata Example LM P2P Ref Arch Corp Standardization Procurement Process Parts Database SAP Core Ref Arch Legacy Procurement LM Finance None TBD 01/2008 01/2013 Jane Doe TBD TBD TBD Growth, Run Business Contains Is an instance of Addresses Mapped to Depends on May use Is an alternative to Is a subset of Overlaps with Expected status in one year Expected status in three years Strategy recommendation Responsible architect Type Number Element Architectural building block {0 .. n } Linkage Alignment Applicability Exactly 1 LEAF-defined product {1 .. n } Reference model element {1 .. n } Solution Architectures {0 .. n } Architectural building block {0 .. n } Solution Architectures {0 .. n } {From set of defined terms] {0 .. n } Solution Architectures {0 .. n } Solution Architectures Exactly 1 Exactly 1 {From set of defined terms] Date Exactly 1 Individual Exactly 1 {From set of defined terms] Current status Exactly 1 {From set of defined terms] Objective / requirement Content Defined by LEAF product type Effective/Expiration dates 1 each
    • 23. (Content) Corporate Reference Architectures Architecture Governance Metadata Reference Architecture IT Architecture Council Recommend Approval CIO Strategic Council Approved Other Reference Architectures Core Products Mission and Vision Statement Architecture Plan and Justification Business Concept Graphic Business Actions Model Business Node Connection Model Information Exchange Matrix Implementation Roadmap System Connection Model Human Actions/System Actions Matrix (Content) Corporate Reference Architectures Metadata
    • 24. Contains Is an instance of Addresses Mapped to Depends on May use Is an alternative to Is a subset of Overlaps with Expected status in one year Expected status in three years Strategy recommendation Responsible architect Type Number Element Architectural building block {0 .. n } Linkage Alignment Applicability Exactly 1 LEAF-defined product {1 .. n } Reference model element {1 .. n } Solution Architectures {0 .. n } Architectural building block {0 .. n } Solution Architectures {0 .. n } {From set of defined terms] {0 .. n } Solution Architectures {0 .. n } Solution Architectures Exactly 1 Exactly 1 {From set of defined terms] Date Exactly 1 Individual Exactly 1 {From set of defined terms] Current status Exactly 1 {From set of defined terms] Objective / requirement Content Defined by LEAF product type Effective/Expiration dates 1 each Reference Architecture Metadata Example LM P2P Ref Arch Corp Standardization Procurement Process Parts Database SAP Core Ref Arch Legacy Procurement LM Finance None Mandatory Baseline Baseline Baseline 01/2008 01/2013 Jane Doe Growth, Run Business
    • 25. Typical EA Challenges <ul><li>Meaning of EA </li></ul><ul><li>Autonomous Business Areas </li></ul><ul><li>Business value of EA </li></ul><ul><li>Change in leadership </li></ul><ul><li>Products and architecture </li></ul><ul><li>EA governance </li></ul><ul><li>Moving train, fewer green fields </li></ul><ul><li>Perception of competing processes </li></ul>
    • 26.  
    • 27.  

    ×