SOA is an evolution from past approaches and focuses on using existing systems, data, and processes, only adding new technology when needed. It is designed for change and adaptive reuse of services rather than being tightly coupled and built in isolation. SOA involves cataloging all business processes and services to create a shared, reusable architecture and vision for flexible business process execution across systems. The first steps typically involve process discovery and documentation rather than trying to define a rigid template or roadmap.

1. OK-SOA Open Knowledge Service Orientated Architecture

2. We have had

3. We have had OnDemand

4. We have had OnDemand Adaptive Enterprise

5. We have had OnDemand Adaptive Enterprise eBusiness

6. We have had OnDemand Adaptive Enterprise eBusiness So why is SOA supposed to be any different

7. We had this

8. were promised this

9. but ended up with this

11. Beware of vendor messages I am not vendor bashing, they do provide great thought leadership – but no magic wands.

12. SOA is not a different way

13. Its an evolution

14. SOA is different from the past

15. SOA is different from the past Its about using what you already have

16. Your Systems

17. Your Systems Your Data

18. Your Systems Your Data Your Processes

19. Your Systems Your Data Your Processes and only adding complimentary technology when it is needed to enable or change an agile business.

20. Old Way New Way Designed to last Designed for change

21. Old Way New Way Tightly Coupled Agile and Adaptive

22. Old Way New Way Build in isolation Build Services

23. Old Way New Way Code is King Metadata Princess

24. Old Way New Way Takes time to complete Interactive progressive development

25. Old Way New Way Middleware Focus Architecture Focus

26. Old Way New Way Homogeneous Hetrogeneous

27. Old Way New Way Programmers Analysts

28. Old Way New Way Documentation Library Best Practice Library

29. Old Way New Way Read a document and design the process Write a document which is the design

30. SOA has four pillars

31. OK…………SOA But how do I start

32. Think of your computer systems as a business asset and the business as processes, some of which rely partially or exclusively on Services

33. Think of systems integration as a natural outcome to building and combining Services

34. Think of SOA as an approach for dealing with frequent, and often unpredictable change…

35. Think of SOA as an approach for dealing with frequent, and often unpredictable change… SOA should be promoted as a drive towards “simple and easy” not “rapid and reactive”

36. OK…………SOA But what is it

37. Its not software – its best practices

38. Its not software – its best practices It’s a little bit of methodology, a lot of opportunistic process improvement and loads of innovation

39. Its not software – its best practices It’s a little bit of methodology, a lot of opportunistic process improvement and loads of innovation Success Tip – Blog about ROI successes and Improvement achievements – people follow success, businesses follow what is successful.

40. It is not “think it, done”

41. It is not “think it, done” SOA will be a gradual adoption of the principles – in the same way that an organisation does not become “Six Sigma” overnight

42. Remember; you evolve into SOA

43. It is not a Policing Policy or a Rule Set for the Business

44. It is not a Policing Policy or a Rule Set for the Business Manage SOA < Manage with SOA

45. It is not a Policing Policy or a Rule Set for the Business Manage SOA < Manage with SOA Policy and Procedure = Understanding

46. It is not a Policing Policy or a Rule Set for the Business Manage SOA < Manage with SOA Policy and Procedure = Understanding Understanding = Adoption

47. It is definitely not Silos and Areas – or even groups

48. It is definitely not Silos and Areas – or even groups SOA means shared and reused Systems & Services

49. It is definitely not Silos and Areas – or even groups SOA means shared and reused Systems & Services Reuse means shared, not duplicated

50. It is definitely not Silos and Areas – or even groups SOA means shared and reused Systems & Services Reuse means shared, not duplicated Shared may mean centralised

51. SOA is not a road map, it’s a vision

52. Do not try and work out the detail,

53. Do not try and work out the detail, most answers will end up as “ it depends ”

54. Do not try and build services as a beginning “ build it and they will come” only works for sports stadiums

55. Do not limit processes to three or four layers of sub processes

56. Do not limit processes to three or four layers of sub processes N+1 is a natural state – policy management and a good process tool ( Aris, iGrafx, Process Master, Provision ) coupled with a good document/content management system ( SharePoint, Meridio, Documentum ) will do the trick.

57. SOA is not a team play

58. SOA requires authority and authorisations before the work, not during the work

59. Services must be under joint and several ownership across the business – but focused and assigned responsibilities have to exist.

60. OK…………SOA Quick recap on the definition

61. Service Oriented Architecture: Is a software design approach in which a client application requests one or more services from another application that provides similar or complementary services. The design allows internal and external business processes to be combined and recombined to support flexibility in business process execution.

62. So a vision statement might look like

63. So a vision statement might look like Our SOA vision is to create a complete business process fusion on our global network of independent infrastructures. We believe in a federated access management policy for services, along with the development of a business process best practice library and the recognition of our centres of excellence.

64. So a vision statement might look like Our SOA vision is to create a complete business process fusion on our global network of independent infrastructures. We believe in a federated access management policy for services, along with the development of a business process best practice library and the recognition of our centres of excellence. Being politically correct is not being weak – systems are easy, people are harder to change so need to be won over slowly.

65. My point….. Business Leaders make commercial and operational decisions based on features and benefits for the domain responsibilities they have to protect.

66. My point….. Business Leaders make commercial and operational decisions based on features and benefits for the domain responsibilities they have to protect. Show SOA as an individual set of improvements that will require their authorisation of the benefits when it includes them, not as something that will be enforced on them.

67. OK…………SOA What first….

68. Catalogue all your business processes . SOA does not start with the quality of your process library, it needs quantity to be credible.

69. Catalogue all your business processes . SOA does not start with the quality of your process library, it needs quantity to be credible. Success Tip: Achieve control by putting in something like Process Master and give it to colleagues to do quick and easy process discovery. This will give you the text, models and documentation you need going forward and will fill up your process repository quickly and easily. You could also do Visio & Word, but……..

70. Catalogue your Services

71. Catalogue your Services Don’t do a database, do a Blog and get a Wiki, the future steps you take in this area will be defined from there

72. SOA is not a static fact, it lives and develops like a garden plant.

73. SOA is not a static fact, it lives and develops like a garden plant. So do step one and step two, and as for what step three will be………

74. SOA is not a static fact, it lives and develops like a garden plant. So do step one and step two, and as for what step three will be……… Its like I said before, that depends on you and your business – there is no template, your SOA is as unique as your finger print.

75. If non of this is of any use to you and you still believe that you do need a template, structure or road map , type in SOA in Google and you will get hundreds. Every one is written to tell you what someone else would do if they were you and working for your company. Which is what they want to be by being employed as consultants and sell you loads of software . If you want SOA success, be an SOA champion, or go sit beside one.

76. The End Almost

77. View my business process discovery video on……. Http://www.ProcessMaster.com If you want a good Blog on SOA, Sandy Kemsley is worth reading Http://www.column2.com Thank You