Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Soa maturity business model

819 views

Published on

Published in: Technology, Business
  • Login to see the comments

  • Be the first to like this

Soa maturity business model

  1. 1. SRL Methodology Library<br />SOA<br />Yuval Birenboum<br />CTO<br />Integration, SOA, BPM <br />& Architecture<br />
  2. 2. Lack of Agility ?<br /> Duplication ? | Data | Web service | Process |<br />Low Reliability ?<br />High Maintenance Costs?<br />Support Confusion - Difficult Root Cause Determination?<br />IT ChallengesWhere are Your Pain Points?<br />Can’t Estimate Change Impact?<br />Poor Project Estimating with Multiple Systems Involved?<br />Falling Data Quality?<br />Project Failure?<br />
  3. 3. Integration Has Become EasyQuick and Easy<br />What did we get ?<br />connection between systems<br /> exposure of transactions<br />spread of data <br /> & functions<br />SOA technologies enable<br /> Asset<br />Visibility<br />Process<br /> Modeling<br />Impact Analysis<br />
  4. 4. How did we get here ?The Big Box Application<br />Stand alone.<br />Modules can import/export data but not dependent<br />Represented a complete end-to-end process by itself. <br />Asset Management<br />Inventory<br />Asset State<br />Parts<br />Accounting<br />Ordering<br />Supplies<br />Stock Control<br />
  5. 5. How did we get here ?But Data Became “Real Time”<br />Not acceptable to slowly import/export data between applications <br />Asset Management<br />Inventory<br />Asset State<br />Parts<br />Accounting<br />Ordering<br />Supplies<br />Stock Control<br />
  6. 6. How did we get here ?The Distributed Application<br />The Big Box<br />Application<br />Asset Process<br />Inventory<br />Asset State<br />Parts<br />Decomposition<br /><ul><li>Increased complexity
  7. 7. Reliability issues
  8. 8. Performance concerns
  9. 9. New security </li></ul>requirements<br />Accounting<br />Ordering<br />Supplies<br />Stock Control<br />distributed <br />interconnected <br />systems and <br />processes.<br />
  10. 10. Business : IT Challenges<br />Quickly Changing Business Demands<br />Do Even More <br />with Less<br />Move Beyond Overhead<br />Start Innovating<br />
  11. 11. Business Demands vs. IT Constraints<br />Stop running<br />Start innovating<br />New & changing <br />business demands<br />Business need<br />Business Value<br />Do more <br />with less<br />Business subduction<br />Business growth<br />Run the business<br />0<br />Increased complexity<br />IT Constraints<br />Reliability<br />Issues<br />Performance<br />Concerns<br />
  12. 12. SOA eliminates the gap<br />Stop running<br />Start innovating<br />IT Empowers the Business<br />New & changing <br />business demands<br />Business need<br />Business Value<br />Do more <br />with less<br />Business subduction<br />Business growth<br />Run the business<br />0<br />Increased complexity<br />IT Constraints<br />Reliability<br />Issues<br />Assets & Process Composition = Service Enabling <br />Assets & Process Visibility = (re)use<br />BAM, Governance & KPI’s = Control<br />Performance<br />Concerns<br />
  13. 13. SOA ApproachesDoes it matter ?<br />Top-Down<br />Middle-Out<br />Bottom-Up<br />Start with business model finish with implementation<br />For each project expose, compose & consume<br />Start with implementation finish with business model<br />Whichever you choose, same steps different order.<br />None of these approaches say “Start tool shopping…”<br />
  14. 14. A Full SOA Model<br />In a perfect world, SOA would follow <br />three top-down stages…<br />Collaborative Modeling<br />Collaborative Operation<br />Service Oriented System Construction<br />
  15. 15. The three milestones of SOACollaborative modeling<br />Multi-views business modelling<br /> describes enterprise business<br />Collaborative modeling<br />Business model is transformed<br /> into platform independent<br /> business collaborative model<br />Platform-independent business <br />collaborative model is mapped into platform-specific business collaborative model<br />
  16. 16. The three milestones of SOA<br />Service modules in enterprise information systems are identified, encapsulated and published into business process services<br />Service oriented information system construction <br />Build service component libraries<br />Theservices in these libraries can be composed and choreographed <br />
  17. 17. The three milestones of SOA<br />Monitor enterprise business processes<br />Collaborative operation and evaluation<br />Analyze and Optimize the performance of the enterprises business processes by a workflow management system<br />Enforce business policies and regulations<br />
  18. 18. Challenges<br />We have a large number of existing systems in older technology & architecture models to maintain & integrate.<br />We have project and business deadlines that don’t care about architecture, they just want to get it done NOW.<br />SOA tech has entered bottom-up, without methodologies & process, because “just connecting things using SOAP” is fast and easy.<br />
  19. 19. SOA Technology without Methodology leads to…<br />Hard to identify process impact, impact of changes and system modifications and upgrades<br />Major Support (Root Cause Identification) Challenges<br />Connection Spaghetti<br />Process Duplication<br />Reduced Reliability<br />Data Duplication<br />
  20. 20. SOA Methodology Provides Measurable Value<br /> Adjustments for Each Stage<br />Every Stage of the Software Development Lifecycle<br />Requires Tweaks to Achieve SOA Success & Get Real Value<br /> Measurements for Each Stage<br /> Keeps the SOA ROI Positive<br /> Provides Describable Business Value<br />
  21. 21. - Improved Data Quality<br />- Reduced Business Process Duplication<br />SOA CycleAre You Getting Value Here?<br />Identify & Model<br />the “gold copy of data” <br />“business process”<br />the right source “system” or “application”<br />SOA <br />Analysis<br />
  22. 22. - Increased Reuse / Faster Development<br />- Increased Agility<br />SOA CycleAre You Getting Value Here?<br />Creating<br />reuse incentives <br />services with highest likelihood of reuse<br />Penalties<br />having to adjust services in the next year<br />Handling of budget <br />issues regarding first-creator cost, maintenance & support costs, etc<br />SOA <br />Analysis<br />IT Management <br />for SOA<br />
  23. 23. - Improved Service & IT Process Control<br />- Improved Project Estimating<br />- Clear Understanding of Change Impact<br />SOA CycleAre You Getting Value Here?<br />Governance<br />Managed Service SDLC Workflow<br />Policy Creation, Automated Application & Enforcement<br />Impact Analysis<br />Determine, Track, Report<br />SOA <br />Analysis<br />Create SOA Controls<br />IT Management <br />for SOA<br />
  24. 24. - Avoid SOA Reliability Decreases<br />- Allow for coordinated parallel development, faster results!<br />SOA CycleAre You Getting Value Here?<br />Consumer – Provider <br />contracts<br />Roles and responsibility<br />Layered QA testing<br />Integration into the Software <br />SDLC<br />SOA <br />Analysis<br />Create SOA Controls<br />Coordinated SOA Development<br />IT Management <br />for SOA<br />
  25. 25. - Determine system, project, and business process impact.<br />- Avoid “surprise” system overloads , whether from service misuse or unexpected business growth.<br />SOA CycleAre You Getting Value Here?<br />Distributed Monitoring<br />SOA <br />Analysis<br />Create SOA Controls<br />Pinpoint problems<br />SLA control<br />Excess use<br />Coordinated SOA Development<br />IT Management <br />for SOA<br />
  26. 26. - Improve what needs improving and provides maximum return!<br />SOA CycleAre You Getting Value Here?<br />Distributed Monitoring<br />measure<br />the right points +<br />Get detailed feedback<br />=<br />Show the ROI, detailed/granular <br />and enterprise.<br />SOA <br />Analysis<br />Create SOA Controls<br />Ongoing KPI’s <br />for SOA<br />Coordinated SOA Development<br />IT Management <br />for SOA<br />
  27. 27. What will we get from a Methodology ?<br /> Moving up in the <br />SOA maturity model<br />
  28. 28. Create services definitions<br />SOA maturity model<br />Integrate SOA into project development<br />methodology<br />Quantify costs, time, and business<br />benefits of pilot projects<br />Key goals<br />Business Value<br />New<br />Functionality<br />1<br />0<br />Initial<br />Services<br />
  29. 29. Specify technology standards for SOA<br />SOA maturity model<br />Integrate SOA into organization-wide<br />development process<br />Use incremental integration<br />Key goals<br />Business Value<br />IT Cost<br />Reduction &<br />Control<br />New<br />Functionality<br />2<br />1<br />0<br />Initial<br />Services<br />Architected<br />Services<br />
  30. 30. Specify policies for use of SOA in creation<br />or modification of business processes<br />SOA maturity model<br />Take advantage of event-oriented and<br />mediation functionality of SOA technologies,<br />especially with regards to enhancing/<br />extending business processes<br />Key goals<br />Business Value<br />change business<br />processes quickly<br />and effectively<br />IT Cost<br />Reduction &<br />Control<br />New<br />Functionality<br />2<br />1<br />3<br />0<br />Initial<br />Services<br />Architected<br />Services<br />Business<br />Service<br />
  31. 31. SOA maturity model<br />Specify policies for use of SOA in<br />collaboration with business and trading<br />partners<br />Implement cross-enterprise security<br />Key goals<br />Collaboration<br />with business &<br />trading partners<br />Business Value<br />Change business<br />processes quickly<br />& effectively<br />IT Cost<br />Reduction &<br />Control<br />New<br />Functionality<br />2<br />1<br />3<br />4<br />0<br />Initial<br />Services<br />Architected<br />Services<br />Business<br />Service<br />Collaborative<br />Services<br />
  32. 32. Collect and analyze business process oriented<br />real-time performance metrics<br />SOA maturity model<br />Implement ongoing business process<br />evaluation and re-engineering<br />Business <br />transformation<br />from reactive <br />To real-time<br />Implement self-correcting business<br />processes<br />Key goals<br />Collaboration<br />with business &<br />trading partners<br />Business Value<br />Change business<br />processes quickly<br />& effectively<br />IT Cost<br />Reduction &<br />Control<br />New<br />Functionality<br />2<br />1<br />3<br />5<br />4<br />0<br />Initial<br />Services<br />Architected<br />Services<br />Business<br />Service<br />Collaborative<br />Services<br />Measured<br />Services<br />
  33. 33. SOA Value: Myth or Reality?<br />Without Methodologies and Process Changes to Match<br />The Technology Change, the IT Organization will Suffer<br />The Promised SOA Advantages are Not Theoretical,<br />But Require Planned Process Changes To Be Gained<br />Cost Savings?<br />Reuse?<br />Agility?<br />Faster Development?<br />
  34. 34. Thank You<br />

×