Your SlideShare is downloading. ×
The Service Oriented Enterprise - Fontys Hogeschool Eindhoven
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Service Oriented Enterprise - Fontys Hogeschool Eindhoven

1,613

Published on

Presentations for Fontys Hogeschool Eindhoven in the Netherlands about the Service-Oriented Enterprise. This presentation explains the role of SOA and mashups in creating Service-Oriented Enterprises …

Presentations for Fontys Hogeschool Eindhoven in the Netherlands about the Service-Oriented Enterprise. This presentation explains the role of SOA and mashups in creating Service-Oriented Enterprises to business students. Presentation created at my previous company Capgemini.

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

  • Be the first to like this

No Downloads
Views
Total Views
1,613
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
49
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Source: http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html
  • As with many
  • SOA has been seen by many as THE magical thing that would transform and save companies. Companies adopted SOA without thinking about how it fitted in the overall company transformation. But what is this SOA thing or service-orientation that everyone is talking about? Let’s take a step back and look at the transport industry. Source: http://geekandpoke.typepad.com/.a/6a00d8341d3df553ef010535f2a9d0970b-pi
  • Drop the whole technical stuff and let’s have a look at the transport sector. Train is much more cheaper than truck for transportation, so why are companies still using trucks? Optimize for control (truck) or optimize for cost (train)? Source train picture: http://www.greenlogistics.org/SiteResources/6e889abc-fb8b-4a4e-a51d-a61b0115683c_Aggregates%20train.JPG Source truck picture: http://www.procesverbeteren.nl/LEAN/DAF3_truck.jpg
  • e.g. email hosting: it’s much cheaper to host it at Gmail, but due to compliance reasons companies prefer own hosted expensive MS Exchange on premise.
  • So, if I’d say that a SOA is like an orchestra, do you understand why? Every member of the team has its own specialty that he/she knows best. But we need a conductor that can keep it in hand and “orchestrate” Source picture: http://www.mtsymphony.org/images/orchestra.jpg
  • IT guys and business guys speak often different languages and often don’t really understand each other. But how are we going to define the steps in the process? (how to define the services?) Source: http://geekandpoke.typepad.com/.shared/image.html?/photos/uncategorized/2008/08/01/geeks.jpg
  • Give example of SAP
  • Difference between compose and orchestrate?
  • Source: http://www.webservices.org/index.php/weblog/website_editor/arriving_at_a_definition_of_soa
  • Source: http://carlaugustsimon.blogspot.com/2005/09/killer-soa-definition.html
  • Source: http://carlaugustsimon.blogspot.com/2005/09/killer-soa-definition.html
  • Source: http://blogs.zdnet.com/service-oriented/?p=490
  • Source: http://blogs.zdnet.com/service-oriented/?p=490
  • Source: http://www.aniltj.com/blog/2008/09/07/TheManyPrinciplesOfSOA.aspx
  • One of the principles of SOA is the reuse of the business functionality. But you can get the situation in large companies that they say “it’s not made by our department so I’m not going to use it”. Source: http://geekandpoke.typepad.com/.shared/image.html?/photos/uncategorized/2008/06/04/soabenefits.jpg
  • Source: http://geekandpoke.typepad.com/.shared/image.html?/photos/uncategorized/2008/09/09/day023.jpg
  • Real-time update from photo uploads on flickr.com, displayed on google maps.
  • Source: http://hinchcliffe.org/img/webmashupstyles.jpg
  • Transcript

    • 1. Lee Provoost Emerging Technologist, Capgemini Nederland B.V. The Service-Oriented Enterprise built on SOA and mashups
    • 2. Overview
      • Case study: transport business
      • Case study: plane ticket booking process
      • SOA: it’s in the eye of the beholder
      • Using the Crown model and TechnoVision to explain “Why SOA?”
      • Mashing it up together
      • Connecting the dots
    • 3. SOA IS DEAD. http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html
    • 4. GET OVER IT.
    • 5. REALLY.
    • 6. REALLY?
    • 7.  
    • 8. TRANSPORT BUSINESS
      • Case study
    • 9. Sending package from A to B vs. Optimize for COST Optimize for CONTROL
    • 10. Hybrid model: Mail services
    • 11. Hybrid model: LOtSS Identify where you can better optimize for CONTROL and where you can better optimize for COST. = LOtSS Local Optimization through Selective Specialization
    • 12. Hybrid model: Mail services Optimize for COST Optimize for CONTROL
    • 13. Optimization strategy?
      • Influenced by:
      • Compliance and regulation
      • Privacy
      • Corporate politics
      • Market conditions (e.g. economic downturn)
      • Expertise (lack of?)
      • Time-to-market pressure
      • Competition
    • 14. Optimization plan: how to
      • Look at the whole process (e.g. mail delivery process)
      • Break up in smaller steps
      • Optimize each individual step
      • Put everything back together
      DECOMPOSE – OPTIMIZE - RECOMPOSE
    • 15. PLANE TICKET BOOKING PROCESS
      • Case study
    • 16. SOA is like an orchestra
    • 17.  
    • 18. SOA: it’s in the eye of the beholder
      • “ I actually have no clue, but we / you should buy it” kind of consultant or analyst (or manager ;-) )
      • Business Analyst / Business Process Expert
      • Software Architect / Software Engineer
    • 19. Top-down vs. bottom-up Business Process IT Landscape ? IS BUSINESS LEADING OR IS IT LEADING? (ALWAYS?)
    • 20. So… Business Process Decompose (identify business functionalities) Optimize each business functionality Recompose Identify Services Compose & orchestrate Optimize for cost or control SOA
    • 21. SOA Definition #1 “ SOA Is a collection of things that work with other things without knowing much about the other things with the purpose of getting something from the other things. In SOA you can also have bigger things to communicate with other little things to achieve bigger things.” http://www.webservices.org/index.php/weblog/website_editor/arriving_at_a_definition_of_soa
    • 22. SOA Definition #2 "A service-oriented architecture (SOA) is the organizational and technical framework that enables an enterprise to deliver self-describing, platform-independent business functionality and make it available as building blocks of current and future applications.“ http://carlaugustsimon.blogspot.com/2005/09/killer-soa-definition.html
    • 23. SOA Definition #2 "A service-oriented architecture (SOA) is the organizational and technical framework that enables an enterprise to deliver self-describing, platform-independent business functionality and make it available as building blocks of current and future applications .“ http://carlaugustsimon.blogspot.com/2005/09/killer-soa-definition.html
    • 24. SOA Definition #3 “ In Service-Oriented Architecture autonomous, loosely-coupled and coarse-grained services with well-defined interfaces provide business functionality and can be discovered and accessed through a supportive infrastructure. This allows internal and external system integration as well as the flexible reuse of application logic through the composition of services to support an end-to-end business process.“ http://blogs.zdnet.com/service-oriented/?p=490
    • 25. SOA Definition: attempt #3 “ In Service-Oriented Architecture autonomous , loosely-coupled and coarse-grained services with well-defined interfaces provide business functionality and can be discovered and accessed through a supportive infrastructure. This allows internal and external system integration as well as the flexible reuse of application logic through the composition of services to support an end-to-end business process .“ http://blogs.zdnet.com/service-oriented/?p=490
    • 26. Key principles of SOA
      • Services in a SOA
      • represent independent business functionality  reusability
      • are loosely-coupled
      • use open standards  interoperability
      • are well-defined (service contract)
      • can be composed and orchestrated
      http://www.aniltj.com/blog/2008/09/07/TheManyPrinciplesOfSOA.aspx
    • 27.  
    • 28. “ WHY SOA?”
      • Using the Crown model and TechnoVision to explain
    • 29.  
    • 30. Quick recap on the Crown model Pressure for Business Change Pressure for IT Stability Comply The Enterprise Transactions and Data; ERP and Legacy Applications Organize The use of SOA to achieve cohesive executions Differentiate A Business Manager’s Customizable Solution Personalize An Individual’s use of the capabilities of Web 2.0
    • 31. Business and Technology Architecture Governance Model Loose Coupled Business Technology Tight Coupled Information Technology SOA the coupling layer between both Personalise An Individual’s capability to choose their ‘experience’ in how they wish to ‘Interact’ and ‘collaborate’ Differentiate A Manager’s capability to build locally unique ‘differentiating’ capabilities both externally and internally Organise (SOA) Common, shared core processes that support each differentiated offer above, and connect to transactional IT applications below Comply (ERP, etc.) Traditional Enterprise Applications with organised procedures and data integrity, keeping compliant business results
    • 32. Quick recap on TechnoVision Open standards and Service-orientation Invisible infostructure Sector-as-a-service Process- on-the-fly Thriving on data From transaction to interaction You experience
    • 33. TechnoVision Conceptual Technology Architecture Personalise Differentiate Comply (ERP, etc.) Organise (SOA) Thriving on Data Process on the fly Sector as A Service From Transaction to Interaction You Experience Invisible Infostructure Open Standards Open Source 1 2 3 4 5 6 7
    • 34. MASHING IT UP TOGETHER
      • And now…
    • 35. TechnoVision Conceptual Technology Architecture Personalise Differentiate Comply (ERP, etc.) Organise (SOA) Thriving on Data Process on the fly Sector as A Service From Transaction to Interaction You Experience Invisible Infostructure Open Standards Open Source iPodification Rich Internet applications Mashup applications Role-based user portals 1 2 3 4 5 6 7
    • 36. Example: flickrvision.com
    • 37. Example: soup-soup.net
    • 38. Tool: JackBe Presto
    • 39. Tool: Yahoo! Pipes
    • 40. Tool: Mozilla Ubiquity
    • 41. Web Mashup Styles by Dion Hinchcliffe http://hinchcliffe.org/img/webmashupstyles.jpg
    • 42. Mashup applications definition Mashup applications quickly combine services and underlying applications from potentially many sources in- or outside the organization to create composite frontend applications.
    • 43. CONNECTING THE DOTS
      • SOA + Mashups
    • 44. Do you see it?
      • SOA
      • Mashups
      • Mashup applications quickly combine services and underlying applications from potentially many sources in- or outside the organization to create composite frontend applications.
      • A service-oriented architecture is the organizational and technical framework that enables an enterprise to deliver self-describing, platform-independent business functionality and make it available as building blocks of current and future applications.
    • 45. Connecting the dots Adaptive Infrastructure
    • 46. References
      • William Oellermann – Enabling the Service-Oriented Enterprise http://msdn.microsoft.com/en-us/library/bb245664.aspx
      • Andy Mulholland – An external changing world is creating the drivers for TechnoVision
      • Andy Mulholland – Mesh Collaboration http://www.meshcollaboration.com
      • Microsoft – Service-Orientation and its role in your connected systems strategy http://msdn.microsoft.com/en-us/library/ms954826.aspx
      • IBM Systems Journal – Impact of Service-Orientation at the business level http://www.research.ibm.com/journal/sj/444/cherbakov.html
      • Anne Thomas Manes – SOA is dead, long live services http://apsblog.burtongroup.com/2009/01/soa-is-dead-long-live-services.html
      • Geek and Poke cartoons: http://geekandpoke.typepad.com/
      • Dana Gardner – Predicting vitality of SOA completely misses the point, legacy IT is dead http://blogs.zdnet.com/Gardner/?p=2772
    • 47. Q&A Lee Provoost http://twitter.com/leeprovoost [email_address]

    ×