1 / 33

Capability Based Models and Service Oriented Architecture [ARC 201]

Capability Based Models and Service Oriented Architecture [ARC 201] . Boundary disputes, autonomy, and other problems in the nirvana of SOA. Ulrich Homann Chief Architect, WW Enterprise Services Microsoft Corporation. Big challenges – even after years of SOA practice.

prue
Download Presentation

Capability Based Models and Service Oriented Architecture [ARC 201]

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Capability Based Models and Service Oriented Architecture [ARC 201] Boundary disputes, autonomy, and other problems in the nirvana of SOA Ulrich Homann Chief Architect, WW Enterprise Services Microsoft Corporation

  2. Big challenges – even after years of SOA practice • Where and how to begin SOA? Can I buy SOA? • How to align services to business needs and priorities? • How to identify, scope and innovate through services? • What about the cloud? • New sourcing model for services • New software architecture model

  3. Objectives and suggested takeaways • Session Objective(s): • Drive successful service-oriented projects leveraging investments in business architecture • Demonstrate business relevancy of your services design • Determine services boundaries and completeness • Service-based system delivery requires: • Top-down planning (business alignment) • Bottoms-up execution

  4. Today

  5. 10 Years Later

  6. Durability WHAT DO WE DO? Capability HOW DO WE DO IT? People, Process and IT Abstraction Relative Change Organisational Structures... Process Models... Infrastructure Diagrams... Time Evolution of the Enterprise shaped by Competitive Strategy

  7. (Business) Capability • Abstract view of what an individual business function does • Relationships to how (process) the business function is achieved and who (organization) • Properties are used to define the characteristics for both current and future state within the project context • Stable representation that will survive even if the implementation changes • Common naming convention is verb and noun sequence, for example: • Provide Service, Request Resources, Manage Suppliers • Durability: a long time 

  8. Develop Products, Services Deliver Products, Services Plan and Manage Enterprise Generate Demand Collaborate Design Product/Service Sales Provide Service Property and Advisory Planning Collaboration Refine Existing Product/Service Marketing Procurement Project Management Strategic Collaboration Develop New Product/Service Channel Management Produce Product Financial Management Operational Collaboration Product/Service Management Customers Business Intelligence Human Resources Logistics Advanced Planning Technology People Process

  9. Order Management Sales Management Order Fulfilment Point of Sales Transportation Management Business Architecture decomposes organisation’s operational model into abstract business functions called capabilities; • Capabilities are Abstract, Stable and have Clear Boundaries Product Pricing Inventory Management Prospect Qualification Warehouse Management

  10. A real life business architecture

  11. Central Management Capability Clusters Changing Enterprise Topology Stable market conditions Focus on cost and efficiency Process-driven Economies of scale Vertical specialization/ hierarchy Changing market conditions Focus on agility and innovation Capability-driven Economies of scope Horizontal specialization

  12. Service A service is a business function that is well-defined and self-contained. Service Consumer Service Provider BusinessComponent ServiceFaçade

  13. Operational Requirements State Applications enforce manage composed of Policies governed by bound by exchange have Message Exchange Pattern Messages Contracts describe is a set of Schemas define structure of contain Service OrientationKey Concepts (Visual explanation helps) Services

  14. Qualify (map) capabilities to services Qualification is the process of mapping capabilities to services that are composed of service components that will provide the implementation of the capability and its associated contracts.

  15. Are we talking unholy alliance?

  16. Business architecture – relevant concepts

  17. Why do you care?

  18. Service-Orientation – relevant concepts

  19. Lifecycle

  20. To CRUD or not to CRUD…

  21. Follow the trail

  22. Business drivers drawing boundaries

  23. Technical drivers driving boundaries

  24. Operations drive boundaries

  25. Discover the pattern (interface contracts) • Collaborations connect Capabilities • Modularity • Patterns: Negotiation, Offer/Acceptance, … Capability 1.1 Capability 1.1.2 Capability 1.1.1 Collaboration Process Process Process Process Process Process

  26. Resources • A Business-Oriented Foundation for Service Orientation • Enterprise Architecture Strategy for SOA/S+S • From capabilities to services: moving from a business architecture to a SOA implementation

  27. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

  28. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related