Determining SOA Success

464 views
319 views

Published on

Presentation from SOA Symposium in DC on April 3, 2009

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
464
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Determining SOA Success

  1. 1. Determining SOA Success JP Morgenthal SOA, BPM & Cloud Strategist jpmorgenthal.com
  2. 2. Agenda <ul><li>Defining SOA </li></ul><ul><li>Classes of SOA </li></ul><ul><li>SOA Success Factors </li></ul><ul><li>Wrapping It All Up </li></ul>
  3. 3. Defining SOA <ul><li>SOA represents the archetype for delivery of anything as a service: Software, hardware, telecommunications, call center, marketing, etc. </li></ul><ul><li>If something can be compartmentalized with a formalized input and result and can be measured then it can be delivered as a service. </li></ul><ul><li>One or more of these services working together to provide a higher-level function is an SOA </li></ul><ul><ul><li>One service does not an SOA make! </li></ul></ul>
  4. 4. Success in SOA is… <ul><li>Contextual </li></ul><ul><li>Based on intention </li></ul><ul><li>Non-deterministic </li></ul>
  5. 5. Classes of SOA
  6. 6. Classes of SOA <ul><li>Enterprise SOA Design </li></ul><ul><li>System Design </li></ul><ul><ul><li>Infrastructure Design </li></ul></ul><ul><ul><li>Application Design </li></ul></ul><ul><li>Service Design </li></ul><ul><li>Semantic Design </li></ul>
  7. 7. SOA Success Factors
  8. 8. Enterprise SOA Design Success Factors <ul><li>Organizational alignment </li></ul><ul><li>Architectural plan </li></ul><ul><li>Business/Technology Mapping </li></ul>
  9. 9. System Design Success Factors <ul><li>Infrastructure Design Success Factors </li></ul><ul><li>Application Design Success Factors </li></ul>
  10. 10. Infrastructure Design Success Factors <ul><li>Cost reductions </li></ul><ul><li>Greater accessibility </li></ul><ul><li>Infrastructure-as-a-Service </li></ul><ul><ul><li>Rapid provisioning </li></ul></ul><ul><ul><li>Bandwidth optimization </li></ul></ul><ul><ul><li>CPU Utilization </li></ul></ul><ul><ul><li>Elasticity </li></ul></ul><ul><ul><li>Metering / Monitoring </li></ul></ul>
  11. 11. Application Design Success Factors <ul><li>Higher quality output </li></ul><ul><li>Reduced development costs </li></ul><ul><li>Well-defined contracts </li></ul><ul><li>Loose-Coupling </li></ul><ul><li>Reuse </li></ul><ul><li>Version management </li></ul>
  12. 12. Service Design Success Factors <ul><li>Satisfied community of consumers </li></ul><ul><li>Repeatable success </li></ul><ul><li>Easily recognized value proposition </li></ul>
  13. 13. Semantic Design Success Factors <ul><li>Appropriate levels of granularity in service </li></ul><ul><ul><li>Need for change is minimal as consumer base grows </li></ul></ul><ul><li>Services model business activity </li></ul>
  14. 14. Wrapping It All up
  15. 15. Success Is Contextual <ul><li>What is your goal? </li></ul><ul><ul><li>Long-term agility? </li></ul></ul><ul><ul><li>Reducing costs? </li></ul></ul><ul><ul><li>Smoother IT/Business collaboration? </li></ul></ul>
  16. 16. Success Is Based On Intention <ul><li>What are you setting out to accomplish? </li></ul><ul><ul><li>Proof-of-Concept </li></ul></ul><ul><ul><li>Complete re-engineering </li></ul></ul><ul><ul><li>Semantic mapping </li></ul></ul>
  17. 17. Success Is Non-deterministic <ul><li>Non-determinism </li></ul><ul><ul><li>An outcome with one or more choice points where multiple different continuations are possible, without any specification of which one will be taken. </li></ul></ul><ul><li>What you think is successful, may only be a successful step in a much larger solution domain </li></ul>
  18. 18. Q&A me [at] jpmorgenthal.com

×