Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Show in a similar fashion the base reference model decoupled from implementation. Reasons why it differs is… Service Description has relationship to contract.
  • SOAReferenceModel-Generic-rev1_05-03.ppt

    1. 1. SOA Reference Model Generic Presentation DRAFT: Not approved by the OASIS SOA RM TC.
    2. 2. Agenda <ul><li>What is SOA; what is a reference model for SOA </li></ul><ul><li>Why is a reference model needed </li></ul><ul><li>The OASIS SOA RM TC </li></ul>
    3. 3. In order define SOA… <ul><li>If SOA is Architecture, as the name implies, it should be definable as architecture. </li></ul><ul><li>We should not do it by referencing an implementation. </li></ul><ul><li>DEFINITION (from Charter): </li></ul><ul><ul><li>“ Architecture: A software architecture for a system is the structure or structures of the system, which consist of elements and their externally visible properties, and the relationships among them.” </li></ul></ul>
    4. 4. Closer look: “Service Oriented” <ul><li>Is a paradigm (model) for developing architecture. </li></ul><ul><ul><li>Focus herein is “software & systems architecture” </li></ul></ul><ul><li>“ Services” are the central concept, yet other concepts are present in all implementations. </li></ul><ul><li>Is not currently defined other than a “common law” or “defacto” perception of what it is. </li></ul><ul><li>Perceptions of what SOA is vastly disparate. </li></ul>
    5. 5. SOA Reference Model... <ul><li>Is not architecture for a single implementation. </li></ul><ul><li>Is a model for developing a range of Service Oriented Architectures and analysis/comparison thereof. </li></ul><ul><li>Is a framework for understanding significant relationships among the entities in a SOA environment. </li></ul><ul><ul><li>DISCUSSION POINT: should the word “elements” be used in place of “entities” above? </li></ul></ul><ul><li>Is based on a small number of unifying concepts of all SOA’s. </li></ul><ul><li>A Reference Model is the best mechanism to define SOA. </li></ul>
    6. 6. To develop a Reference Model for SOA <ul><li>Ask questions: </li></ul><ul><ul><li>What elements are common in all implementations of SOA? ( be careful – think about this ) </li></ul></ul><ul><ul><li>What abstract concepts do those elements represent? </li></ul></ul><ul><ul><li>What relationships exist amongst those concepts? </li></ul></ul><ul><ul><li>How do we represent those concepts without referencing concrete implementations. </li></ul></ul><ul><ul><li>How does this relate to infrastructure concepts? </li></ul></ul>
    7. 7. Draft: Candidate SOA Reference Model DISCUSSION POINT: Details of how to interpret “Concept Maps” are included in the position paper submitted by Mackenzie, Nickull.
    8. 8. Base Components and Concepts of SOA <ul><li>Service: A service is a contractually defined behavior that can be implemented and provided by a component for use by any component solely based on the contract. </li></ul><ul><li>Service Description: Technical parameters, constraints, policies that come together to define terms of invocation. </li></ul><ul><ul><li>DISCUSSION POINT: Is the contract part of the service description or referenced from it (if explicit)? The contract is shown linked to the service since it may be implied only and not physically able to be linked via a Service Description.. </li></ul></ul><ul><li>Advertising: Makes all potential or intended consumers of a service on a fabric aware that the service exists. This MAY involve advertising the Service Description. </li></ul>
    9. 9. Base Components and Concepts of SOA <ul><li>Data Model: The specification and constraints imposed on instance data. </li></ul><ul><ul><li>QUESTION: Are semantics part of the data model? If not, how to others know what data model authors really mean? </li></ul></ul><ul><li>Contract: The implicit or explicit bi-lateral or multi-lateral agreement between the owners or agents of a service and those who use the service. </li></ul><ul><ul><li>QUESTION: Is “no contract” still ipso facto a contract? Is “zero” a number or “null” a value? </li></ul></ul>
    10. 10. Agenda <ul><li>What is SOA; what is a reference model for SOA </li></ul><ul><li>Why is a reference model needed </li></ul><ul><li>The OASIS SOA RM TC </li></ul>
    11. 11. Existing situation WSDL XML & Schema SOAP Base Standards WS-RM WS Addressing Reg/Rep UDDI WS-Security WS-Trust WS-* Requirements Question: How do I map my Requirements to concrete architecture?
    12. 12. Developing SO Architecture <ul><li>Probably not logical to try and develop a “one size, fits all” architecture for SOA or WS. </li></ul><ul><li>Not rational to develop multiple architectures in standards bodies for every set of requirements. </li></ul><ul><li>Best solution: develop an SOA reference Model. </li></ul><ul><ul><li>Used by architects to guide service oriented architecture development. </li></ul></ul><ul><ul><li>Model for a way of thinking when developing solutions. </li></ul></ul><ul><ul><li>Re-useable by multiple architects writing SOA for multiple domains. </li></ul></ul><ul><ul><li>Helps architects slot existing standards into their architectures. </li></ul></ul>
    13. 13. SOA RM used for range of architectures WSDL XML & Schema SOAP Base Standards WS-RM WS Addressing Reg/Rep UDDI WS-Security WS-Trust WS-* Requirements Guides developments of SOA-RM Specific Architectures Uses Input for QUESTION: Does this adequately explain the need for a reference model? Does this also clarify why a reference model is better than developing multiple Architectures?
    14. 14. Agenda <ul><li>What is SOA; what is a reference model for SOA </li></ul><ul><li>Why is a reference model needed </li></ul><ul><li>The OASIS SOA RM TC </li></ul>
    15. 15. OASIS SOA Reference Model TC <ul><li>Chartered February 2005 </li></ul><ul><li>Problem to be solved : </li></ul><ul><ul><li>&quot;Service Oriented Architecture&quot; (SOA) as a term is being used in an increasing number of contexts and specific technology implementations, sometimes with differing or conflicting understandings of implicit terminology and components. </li></ul></ul><ul><ul><li>The proposal to establish a Reference Model is intended to encourage the continued growth of specific and different SOA implementations whilst preserving a common layer that can be shared and understood between those or future implementations. </li></ul></ul>
    16. 16. OASIS SOA Reference Model TC <ul><li>Purpose : </li></ul><ul><ul><li>The SOA-RM TC will deliver a Service Oriented Architecture Reference Model (SOA-RM). </li></ul></ul><ul><ul><li>The TC may also create sub-committees, promotional material, liaisons or other promulgation of the TC's work, in order to promote the use of the SOA Reference Model. </li></ul></ul><ul><ul><li>May help vertical industries develop SOA for their requirements. </li></ul></ul>
    17. 17. Charter Definition <ul><li>Reference Model: </li></ul><ul><li>A reference model is an abstract framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. A reference model is based on a small number of unifying concepts. A reference model is not directly tied to any standards, technologies or other concrete implementation details, but it does seek to provide a common semantics that can be used unambiguously across and between different implementations. </li></ul>
    18. 18. References <ul><li>OASIS SOA RM TC - </li></ul>