SOA: A more pragmatic approach to IT


Published on

Published in: Technology, Business
  • Be the first to comment

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

No notes for slide
  • SOA: A more pragmatic approach to IT

    1. 1. SOA: A more pragmatic approach to IT Peter Evans-Greenwood
    2. 2. Service-Oriented Architecture We can't solve problems by using the same kind of thinking we used when we created them!
    3. 3. Environmental changes enable a new approach to IT U.S. software sales in billions of dollars Source: INPUT SOAP 1.0 WS-I founded SAP WS J2ME Web Services ESB Apache SOAP MS SOAP IBM Web Services Apache Axis JAX-RPC Oracle WS Sun WS WS (J2EE & .NET) WS-* starts exploding WS-* OASIS SOA Reference Model OASIS SOA Blueprints SAP Netweaver Oracle Fusion JAX-WS MS Indigo BPEL BizTalk 2004 Oracle BPEL WBI-SF WS-Policy and WS-Security 2004 2005 2003 2002 2001 2000 1999 Yesterday Today Tomorrow
    4. 4. We’ve tried both ends of the planning spectrum <ul><li>Bottom up action </li></ul><ul><ul><li>Reacting to changes in the environment </li></ul></ul><ul><ul><li>No conscious plan </li></ul></ul><ul><ul><li>Solutions created to meet pressing needs </li></ul></ul><ul><ul><li>Only addressing needs as understood that time </li></ul></ul><ul><li>Top-down planning </li></ul><ul><ul><li>Days spent filling Zachman cells </li></ul></ul><ul><ul><li>Major transformation initiatives </li></ul></ul><ul><ul><li>Initiatives behind by people on the ground who need to get the job done </li></ul></ul>Reactive Omniscient Both result in inflexible systems-of-systems
    5. 5. People use a more pragmatic planning process <ul><li>Establish our goal </li></ul><ul><li>Understand where we are on the landscape </li></ul><ul><li>Consider the paths available to us </li></ul><ul><li>Choose one and head to the junction </li></ul><ul><li>Return to step 1 </li></ul>
    6. 6. SOA enables a similar approach for IT Business Service Architecture IT Landscape Business goals and activities are reified in a service architecture The service architecture acts as a planning framework
    7. 7. We can use city planning as a metaphor <ul><li>A long term plan </li></ul><ul><ul><li>Work with the business landscape </li></ul></ul><ul><ul><li>Create stable infrastructure </li></ul></ul><ul><li>Manage the process </li></ul><ul><ul><li>Appoint a zoning board </li></ul></ul><ul><ul><li>Make the most of what you have </li></ul></ul>City planners try to preserve viable old assets, to replace outmoded assets, and to add new assets—all in the context of an infrastructure linking them coherently. IT developers have a good deal to learn from that approach. Jürgen Laartz, Ernst Sonderegger, and Johan Vinckie, The Paris Guide to IT Architecture McKinsey Quarterly, 2000, Number 3,
    8. 8. Service architecture provides a planning framework Business Service Architecture IT Landscape <ul><li>Optimize new product introduction </li></ul><ul><li>Reduce costs </li></ul><ul><li>Improve process efficiency </li></ul><ul><li>Manual processes </li></ul><ul><li>No support for product management </li></ul><ul><li>Multiple, redundant, applications </li></ul><ul><li>Capture business in service architecture </li></ul><ul><li>Identify scenarios by determining miss-match between current IT and service architecture </li></ul><ul><li>Make a tactical decision on which scenario to deliver, and execute </li></ul><ul><li>Return to 1 or 2 </li></ul>
    9. 9. Scenarios deliver well defined business capabilities <ul><li>Each scenario defines </li></ul><ul><li>Capability delivered </li></ul><ul><ul><li>Optimize new product introduction </li></ul></ul><ul><ul><li>Support multi-channel delivery of services to customers </li></ul></ul><ul><ul><li>Streamline supplier interactions </li></ul></ul><ul><ul><li>Reduce maintenance costs by consolidating IT assets, freeing up cash for investment </li></ul></ul><ul><li>Cost, and associated risk </li></ul><ul><ul><li>Aligned with the business activities effected by the capability </li></ul></ul><ul><li>Detailed business requirements </li></ul><ul><li>Technology footprint required </li></ul><ul><ul><li>New and existing applications </li></ul></ul><ul><ul><li>New and existing business and technical services </li></ul></ul><ul><ul><li>Impact on legacy systems </li></ul></ul><ul><ul><li>Specific technologies required: SOA, BPM, rules engines, MDA, agents, etc. </li></ul></ul>
    10. 10. SOA provides a more pragmatic approach to IT <ul><li>Strategic </li></ul><ul><li>Differentation </li></ul><ul><li>ROI </li></ul><ul><li>Tactical </li></ul><ul><li>Flexability </li></ul><ul><li>Agility </li></ul>Balancing tactical and strategic concerns
    11. 11.