1 / 46

Service Oriented Modelling

Service Oriented Modelling. Hatay Tuna Solutions Architect Microsoft. Head in the Cloud, Foot in the Mud. The FISH – Hatay Tuna. What to expect, what NOT to. The Agenda. What to expect. What is Service Oriented Modelling Also What is Microsoft Service Business Architecture The Jargon

lilianna
Download Presentation

Service Oriented Modelling

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. Service Oriented Modelling Hatay Tuna Solutions Architect Microsoft

  2. Head in the Cloud, Foot in the Mud The FISH – Hatay Tuna

  3. What to expect, what NOT to The Agenda

  4. What to expect • What is Service Oriented Modelling • Also What is Microsoft Service Business Architecture • The Jargon • Concepts behind SOM • The Journey • Method and Practices • The Demo • Visual Studio and DSLs – Cool stuff? • The End • What’s next

  5. First things first Service Oriented Modelling

  6. What is SOM • Capability composed of methods and toolsto enable incremental, repeatable, consistent and accountable service orientation within the enterprise or in the cloud based businessarchitecture, service orientation software factory principals with focus on business value and alignment between business and IT architecture...

  7. What is SOM • SOM is built on Microsoft Services Business Architecture (MSBA) • SOM is a Method supported by familiar Tools • SOM is optimised for • Service Orientation, • Business Process Automation • And Optimisation

  8. Introduction to Business Architecture Microsoft Service Business Architecture

  9. Why Business Architecture • Focus • Focus on “doing the right things” - what • Then “doing them right” - how • Context and Prioritisation • Provides structure to focus on “doing the right things” within the implementation • Logical, rational, and defensible • Optimisation • Services Orientation • Process Automation and Optimisation • Increased Productivity about “doing things right”

  10. The Next Revolution in Productivityby Ric Merrifield, Jack Calhoun and Dennis StevensHarvard School of Business, June 2008 http://harvardbusinessonline.hbsp.harvard.edu/b01/en/common/item_detail.jhtml?id=R0806D MSBA • Method to Decompose and Assess Capabilities • MSBA methodology delivers • Business Architecture • How and Where to Start with SOA • Business Case and Justification • Project Recommendations, Context and Prioritisation • Structure and Focus for SOA Decisions • Endorsed by the creators of • Six Sigma • Business process reengineering • Zachman • No need to spend 6–12 months on SOA analysis and paralysis

  11. 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: Centuries

  12. Good times... Expecting Change? BP 1 - Business Process BC 1 - Business Capability BC 2 - Business Capability BC 3 - Business Capability BC 4 - Business Capability

  13. Change happens... BP 1 - Business Process BP 1 - Business Process BC 1 - Business Capability BC 1 - Business Capability BC 2 - Business Capability BC 2 - Business Capability BC 3 - Business Capability BC 4 - Business Capability BC 3’ - Business Capability BC 4 - Business Capability

  14. Change WILL happen... BP 1 - Business Process BP 1’ - Business Process BC 1 - Business Capability BC 1 - Business Capability BC 2 - Business Capability BC 3’ - Business Capability BC 4 - Business Capability BC 3 - Business Capability BC 4 - Business Capability BC 2 - Business Capability

  15. Most important slide of all... • Build a Foundation on Business Capabilities • Build on STABLE, NOTVOLATILE • Build your Architecture on WHAT, NOT HOW • Manage Change: Change One at a Time • Compose Business Capabilities with Business Processes • Expose Business Capabilities and Processes through Business Services • Consume Business Capabilities and Processes through Composite Applications Looks familiar? Yes, SOM is aligned with Read World SOA too!

  16. Boring? NO, Exciting? YES! The Philosophy

  17. New stuff to think about... The Jargon

  18. The Jargon • Business Capability is an abstract view of what an individual business function does... • Business Capabilities are implemented by Service Components grouped by Business Services... • A Business Service is an contextual association between Business Capabilities and Service Components... • A Service Component may be software (Application, Web Service, Database...), hardware (Mobile Phone, Printer, Devices...) Business Capabilities Business Services Service Components

  19. A to B: Vision to Value... The Journey

  20. The Journey Business Capabilities are implemented by Business Services composed of Service Components Business Capabilities Business Services Service Components

  21. Service Oriented Modelling 1. Discover Capabilities

  22. Business Capability Map • Level 1 Foundational Capabilities • Operational Capabilities • Environmental Capabilities • Level 2 Capability Groups • Level 3+ Business Capabilities

  23. Business Capability Map 2000+ Generic Capabilities and Industry Specific Templates Capital Markets Retail Banking Legal Human Resources Retail Insurance Manage IT Services Professional Services

  24. Context and Focus This methodology provides a rapid process to decompose capabilities to granular levels.

  25. MSBA Analytical Model

  26. Service Oriented Modelling 2. Assess Capabilities

  27. Capability Assessment • Capture Properties • 180+ attributes to choose from • Inputs, Outputs, Exceptions, Service Level Expectations... • Then Assess • Business Value Contribution • Performance • Maturity • Compliance and Regulations • Interconnectedness

  28. A lot to choose from... • Purpose • Owner • Sourcing • Affiliation • Location • Type • Differentiating • Process Reuse • Source • Version • Customer • Customer Of • Process(es) that use the Capability • Dependency Capability(ies) • Collaborative Capability(ies) • Number of Dependencies • Number of Dependent Capabilities • Number of Collaborative Interactions • Customer Satisfaction • SLA/SLE Details Positive Variance Escalation Contact Positive Variance Notification Threshold Negative Variance Escalation Contact Negative Variance Notification Threshold Succession Plan Schedule Dependency Agreement/Contract Based Agreements/Contract Details Past Performance Desired Performance Best Practice Comparison Variability Volatility Human Interaction Value Add Process Variance Exceptions Electronic Input Output Data Used–Reference Data Used–Resource Data Used–Activity Triggering/Animating Function(s) Artifact(s)/Document(s) Created Security Functional Complexity Interface Complexity Passive/Active Request/Response on Inputs Offer/Acceptance at the Outset of the Capability Trigger Event Source Capability(ies) Content Filter Role Role Quantity Size Vertical Traditionally Outsourced Regulation-driven General

  29. Service Oriented Modelling 3. Model Capabilities

  30. Capability Models • Interactions and Relationships between capabilities • Capabilities can trigger, support or control other Capabilities • Capability Models help you understand and validate Business Processes...

  31. Business Capability Model Business Capability Model BP 1 - Business Process BC 1 - Business Capability BC 1 - Business Capability BC 2 - Business Capability BC 2 - Business Capability BC 4 - Business Capability BC 3 - Business Capability BC 3 - Business Capability BC 4 - Business Capability

  32. Service Oriented Modelling 4. Qualify Capabilities into Services

  33. Qualification • Qualification is the process of logically grouping implementation of one or more Business Capabilities into Business Services • Criteria are based on context and nature of the capabilities, there is NO single criteria that fit all but there are key questions and attributes: • Volatility, Outsourcing, Coupling, Shared Implementation Number for Time Performed, Success Metrics, Number of Consumers, Number of Dependencies...

  34. Service Oriented Modelling 5. Define Services

  35. Service Definition • Service Definition is the process of capturing characteristics and behaviour of the Business Service • Think requirements analysis, scenarios, requirements specifications, use-cases, service levels, non-functional requirements etc.

  36. Service Oriented Modelling 6. Model Services

  37. Service Models • Service Modelling is the process of defining interactions between Service Components... • Interactions may represents scenarios, use-cases... • Think Workflows, Sequence Diagrams...

  38. Service Oriented Modelling 7. Transform Services

  39. Transformation • Transformation is the process of generating partially or fully complete technology models • Code, document, configuration, test... • WCF Contracts, Workflows, HTML Documentation, Class Libraries etc. • Transforming Models in SOM is 100% customisable and extensible to enable consistent and predictable results for specific needs • XML/XSLT • LINQ • Text Templates • SOM API

  40. Practical Implementation of SOM in Visual Studio using DSLs The Demo

  41. Summary THE END?

  42. Remember? • Build a Foundation on Business Capabilities • Build on STABLE, NOTVOLATILE • Build your Architecture on WHAT, NOT HOW • Manage Change: Change One at a Time • Compose Business Capabilities with Business Processes • Expose Business Capabilities and Processes through Business Services • Consume Business Capabilities and Processes through Composite Applications Looks familiar? Yes, SOM is aligned with Read World SOA!

  43. Value Pillars • Focus on Business Value and Alignment • Top-Down approach for Business Value • Bottom-up approach for Alignment with IT • Enterprise Architecture = (Enterprise) x (Business Architecture + IT Architecture) • Capability Model -> Service Model -> Technology Model • Optimised for S + S • Accountable Service Orientation in the Enterprise and in the Cloud • Practical, Incremental, Repeatable delivery for Consistent and Predictable Solutions • Rich and Extensible • Familiar Microsoft Office and Visual Studio • Industry, Business and Scenario specific Modelling • Flexible Transformation to Technology Models

  44. The Technologies

  45. Summary • SOA is the Journey, NOT the END • SOM fills a BIG GAP by • Proven Methods and Familiar tools to tackle SOA • Focus on Business Value • Alignment between Business and IT Architecture • SOM is already Released! • SOM and MSBA are delivered through Microsoft Services • SOM toolset is customisable and extensible for your needs • “oslo” will be the platform of choice to perform SOM • Get in Touch • Talk to your Microsoft representative, ask about SOM • Contact me • Watch Channel 9 Interview on SOM • Start drawing some “Boxes and Lines” tomorrow! • Don’t miss • “Oslo” - Microsoft's Vision for the Future of Modelling By Robert Hogg

  46. Have a nice day and don’t forget to check-out other great sessions... The Goodbye

More Related