Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
SOA – Successful Adoption and Barriers IDC Service-Oriented Architecture Conference 2005 Rick Robinson, IT Architect, IBM ...
Agenda <ul><li>What works? </li></ul><ul><li>Barriers </li></ul><ul><li>Roadmaps </li></ul><ul><li>Summary </li></ul>
What Works? Business scenarios, technologies and governance
What Works? Business Scenarios <ul><li>Multi-channel </li></ul><ul><ul><li>Multiple technology channels, e.g. desktop, bro...
<ul><li>Legacy </li></ul><ul><ul><li>e.g. CICS “routing transaction” using simple structured data formats </li></ul></ul><...
Reseller channels, e.g. supermarkets Branches Online bank Corporate Bank ... etc. ... Service Gateway Account Management P...
Barriers Mismatches, trust and … governance
Barriers: Mismatches <ul><li>Narrow drivers, broad ambition </li></ul><ul><ul><li>Are current business goals to reduce cos...
Barriers: Trust Application Service 1 Service 2 Service 3 Service Z No need to test No need to test Test <ul><li>If SOA us...
Barriers: Governance Store Client (Catalogue) Sales Management Client Store Client (Orders) Product Management Client ... ...
Barriers: Governance ITA SOA Project ! ITS Infrastructure Can it be operated? Architecture  Review Board Operational TDA D...
Roadmaps
There is no roadmap … <ul><li>Standards Based Model for all Service Interaction Aspects </li></ul><ul><ul><li>Important as...
Summary
Summary <ul><li>SOA has been repeatedly proven over the last decade (at least!) </li></ul><ul><li>Open standard and produc...
End
 
 
 
Timings <ul><li>3 minutes intro </li></ul><ul><li>3 slides in first section finish on 5, 7, 9 minutes </li></ul><ul><li>1 ...
Prochain SlideShare
Chargement dans…5
×

IBM Software Group ® SOA – Successful Adoption and Barriers

389 vues

Publié le

  • Login to see the comments

  • Soyez le premier à aimer ceci

IBM Software Group ® SOA – Successful Adoption and Barriers

  1. 1. SOA – Successful Adoption and Barriers IDC Service-Oriented Architecture Conference 2005 Rick Robinson, IT Architect, IBM EMEA WebSphere Lab Services [email_address]
  2. 2. Agenda <ul><li>What works? </li></ul><ul><li>Barriers </li></ul><ul><li>Roadmaps </li></ul><ul><li>Summary </li></ul>
  3. 3. What Works? Business scenarios, technologies and governance
  4. 4. What Works? Business Scenarios <ul><li>Multi-channel </li></ul><ul><ul><li>Multiple technology channels, e.g. desktop, browser pervasive </li></ul></ul><ul><ul><li>Multiple brands </li></ul></ul><ul><li>Intermediary, B2B or dot.com models </li></ul><ul><ul><li>Small to large </li></ul></ul><ul><ul><li>Service aggregation e.g. financial portals </li></ul></ul><ul><ul><li>dot.com integration e.g. Amazon, e-Bay </li></ul></ul><ul><li>New Applications </li></ul><ul><ul><li>Well-targetted process automation </li></ul></ul><ul><li>Integration or Consolidation </li></ul><ul><ul><li>Bottom-up integration architectures of reasonable ambition </li></ul></ul><ul><ul><li>Single view of data </li></ul></ul>
  5. 5. <ul><li>Legacy </li></ul><ul><ul><li>e.g. CICS “routing transaction” using simple structured data formats </li></ul></ul><ul><ul><li>… increasingly migrating to Web services </li></ul></ul><ul><li>Enterprise Application Integration (EAI) </li></ul><ul><ul><li>XML interfaces and message formats </li></ul></ul><ul><ul><li>Communication through EAI technology e.g. asynchronous messaging </li></ul></ul><ul><ul><li>Custom API frameworks provide application support </li></ul></ul><ul><ul><li>… increasingly migrating to Web services </li></ul></ul><ul><li>Web services </li></ul><ul><ul><li>Many current uses of Web services are for basic point-to-point integration </li></ul></ul><ul><ul><li>Some more advanced organisations have built SOA infrastructures with extensive use of Web services </li></ul></ul><ul><ul><li>… becoming more common as Web services mature </li></ul></ul>What Works? Technologies
  6. 6. Reseller channels, e.g. supermarkets Branches Online bank Corporate Bank ... etc. ... Service Gateway Account Management Payments etc. What Works? Aligned Service and System Ownership <ul><li>One layer of services </li></ul><ul><li>Organisation matches service architecture </li></ul><ul><li>Obvious owners of services and supporting infrastructure </li></ul>Operations Director Channel Owners System Owners
  7. 7. Barriers Mismatches, trust and … governance
  8. 8. Barriers: Mismatches <ul><li>Narrow drivers, broad ambition </li></ul><ul><ul><li>Are current business goals to reduce cost or develop new business? </li></ul></ul><ul><ul><li>Is the level of sponsorship consistent with the scope of impact? </li></ul></ul><ul><li>Inappropriate combinations of risk </li></ul><ul><ul><li>Pilot project, new technology </li></ul></ul><ul><ul><li>Production project, conservative technology </li></ul></ul><ul><ul><li>Many other combinations! </li></ul></ul><ul><li>Scepticism – adopting SOA successfully requires cultural change </li></ul><ul><ul><li>“ It’s nothing new” </li></ul></ul><ul><ul><li>“ The technology doesn’t work” </li></ul></ul><ul><ul><li>“ It’s not for us” </li></ul></ul>
  9. 9. Barriers: Trust Application Service 1 Service 2 Service 3 Service Z No need to test No need to test Test <ul><li>If SOA uses intermediaries to insulate service consumers from changes to service implementations, how do services consumers know when to re-test? </li></ul><ul><li>Until services are trusted, regression testing will be performed in all cases </li></ul><ul><li>Automated testing scripts and tools can be used to minimise impact </li></ul>Change to irrelevant optional schema Change to relevant optional schema or mandatory schema Service implementation changed or substituted
  10. 10. Barriers: Governance Store Client (Catalogue) Sales Management Client Store Client (Orders) Product Management Client ... etc. ... Service Bus Order Services Product Services etc. Pricing Services Accounts Product Management etc. ERP <ul><li>No clear point of ownership for common services </li></ul><ul><li>Infrastructure owned by IT, clients and back end systems owned by lines of business </li></ul><ul><li>Tends to result in a proliferation of variations of “common” services dedicated to specific channels </li></ul>
  11. 11. Barriers: Governance ITA SOA Project ! ITS Infrastructure Can it be operated? Architecture Review Board Operational TDA Does it advance our strategy? Enterprise Architecture Group Our strategy is SOA I need a new mortgage system
  12. 12. Roadmaps
  13. 13. There is no roadmap … <ul><li>Standards Based Model for all Service Interaction Aspects </li></ul><ul><ul><li>Important aspects include protocols, interface definitions, message formats, APIs, directories etc. </li></ul></ul><ul><li>Service Enable Legacy Systems and Applications </li></ul><ul><ul><li>Analogous to JDBC enablement of databases for J2EE </li></ul></ul><ul><li>Implement a High Quality of Service Infrastructure </li></ul><ul><ul><li>Asynchronous messaging, assured delivery, security, transactions and compensation etc. </li></ul></ul><ul><li>Establish a comprehensive model and implementation of different types of service </li></ul><ul><ul><li>Business process vs. business transaction vs. technical service vs. external service vs. legacy service etc. </li></ul></ul><ul><li>Service directory and re-use strategy </li></ul><ul><ul><li>Establishing the development culture, publishing and discovering services, internally and externally etc. </li></ul></ul><ul><li>Establish organisations and processes for governance and ownership </li></ul><ul><ul><li>Enterprise Architecture governance, service ownership etc. </li></ul></ul>… but there are many individual steps to take in an order that makes sense to your organisation.
  14. 14. Summary
  15. 15. Summary <ul><li>SOA has been repeatedly proven over the last decade (at least!) </li></ul><ul><li>Open standard and product support is increasingly rapidly in sophistication and maturity </li></ul><ul><li>In it’s broadest form, SOA is an approach to Enterprise Architecture, and there is no skirting the difficult issues associated with that </li></ul><ul><li>But a big-bang approach is not mandated … </li></ul><ul><ul><li>… a flexible, incremental approach moulded to business needs and strategy is the most likely to succeed </li></ul></ul>
  16. 16. End
  17. 20. Timings <ul><li>3 minutes intro </li></ul><ul><li>3 slides in first section finish on 5, 7, 9 minutes </li></ul><ul><li>1 minute bridge </li></ul><ul><li>4 slides in second section finish on 12, 14, 16, 18 minutes </li></ul><ul><li>1 minute bridge </li></ul><ul><li>1 slide in last section finishes on 21 minutes </li></ul><ul><li>4 minutes wrap-up and contingency </li></ul>

×