1. Pooya Darugar Architect, Microsoft Gulf

2.  What is SOA, What isn’t SOA  The important A in SOA  Business Modeling  How to get started  The forgotten aspects of SOA

3. What about all those buzz words and complicated specs I keep hearing about?? A design philosophy that leverages existing investments in the creation of flexible solutions that are more responsive to your business needs

4. 1. SOA is a design philosophy independent of any product, technology or industry trend 2. SOAs may be realized via web services but using web services will not necessarily result in a SOA 3. EDI and CORBA were early examples of SO 4. SOA is not a methodology 5. SOA should be incremental and build on your current investments 6. SOA can be done in house 7. SOA is a means, not an end 1. SOA is a technology 2. SOA requires Web Services 3. SOA is new and revolutionary 4. SOA ensures the alignment of IT and business 5. SOA requires a complete technology and business processes overhaul 6. SOA requires an army of consultants 7. We need to build a SOA Facts Myths Deliver a solution, not a SOA

5. User Assign ID Check Knowledgebas e Solve Problem Bill Customer Assign ID Check Catalog Check Inventory Bill Customer DataEntitiesLoB SystemsSecurity LoB Systems DataEntities

6. Adapter BP Platform LoB Systems User LoB Systems BillingService IDService DataServices CustomerService ProductServiceSecurityService ServiceAgent

8. User DataEntitiesLoB SystemsSecurity LoB Systems DataEntities Billing Service ID Service Step 1: Ignore Solution Boundaries Step 2: Group Similar Functions, Expose as a Service

9. LoB Systems Billing Service User DataEntitiesLoB SystemsSecurity DataEntities Step 3: Hide data source behind services ID Service Data Services

10. LoB Systems Billing Service User EntitiesLoB SystemsSecurity Entities Step 4: Expose Entities as Services for “Single View” of Customer, Product, others… ID Service Data Services Customer Service Product Service

11. LoB Systems Billing Service User LoB SystemsSecurity Step 5: Hide security behind reusable services ID Service Data Services Customer Service Product Service Security Service

12. LoB Systems Billing Service User LoB Systems ID Service Data Services Customer Service Product Service Security Service Agent Step 6: Use service agents for dynamic assembly of rich user experiences across multiple devices

13. Adapter BP Platform LoB Systems Billing Service User LoB Systems ID Service Data Services Customer Service Product Service Security Service Agent Step 7: Use a BP Platform for aggregating services into workflows and integration with legacy systems

14. Adapter BP Platform LoB Systems User LoB Systems BillingService IDService DataServices CustomerService ProductServiceSecurityService ServiceAgent Step 8: Optimize infrastructure to take advantage of the services-based environment

15.  What have we really created:  Modeling the business  Re-usable components Agility

16. 16 Business Model Technology Model System Model (Classic Client-Server Based)

17. 17  Business people are not good at explaining what they do  Often fail to distinguish between what they do and how they do it  Use jargon and assume a level of basic knowledge  IT people are not good at explaining what they do  Often fail to express strategies in terms of business value  Use jargon and assume a level of basic knowledge  Important to finally fix this because the role of IT is changing:  Used to be cost reduction  Now it is a major business differentiator

18. 18 Business Model Service Model Technology Model System Model (Modern Service Based) The service model is the common ground between business and IT

19. 19 Business Model What  Capabilities How  Business Processes Technology Model Service Interface Orchestration Engine Service Implementation Service Host Service Model Service Contract OrchestrationService Management SLASLE

20. 20 Business Model What  Capabilities Technology Model Service Interface Orchestration Engine Service Implementation Service Host Service Model Service Contract OrchestrationService Management SLA How  Business Processes SLE

21. 21  Has two major constituents:  A capability map describing business capabilities  A simple, short, prescriptive process of analysis  Exploits insights:  Business capabilities are relatively stable and enduring  Helps address two fundamental problems:  IT projects constantly repeat themselves…  … and only rarely introduce true business innovation

22. 22  Motion is  Patent-pending business architecture model with tools  Set of heat mapping tools  Training classes for using the model and the tools  endorsed by the creators of Six Sigma and Business Process Reengineering  Motion delivers  Business architecture map (with properties)  Project recommendations – what to change in terms of people, process, and IT, in the context of cost, benefit, and risk  Several forms are available  2-4 week business architecture training projects  Motion Methodology – one or all four phases, usually two weeks per phase  Not strategy consulting – it is business consulting  Proven  Mature

23. 23 Develop Products & Services Plan and Manage the Enterprise Generate Demand Deliver Products & Services Customers Customer-Facing Channel Partners Financial Providers Governments (regulation and infrastructure) Suppliers Logistics Providers Collaborate

24. 24 Develop Products & Services Plan and Manage the Enterprise Generate Demand Deliver Products & Services Customers Customer-Facing Channel Partners Financial Providers Governments (regulation and infrastructure) Suppliers Logistics Providers Collaborate 3. Deliver Products and Services 1.Provide Service 2.Advanced Planning 3.Procurement 4.Produce Product 5.Logistics 3.3 Procurement 1.Sourcing and Supplier Contract Management 2.Purchasing 3.Receiving of Indirect/ Capital Goods 3.3.2 Purchasing 1.Request Resources 2.Acquire/Purchase Resources 3.Manage Suppliers 3.3.2.1 Request Resources 1.Create Purchase Requisitions 2.Manage Requisition Approval Process 3.Perform Encumbrance Check 4.Create Auction Bids

25. 25 StartStart People Procedures Technology

26. 26 Develop Products & Services Plan and Manage the Enterprise Generate Demand Deliver Products & Services Customers Customer-Facing Channel Partners Financial Providers Governments (regulation and infrastructure) Suppliers Logistics Providers Collaborate Value propositionOperating model Capabilities Metrics IT project portfolio IT projects SOA Outsourcing Partnerships Offshoring Self-service

27.  Top Down – eg. Motion  Bottom Up

28.  How it works:  Define a business architecture  Using, for example, Microsoft’s Motion methodology  Discover what services are required  Create service-oriented apps based on this  Pros:  It’s elegant, clean, and sensible  Cons:  It’s very difficult in most organizations  Getting the up-front funding and business buy-in is tough  Keeping up with business change is also tough

29.  How it works:  Build a service-oriented app  Then build another one  Next, work on central SOA issues, e.g., security and management  Then build another service-oriented app...  Pros:  It’s the only approach that has worked in most organizations  Cons:  It’s an inelegant, piecemeal way to address the problem

30.  SOA is about Agility  Agile principles  Requirements will change  Feedback, feedback, feedback!  Measurement and Adjustments  Get good people to work together effectively  SOA center of excellence  Holistic view but choose part of the business  Start small then scale-up  Pragmatism  Oscillate top down/bottom up

32. Entity Services Process Services Infrastructure Services Clients and Agents Technology Architecture Information Architecture Activity Services  Entity Identification  Entity Factoring  Service Identification  Service Factoring  Process Specification  Endpoint (Touchpoint) identification  Role Mapping  SLAs  …

33.  Schema definition  Message definition  Contract definition  Message handling  Process management  Transaction model  Operational compliance  Exception handling  Message to Object mapping  Refinement of Analysis  … Contracts Service Process Document A Document C-1 Document C-2 Document B Either C-1 or C-2 Process

34.  Security  Access control  Monitoring  Management  QoS and SLA enforcement  Versioning  Scalability  Dealing with unreliability  Exception routing  Caching Service Message Processing Infrastructure Serialize Encrypt Sign Deserialize Authenticate Authorize Audit Log Reliable messaging

35.  This is the hardest aspect of building a service- oriented application  And almost nobody has much experience  The goal: define the right use cases for future apps that will use these services  Some suggestions:  Expose business logic via a services wrapper  Don’t expose objects directly  Expect to make mistakes  And be supportive when your customers screw up  Don’t let developers decide which services to expose  Start with the Contract and Schema  Use industry standards if available

36.  Some organizations have people in a business analyst role  In a service-oriented world, they’ll matter more  Where BAs can potentially help:  Defining services  Creating and updating process logic (orchestrations)  Defining and modifying business rules

37. SOA and Web Service Advantages are Not Automatic Reality is, benefits are often only realised when combined with  Change in culture  Investment in future needs, not just today’s short term issues  Proper understanding of business requirements (today and tomorrow)  Careful analysis and system design  Flexible and agile implementations using appropriate technology and componentization  Business Process Re-engineering  Business commitment and involvement  Adequate funding recognising changes in ownership and responsibility

38.  SOA is about Architecture  Service Oriented Infrastructure make the plumbing for SOA easier  This is the part you can buy from a vendor  SOA - business modeling, service modeling  Motion  Real World SOA – middle out approach  It doesn’t end there  Developing services is the easy part  Managing and governing them in a loosely coupled world is much more complex

39. Pooya Darugar pooyad@microsoft.com http://blogs.msdn.com/pooyad