<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-kBKKIXeRmCXqMr2WoLy_oQ" name="new_guideline,_vR9pQJgzEd6l6vBsNJSPDA" guid="-kBKKIXeRmCXqMr2WoLy_oQ" changeDate="2009-09-04T13:18:31.812-0700" version="7.5.0">
  <mainDescription>&lt;p>&#xD;
    &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../core.tech.common.extend_supp_soa-ibm/guidances/examples/services_architecture_soaml_BF38A4B3.html&quot;&#xD;
    guid=&quot;_mOf5sFbBEd6MCpkuB85p5g&quot;>Example: ServicesArchitecture (SoaML)&lt;/a>,&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../core.tech.common.extend_supp_soa-ibm/guidances/concepts/service_composition_and_choreography_67057C86.html&quot;&#xD;
     guid=&quot;_yAh28IA6Ed6H1oy6lZPykw&quot;>Concept: Service Composition and Choreography&lt;/a>, and &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../core.tech.common.extend_supp_soa-ibm/guidances/examples/soaml_design_model_sample_83612289.html&quot;&#xD;
    guid=&quot;_AfQisHNIEd6va-EJWoOsvg&quot;>Example: Sample SoaML Design Model&lt;/a>&amp;nbsp;illustrate the&amp;nbsp;elements of&#xD;
    a&amp;nbsp;ServicesArchitecture, which is a stereotyped UML collaboration:&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Collaboration parts, which interact to solve a business problem. In the most general case, the parts will have only&#xD;
        role names to illustrate the roles that are involved in the collaboration. In a concrete ServicesArchitecture --&#xD;
        one that shows which specific Participants in the solution space are being used to address the problem --&amp;nbsp;the&#xD;
        roles are typed with&amp;nbsp;Participants.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
        href=&quot;./../../../core.tech.common.extend_supp_soa-ibm/guidances/concepts/collaboration_use_soaml_CD661F65.html&quot;&#xD;
        guid=&quot;_iLYT8GajEd65K8S2sWS35w&quot;>CollaborationUses&lt;/a>, which are used to bind the parts to the roles that they play&#xD;
        in the &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
        href=&quot;./../../../core.tech.common.extend_supp_soa-ibm/guidances/concepts/service_contract_soaml_E57B30D4.html&quot;&#xD;
        guid=&quot;_IhtgsFbBEd6MCpkuB85p5g&quot;>ServiceContracts&lt;/a> or in the&amp;nbsp;ServiceInterface protocols that govern the&#xD;
        interactions of the parts.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        An ownedBehavior (such as an Activity or an Interaction), which is used to explicitly illustrate how the parts&#xD;
        interact to solve the problem.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        A structure diagram, which is used to connect the parts to the roles they play in the Collaboration Uses.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Build each ServicesArchitecture by following these steps:&#xD;
&lt;/p>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        Identify the services that need to be involved in the solution. This information can be gleaned from the roles that&#xD;
        were involved in the&amp;nbsp;original &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
        href=&quot;./../../../core.tech.common.extend-ibm/guidances/termdefinitions/service_collaboration_35276470.html&quot;&#xD;
        guid=&quot;_V4z3YJgtEd6l6vBsNJSPDA&quot;>Service Collaborations&lt;/a>. The required services will be the ones that were derived&#xD;
        previously&amp;nbsp;from the Service Collaboration roles.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify the Participants that provide the necessary services. Add them to the ServicesArchitecture as parts.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify the ServiceContracts or the ServiceInterface protocols that govern the interactions of the Participants&#xD;
        that are involved in the ServicesArchitecture.&amp;nbsp; Create a CollaborationUse for each such collaboration, and add&#xD;
        it to the ServicesArchitecture.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the ServicesArchitecture's structure diagram, bind all of the parts to the appropriate roles of the&#xD;
        CollaborationUses.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Check your work. Leverage the ServiceContract and protocol behaviors to&amp;nbsp;create a behavior for the&#xD;
        ServicesArchitecture that shows how all of the involved services interact to address the problem. The resulting&#xD;
        behavior is expected to be a concrete rendering of the role-based behavior that was created for the original&#xD;
        Service Collaboration.&#xD;
    &lt;/li>&#xD;
&lt;/ol>&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
