Your SlideShare is downloading. ×
Microsoft PowerPoint - When EA and SOA Worlds Collide ...
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

Microsoft PowerPoint - When EA and SOA Worlds Collide ...

648

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
648
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
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

Transcript

  • 1. Directions Teleconference & Webinar: When EA & SOA Worlds Collide! Featured Guest SOA Expert: David Linthicum Linthicum Group Sponsored by Shared Insights July 19, 2007 © EAdirections 2006. All Rights Reserved.
  • 2. Today’s Agenda • Why is SOA such a misunderstood topic • The natural tension between Enterprise-level and project- level architecture • An Enterprise Architect’s view of SOA • A Service Oriented Architect’s view of SOA • What should EA do for SOA projects? • What should SOA projects do for EA? • What should SOA and EA do together for the business? • How do you bring these two together? • Implications for Governance • Q & A from the audience © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 2
  • 3. © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 3
  • 4. Current Issues • Technological obstacles to reuse being overcome • Cultural obstacles to reuse still an issue • Project-oriented obstacle to reuse • Many competing internal SOA projects, approaches, & technology choices • Hype-driven confusion (e.g., “SOA 2.0”) • Lack of leadership from EA on SOA • Processes moving outside of the firewall • Departments operating independent of oversight • More enterprise applications are Web-delivered • Technology as a business advantage and cost saving mechanism © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 4
  • 5. Understanding the Forces at Work Enterprise Architecture Hype Web 2.0 SOA Cost Reduction Emerging Standards SaaS © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 5
  • 6. EA and SOA…Let’s Face Facts • There seems to be two worlds out there, the world of enterprise architecture and the world of SOA. – “The funny thing is that those in each world thinks that they can do the other world's jobs.” – “The end result...there is not a lot of synergy there yet.” This is not about “Who gets to lead?” © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 6
  • 7. More good news… Some traditional enterprise architects have not done a stellar job in understanding the opportunities within SOA, generally speaking, and the SOA guys have not figured out how SOA meshes with existing enterprise architecture standards, notions, and practices, again generally speaking. © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 7
  • 8. Natural Tension between E-level and project-level architecture • The project is the primary “unit of change” in an enterprise THE BIG PICTURE • Project have limited scope, budget, schedule and resources • The “Big Picture” needs to exist and be maintained • Linkages need to be established and impact analysis performed • Downstream decision making/projects must be consistent with Upstream Project Portfolio intentions Build Integrate Build Build Capabilities Capabilities Build Build Service Service Tension can become Synergy! Service Service © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 8
  • 9. Defining Enterprise Architecture: Process • Enterprise Architecture (EA) is a strategic management discipline that creates a single, holistic view of the processes, systems, information and technology of the enterprise designed and optimized to achieve the business strategy and current objectives. • Primary Output: a roadmap that evolves the ‘as-is’ business processes, systems, information and technology of the enterprise from the ‘current state’ to the desired ‘future state’. • Intent of EA process: Identify the impact of enterprise strategies and influence lower-level tactical, operational, and project decisions and activities to be more aligned with enterprise strategies. The primary design goal for enterprise architecture must be to enable efficient change in business capabilities through the services that enable them! © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 9
  • 10. Key Concepts in Enterprise Architecture • Holistic View Business Strategy – Lots of other views – From Portfolio Management to Budget to HR • Optimized for the Enterprise Current Objectives – Not the Business Unit – Not the Process – Not the Application – Not the Database – Not the Server – The problem of ‘point optimization’ Processes • Not simply ‘IT standards’ – Examples: • This building • Designing an airplane • EA is a ‘process’ not a ‘project’ Data & Information Systems & Infrastructure © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 10
  • 11. EA Supports SOA and More… C L Services Strategic Performance M O IA PL AN C Design Planning Management IA N N C FI Outsourcing E Security/Privacy Transition Compliance Planning License Business Case Compliance Analysis EA Process Asset Project and Impact Redundancies Knowledge Base Analysis Resource Allocation Standards Compliance Skills Planning Business PR Process O Services Application Resumption JE Optimization ET S CT S Delivery Portfolio Risk Planning AS S © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 11
  • 12. An Enterprise Architect’s view of SOA Business Strategy Enterprise Capabilities Services Catalog Current Objectives Business Services Application Services Processes Information Services Infrastructure Services EA Roadmap Current Future Data & Information State Analysis State Project Portfolio Systems & Infrastructure © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 12
  • 13. An Enterprise Architecture Model view of SOA Enterprise Solutions Architecture Enterprise Value Enterprise Technology Architecture Intelligence S Network Enterprise Information Architecture Enterprise Enterprise Business Architecture T Analysis Business I Information Strategy “The Enterprise Solutions Architecture Big Picture” B Value Chain Analysis Required Enterprise Technology Architecture Capabilities Enterprise Information Architecture S Context (CRV) Enterprise Business Architecture T Diagrams Business I Scenario Scenario Level Architecture B Models Enterprise Enterprise Solutions Business Principles Enterprise Technology Architecture Event (CA) Enterprise Information Architecture S Analysis T Enterprise Business Architecture Swimlane I Function/ Diagrams Process Capabilities LevelArchitecture B Enterprise Solutions Decomposition Enterprise Technology Architecture Integration IT Enterprise Information Architecture S Service Models Standards T Catalog Enterprise Business Architecture Service I Solutions Function Services Level B Use Portfolio Models Cases © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 13
  • 14. Continued … Enterprise Capabilities Business = + Services Application Services Information Services Infrastructure Services Enterprise Solutions Architecture Enterprise Technology Architecture Integration IT Enterprise Information Architecture S Models Service Standards T Catalog Enterprise Business Architecture I Service Solutions B Function Use Services Level Models Cases Portfolio © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 14
  • 15. A Service Oriented Architect’s view of SOA Monitoring/Event Management Process/Orchestration Governance Security Services Data Services/Messaging Data Abstraction Data Data Rep Legacy Legacy Internet- Based New Services Services © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 15
  • 16. So, the EA “Mega Trends” 1. SOA, SOA, SOA! 2. SaaS 3. “Web 2.0” 4. “Enterprise 2.0” – Mashups – Inside-out – Outside-in 5. Incorporating existing Enterprise Architecture concepts and practices…how? © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 16
  • 17. What should EA do for SOA projects? • Standardization – Infrastructure (hw, sw, network) – Messages (format, content, delivery, use case) – Data content/names/definitions/ownership – Business Rules & Events • Drive towards common semantics between EA and SOA • Be proactive in identifying services that should be built and identifying the development efforts that are positioned to deliver needed services • Broader than the project view – Scope of analysis and design – Models for impact analysis and integration planning • Research and recommend SOA technology choices, approaches and designs • Collaborate on technology choices, approaches and designs that can satisfy a broader part of the enterprise • Extend the application of successful SOA implementations to other parts of the enterprise • Governance integration • CULTURE CHANGE!!! © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 17
  • 18. What should SOA projects do for EA? • Create and populate EA repository with appropriate documentation • Comply with existing EA standards, when possible • Demonstrate need for new standards or extensions to EA • Provide an opportunity for SOA Proof-of-Concept (POC) • Contribute to the ongoing evolution of EA standards, patterns and models • Seek service reuse opportunities • Bind services with appropriate partners • Create long term service development, deployment, and management plan • Link back to proper EA methods © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 18
  • 19. What should SOA and EA do together for the business? • Deliver the needed Enterprise Capabilities • Identify the potential investments required to build an SOA • Develop a Service Catalog • Foster a collaborative reuse-oriented culture as a model for the rest of IT • Identify opportunities to externalize business services, as well as identify external services for consumption • Continue to measure agility and reuse, and adjust as needed • Monitor the integration with partners • Continue to monitor the value to business © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 19
  • 20. How do you bring these two together? Executive Business Strategy Management Enterprise Architecture New/Changed Capabilities Required Models of the Annual, Tactical Input Future State Enterprise G Models of the Goals, Objectives & Targets Current State lu enc es O Inf Enterprise V Existing Tactical Project Portfolio EA Roadmap • Project Requests • Adds/Changes to Applications, E Operations Project Requests Infrastructure, Information, & Business Processes Services R N • Timeline/Interdependencies Populate New/Changed Capabilities Delivered A N C E Project A Project B Project C NEED Standard Service Request NEED Standard Service Request NEED Standard Service Request Standard Service Request Service Service Service NEED Service CLIENT CLIENT CLIENT CLIENT FOR Provider FOR Provider FOR Provider FOR ICE (Service ICE (Service ICE (Service ICE (Service Provider SERV Requestor) Standard Service ResponseWORK SERV Requestor) Standard Service ResponseWORK SERV Requestor) Standard Service Response WORK SERV Standard Service Response Requestor) WORK rm rm m rm or orm orm orm orm rfo rfo rf rfo Pe Pe Pe Pe Pe Pe Pe Pe f f f f Pe r Pe r Pe r Pe r r r r r fo fo fo fo rm rm rm rm Object Object Object Object Per Per Per Per f f f f orm orm orm orm Object Object Object Object Build & Object Object Build & Object Object Build & Object Object Object Object Integrate Integrate Integrate © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 20
  • 21. Implications on Governance EA Governance SOA Governance • Ensuring that duplicate services are not • SOA Governance becomes a sub-discipline to created EA Governance • Compliance with standards / exemptions / • Design Time SOA Governance extensions – A registry and/or repository for the tracking of • Ensuring service levels are defined and service design, management, policy, security, approved and testing artifacts. – Need appropriate metrics – Design tools, including service modeling, • Change management more complex – dependency tracking, policy creation and unknown service consumers management, and other tools that assist in • Manage the portfolio of services the design of services. – Deployment tools, including service deployment, typically through binding with external development environments. – Links to testing tools and services, providing the developer/designer the ability to create a test plan and testing scenarios, and then leverage service testing technology. • Run-Time SOA Governance – Service discovery – Service delivery Design Run – Security Time Time – Setting and maintaining appropriate service levels – Managing errors and exceptions – Enabling online upgrades and versioning – Service validation – Auditing and logging © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 21
  • 22. Final Thoughts • EA is an evolving discipline. New notions and business events will drive EA activities going forward. • SOA is part of EA. We have a tendency to forget that. The “A” in SOA is architecture. • Learn how to see beyond the SOA hype, and make sure to understand your own business issues. • Accept the emerging Web as a resource that is to be leveraged for the good of the company. There will be much change here. • The enterprise architect should drive change for the good of the company. However, never “manage by magazine.” • The lines are blurring between enterprise applications and the emerging Web. There is a fundamental shift in how we deploy and manage enterprise applications and services going forward. • Project architects may lead, or EA may lead, but they must work collaboratively to advance SOA beyond marginal point successes © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC 22
  • 23. Q&A To submit your questions, please click on the “Q&A” tab on the bottom right-hand corner of your screen. © EAdirections 2007. All Rights Reserved. Copyright 2007 The Linthicum Group, LLC

×