Mike Gilpin Liz Barnett VP/Research Director Vice President


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mike Gilpin Liz Barnett VP/Research Director Vice President

  1. 1. May 4, 2004. Call in at 12:55 pm Eastern Time Mike Gilpin Liz Barnett VP/Research Director Vice President Forrester Research ForrTel: Managing The Business Service Model
  2. 2. Theme Without the right process and tools, your portfolio of shared business services is likely to spin out of control and fail to deliver expected SOA value.
  3. 3. SOA: A top issue for enterprise architects What topics are you most interested in learning more about? Information architecture: Where do I start? 50% Security architecture: How well is it baked into your enterprise architecture? 50% Enterprise architecture toolsets and capabilities 61% Identity management 29% Service-oriented architecture 64% Refresh your enterprise architecture 43% Organization of the central federated EA group 39% Creating a mission and vision statement and turning it into an actionable plan 32% How to measure and communicate ROI 14% Preparing for a new CIO 18% Improving the image of IT 21% Process and project management 21% Organizational structures and implementing organizational change 21% What’s the next driver of enterprise architecture? 32% Negotiating better contracts 4% Base: 28 IT decision-makers on Forrester’s Enterprise Architecture Council (multiple responses accepted)
  4. 4. Service orientation: Definitions Service-oriented architecture: A specific instance of an integrated software infrastructure and design approach for service-based applications Service-based development: Methods and design concepts for building, integrating, and provisioning services Service: Performs a complete parcel of work Examples of SOA: <ul><li>Web services architecture </li></ul><ul><li>MOM-based service bus </li></ul><ul><li>CORBA SOA </li></ul>
  5. 5. SOA creates service portfolio to manage Service rules and configuration Service implementations … Service delivery bus Service reporting and management Service clients Service interfaces Service metadata
  6. 6. Service metadata comprises the business service model (BSM) Service rules and configuration Service implementations … Service delivery bus Service reporting and management Service clients Service interfaces The Business Service Model Service metadata
  7. 7. The business service model includes Message Interface The Business Service Model Payload Header Service Interface Descriptions (e.g. WSDL) Format of all content delivered (e.g. XML Schemas) Additional service attributes (e.g. header, parameters) Dictionary of common data elements (e.g. CustName) Relationships between all the above
  8. 8. SOA delivers business value <ul><li>Speed to market </li></ul><ul><ul><li>Faster functional or process change enabled by service-oriented apps that are more easily modified </li></ul></ul><ul><ul><li>Reuse of business and technical services adds more acceleration as services accrue </li></ul></ul><ul><li>Business-process optimization </li></ul><ul><ul><li>Wider circles of process integration enabled by SOAP as the most broadly adopted A2A protocol </li></ul></ul><ul><ul><li>Deeper process integration enabled by SOA infrastructure for more flexible and rich apps </li></ul></ul>
  9. 9. But out of control service portfolios wreak havoc on SOA payback <ul><li>You can’t reuse what you can’t find </li></ul><ul><li>Architects can’t control what they don’t know about </li></ul><ul><li>The SOA architect’s work is never done </li></ul>
  10. 10. It’s not just a technology problem <ul><li>Consider parallel of DBAs, DAs, for data models </li></ul><ul><li>But you must define new roles, change processes </li></ul><ul><li>Processes handle more dynamic service metadata: </li></ul><ul><ul><li>Data in motion different than data at rest </li></ul></ul><ul><ul><li>Multiple versions of interfaces and payloads </li></ul></ul><ul><ul><li>Different metadata relationships are important </li></ul></ul><ul><li>Processes must resolve inherent conflicts arising from associated business priorities and goals </li></ul><ul><li>SOA architects must manage the BSM </li></ul>
  11. 11. BSM requires metadata repository <ul><li>Stores all BSM design artifacts, metadata </li></ul><ul><li>Separates service interface & payload definitions </li></ul><ul><li>Defines message manipulation semantics </li></ul><ul><li>Provides extensible repository metamodel </li></ul><ul><li>Categorizes artifacts into usage domains </li></ul><ul><li>Provides second-generation search for reuse </li></ul>
  12. 12. Integrate SOA architects with development and integration processes <ul><li>Build virtual teams </li></ul><ul><li>Integrate SOA milestones into project milestones </li></ul><ul><li>Make teams responsible for maintaining service metadata (where possible) </li></ul><ul><li>Model using an incremental approach to avoid analysis paralysis </li></ul>
  13. 13. Tools for managing BSM scarce — for now <ul><li>Component management tools closest to a solution — for today </li></ul><ul><li>SOA platforms focal point for ultimate solution </li></ul><ul><li>EAI/BPM/B2B vendors also in the game </li></ul>
  14. 14. Component management tools <ul><li>Select, ComponentSource, Flashline, LogicLibrary, Artifact </li></ul><ul><li>Tool integration mainly focused on project reuse </li></ul><ul><li>More enterprisewide approach needed </li></ul><ul><li>Integration with tool frameworks (Eclipse, Netbeans, Visual Studio, etc.) can be extended to provide full management of BSM </li></ul>
  15. 15. Integration with SOA platform ecosystems <ul><li>IBM/Eclipse, Microsoft, BEA, Sun, Oracle, Borland </li></ul><ul><li>Eclipse options: </li></ul><ul><ul><li>Eclipse Modeling Framework (EMF), Ecore model </li></ul></ul><ul><ul><li>Ecore should be extended in standard way for BSM </li></ul></ul><ul><ul><li>Extension points can hook into developer workflow </li></ul></ul><ul><li>Microsoft options: </li></ul><ul><ul><li>Future metadata enrichment (Yukon, Whidbey) </li></ul></ul><ul><ul><li>WinFS enriching storage, searching of metadata </li></ul></ul>
  16. 16. EAI/BPM/B2B vendors have role to play <ul><li>TIBCO, SeeBeyond, webMethods, Vitria </li></ul><ul><li>TIBCO XMLCanon/Developer models payloads </li></ul><ul><li>SeeBeyond ICAN integrates with NetBeans, webMethods Fabric with Eclipse </li></ul><ul><li>Standard integration models: </li></ul><ul><ul><li>SeeBeyond Common Business Object (CBO) library </li></ul></ul><ul><ul><li>Vitria Collaborative Information Model (CIM) </li></ul></ul>
  17. 17. Support for BSM management by product category over time Less complete More complete SOA application platforms Component management tools EAI/BPM/B2B integration SOA platforms 2004 2007+ 2004 2007+ 2004 Tool framework integration Enterprisewide model scope Extensible metadata Process collaboration support BSM support Rich search, domain categorization 2007+
  18. 18. Selected bibliography <ul><li>April 26, 2004, Trends “Managing The Business Service Model” </li></ul><ul><li>April 1, 2004, Best Practices “Nine Tips For SOA Implementation” </li></ul><ul><li>March 18, 2004, Big Idea “Organic Business” </li></ul><ul><li>October 27, 2003, Planning Assumption “Case Studies Show Incremental Path To Service Oriented Architecture” </li></ul><ul><li>March 24, 2003, Planning Assumption &quot;Market Overview 2003: Component Management Tools&quot; </li></ul>
  19. 19. Thank you Mike Gilpin [email_address] Liz Barnett [email_address] www.forrester.com Entire contents © 2004 Forrester Research, Inc. All rights reserved.