Download Richard Soley's presentation - 19th Australian Software ...


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
  • Not a technology conversation. Not a product conversation. A business conversation. Business Transformation, Business Re-engineering, creating a platform for Business Agility. Model-driven execution is about compliance and traceability. It’s not about shifting the “programming model” onto business analysts. In fact, goal is to remove “system” from the conversation with the business. No longer about “System A or System B”, and the constraints that brings. About the business process, the business activities, and the services to support those activities.
  • One group of Executives shared we were being to generous with the line between Business Strategy and IT Strategy.
  • Collaborative Strategy and Architecture; Business Solutions that match the Business Architecture; No longer forcing Business to conform to the IT Solution Business Solution delivery is also collaborative – incorporation of Agile practices… Scrum Sprints (iterations) … Not so much for infrastructure, but for service development and composite application development “enterprise architecture” – refers to the discipline, perhaps as originally intended “enterprise”… facilitating the business architecture and aligning the IT architecture… Traditional Enterprise Architects (IT) are not defining the business architecture. They are facilitating the capture/recording. Lead/Chief Enterprise Architects will need to be Business and IT Savvy. With Leadership Skills. Not necessarily “Top Technologist”. Not Coffee Table Document Enterprise Architecture
  • Third quote seems contradictory to second, but actually shows the reality, that in asking where will the services come from, the CIOs and CTOs said it will be a mix…
  • Richard’s experience as AI person in the ’80s, systems work, but hype (vendors, academics) essentially killed it off In the beginning of the object hype of the early 90’s, OMG worked to control the hype when the vendors said, objects, C++. It’ll solve all your problems. Throw away all your COBOL, etcetera. We should, and can, do the that for SOA also, and I think we need to do it top down, which is why you’re here, not your developers. Package the term in a way that it is about business services so that you can sell the concept, and related concepts – business modeling. Tying it all to (measurable) business agility. But if we blow it and tell them SOA solves all your problems, your IT expenditures are going to go down by 90 percent, and you’ll be able to fire all those pesky people, number one, we will have lied and number two, we will have failed.
  • Download Richard Soley's presentation - 19th Australian Software ...

    1. 1. Service Oriented Architecture: Making the Leap, Leveraging Model Driven Architecture Richard Mark Soley, Ph.D. Chairman and CEO, OMG Executive Director, SOA Consortium
    2. 2. Pop Quiz: What are you doing? <ul><li>I am using Service Oriented Architecture (SOA) </li></ul><ul><li>I am using Business Process Modeling (BPM) </li></ul><ul><li>I am using both SOA and BPM </li></ul><ul><li>I don’t need that newfangled stuff, sonny </li></ul><ul><li>I don’t know what the heck you’re talking about </li></ul>
    3. 3. Service Oriented Architecture <ul><li>Wikipedia says: </li></ul><ul><li>“… a perspective of software architecture that defines the use of services to support the requirements of software users. In an SOA environment, resources on a network are made available as independent services that can be accessed without knowledge of their underlying platform implementation.” </li></ul>
    4. 4. SOA Solves All Our Problems? <ul><li>InfoWorld: Desperately Seeking SOA (Alan Zeichick, 30 December 2004!) </li></ul><ul><li>Zapthink: Why is SOA Taking So Long? (October 2005) </li></ul><ul><li>Gartner 18 July 2006: SOA is entering the “trough of disillusionment” </li></ul>
    5. 5. It's New!
    6. 6. Remember MQSeries? How about QNX?
    7. 7. …or MSMQ?
    8. 8. A Little Bit of OMG History…
    9. 9. Now Here’s the Next Best Thing
    10. 10. There You Go Again! <ul><li>“Hey Doc, it hurts when I do this!” </li></ul>
    11. 11. Here’s a Thought… <ul><li>Perhaps we should focus on </li></ul><ul><ul><li>agility </li></ul></ul><ul><ul><li>reusable design </li></ul></ul><ul><ul><li>performance metrics </li></ul></ul><ul><ul><li>expected change . </li></ul></ul>
    12. 12. Pop Quiz: What is SOA? <ul><li>The latest pointless IT industry hype </li></ul><ul><li>A cool technology for building distributed systems on the Web </li></ul><ul><li>Web Services technology for integrating my applications </li></ul><ul><li>A business strategy for increasing the efficiency & agility of my company </li></ul>
    13. 13. Introducing SOA Consortium <ul><li>“ The SOA Consortium is a new SOA advocacy group comprised of end users, service providers, and technology vendors, committed to helping the Global 1000, major government agencies and mid-market businesses successfully adopt SOA by 2010.” </li></ul><ul><li>The SOA Consortium is a time-boxed organization, with an end date of 2010. </li></ul>
    14. 14. SOA Consortium Foundational Premises <ul><li>SOA adoption is a key enabler for the 21st century enterprise </li></ul><ul><li>Achieving the benefits of SOA requires significant changes for both IT and business executives </li></ul><ul><li>SOA is perceived by business executives as an IT integration and productivity story, but is really a business agility story </li></ul><ul><li>Enterprise SOA practitioners would greatly benefit from a vibrant practitioner community to drive local, business-driven, SOA success, and to spur broader enterprise, and industry-wide, SOA adoption. </li></ul>
    15. 15. SOA Consortium Mission <ul><li>“ Promote and enable business agility via Service-Oriented Architecture to allow businesses to compete, innovate & thrive.” </li></ul>
    16. 16. SOA Consortium Vision/Goals <ul><li>“ In 2010… </li></ul><ul><ul><li>75% of the Global 1000 </li></ul></ul><ul><ul><li>75% of Major Government Agencies </li></ul></ul><ul><ul><li>50% of mid-size businesses </li></ul></ul><ul><li>… self proclaim SOA Success. * </li></ul><ul><li>* SOA success is defined in terms of business value generation, business agility, IT agility, IT productivity, and business and IT collaboration. </li></ul>
    17. 17. SOA Consortium Strategies <ul><li>Promoting Business-Driven SOA: Executive Suite SOA </li></ul><ul><li>Generating Business Value from SOA: Business Operations SOA </li></ul><ul><li>Executing Business-Driven SOA: Ground Floor SOA </li></ul>
    18. 18. SOA Consortium Constituency
    19. 19. Executive Summits Overview <ul><li>Invitation-only, vendor-free, IT executive-level summits for early SOA adopters </li></ul><ul><ul><li>CIOs and CTOs representing Fortune 1000 corporations (consumer goods, financial, technology, travel), major government agencies and non-governmental organizations </li></ul></ul><ul><li>Purpose: </li></ul><ul><li>Validate and augment the mission, vision, strategies and tactics of the SOA Consortium </li></ul><ul><li>Participate in a roundtable discussion on real-world SOA implementation opportunities and challenges. </li></ul>
    20. 20. Some Comments <ul><li>“ I told my executive team, don’t worry about SOA. It’s just an IT infrastructure productivity tool. </li></ul><ul><li>You don’t need to know.” </li></ul><ul><li>– Travel CIO at start of Summit </li></ul><ul><li>“ Well, I learned something. You actually changed my mind on something. </li></ul><ul><li>How SOA is not just an infrastructure productivity took for IT, so you guys pretty much convinced me, which is really great.” </li></ul><ul><li>– Travel CIO at end of Summit </li></ul>
    21. 21. SOA and BPM are One Strategy <ul><li>“ SOA, BPM, Lean, Six Sigma are all basically one thing (business strategy & structure) that must work side by side” - CTO </li></ul><ul><li>The only way we can be efficient & agile is to ensure that business processes can be </li></ul><ul><ul><li>recognized </li></ul></ul><ul><ul><li>precisely captured </li></ul></ul><ul><ul><li>categorized & stored </li></ul></ul><ul><ul><li>found & reused </li></ul></ul><ul><ul><li>made more efficient </li></ul></ul>
    22. 22. Success Requires Business and IT Collaboration <ul><li>Achieving the benefits of SOA requires significant changes for both IT and business executives – SOA Consortium Premise 2 </li></ul>Before SOA X
    23. 23. Success Requires Business and IT Collaboration <ul><li>Achieving the benefits of SOA requires significant changes for both IT and business executives – SOA Consortium Premise 2 </li></ul>With SOA “ Enterprise Architecture Discipline”
    24. 24. Selling SOA - Approaches <ul><li>SOA as IT Strategy/Platform </li></ul><ul><ul><li>Next Generation Architecture </li></ul></ul><ul><ul><li>Technical Underpinnings </li></ul></ul><ul><ul><li>Code Re-use </li></ul></ul><ul><li>Skunk Works Approach </li></ul><ul><ul><li>Prove out under the radar </li></ul></ul><ul><ul><li>Deliver business value </li></ul></ul><ul><li>Business Pain Points Approach </li></ul><ul><ul><li>Business Process and Activities </li></ul></ul>
    25. 25. SOA Adoption “is a Journey” <ul><li>Success at Line-of-Business Level, not yet Enterprise SOA </li></ul><ul><ul><li>Few people in an Enterprise see the Enterprise </li></ul></ul><ul><li>Business Process Owners & Business Unit Leaders can be “enemy of SOA” </li></ul><ul><ul><li>Have work that needs to get done, now! </li></ul></ul><ul><li>Some early adopters focused too much on IT, despite large portfolio of services and composite applications, having difficulty engaging other lines of business </li></ul><ul><li>Measuring Progress </li></ul><ul><ul><li>Web Service Implementation != SOA </li></ul></ul><ul><ul><li># of Services is not a valuable metric </li></ul></ul><ul><ul><li>Current Maturity Models are too technology focused </li></ul></ul><ul><li>Not only doing SOA </li></ul><ul><ul><li>BPM, Virtualization, EDA, SaaS, Web 2.0, Office 2.0, Enterprise 2.0 </li></ul></ul>
    26. 26. SOA is Game Changing for Application Providers <ul><li>“ We’re going to completely change the IT execution model, it’ll be based on SOA principles… </li></ul><ul><li>I’m not going to build any more monolithic applications. I don’t even want to buy any more monolithic applications. </li></ul><ul><li>I want to use SOA to de-customize the ones I have spent the last 8 years customizing.” </li></ul><ul><li>- CIO on future of applications </li></ul>
    27. 27. SOA is Game Changing for Application Providers <ul><li>“ SOA fundamentally enables a change in the marketplace. </li></ul><ul><li>The way we buy software today is changing and we are not going to buy software in the future. </li></ul><ul><li>We are going to subscribe to services and you are going to deploy those services to develop and deploy your next generation applications.” </li></ul><ul><li>- CIO on future of applications </li></ul>
    28. 28. SOA is Game Changing for Application Providers <ul><li>“ Are we going to have software as a service? Yes. </li></ul><ul><li>Is it a major part of our SOA? No. </li></ul><ul><li>We’ll pick and choose things.” </li></ul><ul><li>- CIO on future of applications </li></ul>
    29. 29. SOA is Game Changing for Application Providers <ul><li>Where will Services Come From? </li></ul><ul><li>Internally Built, Exposing Existing Functions and Data </li></ul><ul><li>Packaged Software with a Service-Oriented Architecture </li></ul><ul><ul><li>Buy “application platform”, Services are Free </li></ul></ul><ul><li>Service Bundles from Software Providers </li></ul><ul><li>Service Subscriptions from “Service Grid/Marketplace” </li></ul><ul><li>Open Source - Common Services (Customer Creation) </li></ul>
    30. 30. That’s Just a Taste <ul><li>Far more details from the Executive Summit “readout” available from the Consortium </li></ul><ul><li>Community of Practice is moving very rapidly to capture lessons learned and share success stories </li></ul><ul><li>Growing Rapidly! </li></ul>
    31. 31. SOA Consortium Members <ul><li>Six Sponsors </li></ul><ul><ul><li>CISCO, Hewlett Packard, IBM, SAP AG, Savant, Sparx Systems </li></ul></ul><ul><li>Initial seven Participants, some 90 now including manufacturers, government organizations, emergency response organizations, banks, retailers, insurance companies, industry analysts, travel companies & SI’s </li></ul>
    32. 32. Selling SOA - Challenges <ul><li>Vendor and Industry Hype </li></ul><ul><ul><li>Vendors and Press are too far ahead of market </li></ul></ul><ul><ul><li>CEOs hear invest in SOA, don’t know why </li></ul></ul><ul><li>Measuring the value of SOA to an initiative, rather than the value of the entire initiative </li></ul><ul><li>Seeking Business Value Metrics </li></ul><ul><ul><li>Cost Reduction, Schedule Reduction, Revenue Growth </li></ul></ul><ul><li>A vendor-neutral player can control the hype </li></ul>
    33. 33. What About Standards? <ul><li>SOA Standards world is a huge mess </li></ul><ul><ul><li>Confusion about “low SOA” vs. “high SOA” </li></ul></ul><ul><ul><li>Over 440 XML standards groups </li></ul></ul><ul><ul><li>Even the basics of “low SOA” are managed by too many groups: W3C, OASIS, WS-I </li></ul></ul><ul><ul><li>Architects & developers need protection from constant churn of the SOA IT support infrastructure </li></ul></ul><ul><li>OMG focused on two directly-relevant areas </li></ul><ul><ul><li>Business Process Management & Modeling </li></ul></ul><ul><ul><li>SOA Modeling </li></ul></ul>
    34. 34. OMG’s Mission Since 1989 <ul><li>Develop an architecture, using appropriate technology, for modeling & distributed application integration, guaranteeing: </li></ul><ul><ul><li>reusability of components </li></ul></ul><ul><ul><li>interoperability & portability </li></ul></ul><ul><ul><li>basis in commercially available software </li></ul></ul><ul><li>Specifications freely available </li></ul><ul><li>Implementations exist </li></ul><ul><li>Member-controlled not-for-profit </li></ul>
    35. 35. Who Are OMG? Accenture ADA Services BEA Borland Boeing CA Citigroup Daimler DSTO EDS Ericsson Federal Reserve Fujitsu General Electric Hewlett Packard Hitachi Holocentric IBM IONA Kaiser Permanente Kennedy Carter MITRE NASA NEC NIST NTT DoCoMo Northrop Grumman OASIS Oracle Queensland U.T. SAP Satyam Select Software Sparx Systems SWIFT TCS Tethers End Unisys Visa W3C
    36. 36. OMG’s Best-Known Successes <ul><li>Common Object Request Broker Architecture </li></ul><ul><ul><li>CORBA® remains the only language- and platform-neutral interoperability standard </li></ul></ul><ul><li>Unified Modeling Language </li></ul><ul><ul><li>UML TM remains the world’s only standardized OO modeling language </li></ul></ul><ul><li>Common Warehouse Metamodel </li></ul><ul><ul><li>CWM TM , the integration of the last two data warehousing initiatives </li></ul></ul><ul><li>Meta-Object Facility </li></ul><ul><ul><li>MOF TM , the language for defining languages </li></ul></ul><ul><li>XML Metadata Interchange </li></ul><ul><ul><li>XMI TM , the XML standard for MOF-defined languages </li></ul></ul>
    37. 37. Gartner on Modeling <ul><li>“ Organizations implementing SOA’s should pay close attention to the MDA standards and consider acquiring tools that automate models and rules.” </li></ul><ul><li>“ By reinforcing the business-level focus and coupling MDA’s with SOA concepts, you end up with a system that is inherently more flexible and adaptable.” </li></ul>
    38. 38. People Share Design with Models <ul><li>Models—abstractions—are ancient in </li></ul><ul><ul><li>Engineering </li></ul></ul><ul><ul><li>Architecture </li></ul></ul><ul><ul><li>Ship-building </li></ul></ul><ul><ul><li>Traffic control </li></ul></ul><ul><ul><li>Workflow </li></ul></ul><ul><ul><li>Maintenance </li></ul></ul><ul><ul><li>… </li></ul></ul>
    39. 39. People Talk to Computers with Symbols <ul><li>while (x < 10) { </li></ul><ul><li>printf (stdout, array[x]); </li></ul><ul><li>x++; </li></ul><ul><li>} </li></ul><ul><li>What’s wrong with this (non)-picture? </li></ul>
    40. 40. What is the real integration issue? The Global Information Appliance
    41. 41. Not too bad for electrical power
    42. 42. …but a mess for telephony!
    43. 43. Heterogeneity is Permanent <ul><li>Programming languages </li></ul><ul><ul><li>~3 million COBOL programmers </li></ul></ul><ul><ul><li>~1.6 million VB programmers </li></ul></ul><ul><ul><li>~1.1 million C/C++ programmers </li></ul></ul><ul><li>Operating systems </li></ul><ul><ul><li>Unix, MVS, VMS, MacOS, Windows (all 8!), PalmOS… </li></ul></ul><ul><ul><li>Windows 3.1: it’s still out there! </li></ul></ul><ul><ul><li>Embedded devices (mobile, set-top, etc.) </li></ul></ul><ul><li>Networks </li></ul><ul><ul><li>Ethernet, ATM, IP, SS7, Firewire, USB </li></ul></ul><ul><ul><li>Bluetooth, 802.11b, HomeRF </li></ul></ul>
    44. 44. The integration picture is always changing Executive decisions, mergers & acquisitions have a way of surprising us…
    45. 45. The Model Driven Architecture <ul><li>OMG’s Model Driven Architecture (MDA TM ) initiative is aimed precisely at modeling “up and down the stack” </li></ul><ul><li>You have an opportunity to increase your bottom line by integrating your assets </li></ul><ul><li>Industry standards support that goal by future-proofing your application design </li></ul><ul><li>The MDA will help you integrate the mix you have today, and give you an architecture to support the unexpected </li></ul><ul><li>Focus on integrating legacy applications </li></ul><ul><li>Ensure smooth integration of COTS applications </li></ul><ul><li>Models are testable and simulatable </li></ul><ul><li>The aim: a 20-year software architecture </li></ul>
    46. 46. Modeling: Key Concepts <ul><li>Emphasis on transformation techniques </li></ul><ul><ul><li>Based on a standard metamodeling framework; there will be many metamodels, and plenty of modeling languages (including UML) </li></ul></ul><ul><ul><li>Clear semantics, expressed consistently </li></ul></ul><ul><ul><li>Potentially many levels of abstraction </li></ul></ul><ul><li>Enduring architectures are the focus </li></ul><ul><ul><li>Maintenance and integration aren’t pretty, but they are the main job of IT </li></ul></ul><ul><li>Graphical languages as well as textual ones </li></ul><ul><ul><li>Some generic, some domain-specific, just like the textual language world </li></ul></ul>
    47. 47. Model Driven Architecture
    48. 48. An Example: Finance DTF <ul><li>Several activities under way: </li></ul><ul><ul><li>Conversion Maps for Payment Data done </li></ul></ul><ul><ul><li>XMI Profile for ISO 20022 under way </li></ul></ul><ul><ul><li>Finance Reference Models under way </li></ul></ul><ul><ul><li>Property & Casualty Insurance Models starting </li></ul></ul><ul><li>All shared models with many implementations. </li></ul>
    49. 49. MDA is Proven <ul><li>Many excellent proofs-of-concept: </li></ul><ul><ul><li>Banks, railroads, trading, insurance, manufacturing, healthcare, etc. </li></ul></ul><ul><ul><li>Adopted by UN/CEFACT, SWIFT, ACORD, HL7 and other key standards players </li></ul></ul><ul><li>Careful studies prove the point </li></ul><ul><ul><li>The Middleware Company (TMC) </li></ul></ul><ul><ul><li>Electronic Data Systems (EDS) </li></ul></ul>
    50. 50. An Underlying MOF Model
    51. 51. BPMN: An Example of MDA <ul><li>BPMN was designed to bridge the gap between business process design and process implementation </li></ul><ul><ul><li>To support both abstract and executable processes: not just automation </li></ul></ul><ul><li>BPMN is supported by more than 40 vendors </li></ul><ul><ul><li>Process engines support BPMN natively </li></ul></ul><ul><ul><li>Tools map BPMN to BPEL and other execution languages </li></ul></ul><ul><ul><li>Also in use by BPM practitioners in the end user community </li></ul></ul>
    52. 52. Circling Back: SOA, BPM & MDA <ul><li>Service Oriented Architecture (SOA) is an executive decision that requires commitment to discovering, mapping, and executing repeatable processes </li></ul><ul><li>Business Process Modeling (BPM) is a requirement for mapping, executing and measuring repeatable processes </li></ul><ul><li>Model Driven Architecture (MDA) is a way to share concepts, designs and languages in a world of constantly changing infrastructure and requirements </li></ul><ul><li>Tools supporting that stack are in use today. </li></ul>
    53. 53. OMG Business Modeling Activity <ul><li>Semantics of Business Vocabulary and Rules </li></ul><ul><ul><li>Adopted OMG standard </li></ul></ul><ul><li>Business Motivation Metamodel </li></ul><ul><ul><li>Adopted OMG standard </li></ul></ul><ul><li>Business Process Modeling Notation </li></ul><ul><ul><li>Adopted OMG standard (2.0 underway) </li></ul></ul><ul><li>Business Process Definition Metamodel </li></ul><ul><ul><li>Adopted OMG standard </li></ul></ul><ul><li>Organization Structure Metamodel </li></ul><ul><ul><li>In process; completion soon </li></ul></ul><ul><li>Production Rule Representation </li></ul><ul><ul><li>In process; completion soon </li></ul></ul><ul><li>Business Process Maturity Model completed </li></ul>
    54. 54. Up the Stack Some More! <ul><li>Where real value gets added is shared models in vertical markets </li></ul><ul><li>OMG is focused on verticals today: </li></ul><ul><li>Government </li></ul><ul><li>Finance </li></ul><ul><li>Telecommunications </li></ul><ul><li>Manufacturing </li></ul><ul><li>Life Sciences </li></ul><ul><li>Robotics </li></ul><ul><li>Software Radio </li></ul><ul><li>Regulatory Compliance </li></ul><ul><li>C4I/Logistics </li></ul><ul><li>Systems Engineering </li></ul><ul><li>Healthcare </li></ul><ul><li>Business Modeling </li></ul><ul><li>Realtime/Embedded </li></ul><ul><li>Ontology </li></ul><ul><li>Space </li></ul>and so forth…
    55. 55. Pop Quiz: What Do You Think? <ul><li>Just more hype, Richard, sit down </li></ul><ul><li>Maybe there’s something to this </li></ul><ul><li>I am already doing BPM & SOA, I slept through the talk </li></ul>
    56. 56. More Information <ul><li>Interested in the SOA Consortium? </li></ul><ul><ul><li> </li></ul></ul><ul><li>Interested in Standards? </li></ul><ul><ul><li> </li></ul></ul><ul><li>Didn’t get to ask your question? </li></ul><ul><ul><li>[email_address] </li></ul></ul>