<?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:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_qVRYkPS3EdmIX5Pw7v8pRw" name="developing_service-oriented_solutions,3.300952218919066E-305" guid="_qVRYkPS3EdmIX5Pw7v8pRw" changeDate="2006-10-15T19:00:03.128-0700" version="7.1.0">
  <mainDescription>&lt;h3 align=&quot;left&quot;>&#xD;
    RUP and Service Oriented Modeling and Architecture&#xD;
&lt;/h3>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    The SOMA method was developed as an engagement model within IBM's Global Business Services group, and while public&#xD;
    papers and descriptions were available it was primarily a method used by consultants in the field and not available to&#xD;
    IBM customers. On the other hand the RUP is a commercial product offering from IBM which customers use to develop their&#xD;
    own software development processes. This integrated method offering, RUP/SOMA has been developed to bring the unique&#xD;
    aspects of SOMA to the RUP commercial method and make these available to commercial customers.&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    The framework for RUP/SOMA is described by the picture below which demonstrates the key phases of the method, including&#xD;
    the influences driving each phase and the artifacts produced. Note that the key artifact manipulated by the method is&#xD;
    the Service Model (described below).&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &amp;nbsp;&lt;img height=&quot;289&quot; alt=&quot;Method Overview&quot; src=&quot;./resources/method_overview.png&quot; width=&quot;506&quot; />&#xD;
&lt;/p>&#xD;
&lt;h4 align=&quot;left&quot;>&#xD;
    Service Identification&#xD;
&lt;/h4>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    Service Identification is primarily an Elaboration time set of activities, focused on the identification of candidate&#xD;
    services from the set of assets from both business and IT. The workflow for Service Identification is as follows:&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;52&quot; alt=&quot;&quot; src=&quot;./resources/identification_workflow.png&quot; width=&quot;426&quot; />&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    The tasks identified within this set of activities are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../extend.bus_model/tasks/functional_area_analysis_FA3C6512.html&quot;&#xD;
            guid=&quot;_DdZsUEyBEdugTvBtC2ApIg&quot;>Task: Functional Area Analysis&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../extend.bus_model/tasks/refine_business_use_case_13E3A77B.html&quot;&#xD;
            guid=&quot;_NQD5oDOdEduwK5jZAAYgbw&quot;>Task: Refine a Business Use-Case&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/soa_service_identification_bp_D5A863FB.html&quot;&#xD;
            guid=&quot;_am-VYCwTEduKcvYAyaKSaA&quot;>Task: Business Process Analysis&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/soa_service_identification_uc_F1F4D8B7.html&quot;&#xD;
            guid=&quot;_GkKR4CwUEduKcvYAyaKSaA&quot;>Task: Business Use Case Analysis (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../extend.bus_model/tasks/identify_business_goals_BDD1599E.html&quot;&#xD;
            guid=&quot;{BE3CF670-F2E7-4B03-90A0-F01B59777597}&quot;>Task: Identify Business Goals and KPIs&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_goal_service_assignment_46A9906C.html&quot;&#xD;
            guid=&quot;_I7P6gCwTEduKcvYAyaKSaA&quot;>Task: Identify and Associate Services to Goals&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/soa_service_identification_legacy_CF2A5A41.html&quot;&#xD;
            guid=&quot;_xQpQ8CwTEduKcvYAyaKSaA&quot;>Task: Existing Asset Analysis&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/soa_service_identification_data_1AFDAC0A.html&quot;&#xD;
            guid=&quot;_mJtYwCwTEduKcvYAyaKSaA&quot;>Task: Data Model Analysis&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/soa_service_identification_rules_DAB02396.html&quot;&#xD;
            guid=&quot;_6zx0ECwTEduKcvYAyaKSaA&quot;>Task: Business Rule Analysis&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_construct_arch_proof_F12BF33D.html&quot;&#xD;
            guid=&quot;_XHRjoEw5EduGSMz-5zscXg&quot;>Task: Construct Architectural Proof-of-Concept (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4 align=&quot;left&quot;>&#xD;
    Service Specification&#xD;
&lt;/h4>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    Service Specification is primarily an Elaboration time set of activities, focused on the selection of candidate&#xD;
    services that shall be developed into full services. These services are then allocated to subsystems also identified&#xD;
    above and then decomposed into sets of componenents for implementation. The workflow for Service Specification is as&#xD;
    follows:&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;50&quot; alt=&quot;&quot; src=&quot;./resources/specification_workflow.png&quot; width=&quot;537&quot; />&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    The tasks identified within this set of activities are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_service_qualification_E0D920A6.html&quot;&#xD;
            guid=&quot;_mHhK8CwUEduKcvYAyaKSaA&quot;>Task: Apply Services Litmus Tests&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_service_specification_AB6BA763.html&quot;&#xD;
            guid=&quot;{9EB2B302-79F6-4DF8-AEB7-98E6AC1756DD}&quot;>Task: Service Specification&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_service_message_design_D1BA096D.html&quot;&#xD;
            guid=&quot;_ObqZoCwUEduKcvYAyaKSaA&quot;>Task: Message Design&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot;&#xD;
            href=&quot;./../../../soa.rup_soma/tasks/sec_identify_security_patterns_1953748F.html&quot;&#xD;
            guid=&quot;_m8lcIDIyEduePY7oPsXsLA&quot;>Task: Identify Security Patterns&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_subsystem_design_B9BB36BD.html&quot;&#xD;
            guid=&quot;{FACE1697-1CB6-4F57-8B39-ED507BE7006F}&quot;>Task: Subsystem Design (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_component_specification_6BB8DC55.html&quot;&#xD;
            guid=&quot;_OjBb4Ew_EduGSMz-5zscXg&quot;>Task: Component Specification (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4 align=&quot;left&quot;>&#xD;
    Service Realization&#xD;
&lt;/h4>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    Service Realization is primarily a Construction time set of activities, focused on the completion of component design&#xD;
    ready for component implementation. The workflow for Service Specification is as follows:&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;50&quot; alt=&quot;&quot; src=&quot;./resources/realization_workflow.png&quot; width=&quot;115&quot; />&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;left&quot;>&#xD;
    The tasks identified within this set of activities are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_service_realization_66984C2B.html&quot;&#xD;
            guid=&quot;_V6uMMCwUEduKcvYAyaKSaA&quot;>Task: Document Service Realization Decisions&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_component_specification_6BB8DC55.html&quot;&#xD;
            guid=&quot;_OjBb4Ew_EduGSMz-5zscXg&quot;>Task: Component Specification (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div align=&quot;left&quot;>&#xD;
            &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/tasks/soa_construct_arch_proof_F12BF33D.html&quot;&#xD;
            guid=&quot;_XHRjoEw5EduGSMz-5zscXg&quot;>Task: Construct Architectural Proof-of-Concept (SOA)&lt;/a>&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4 align=&quot;left&quot;>&#xD;
    The Service Model&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    In SOMA the Service Model is described using the picture below; it is a single, document based,&amp;nbsp;work product that&#xD;
    encompasses the different technical and lifecycle views of the services identified and specified during a project. The&#xD;
    different sections of the service model are listed in more detail in the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../soa.rup_soma/workproducts/soa_service_model_623494B9.html&quot;&#xD;
    guid=&quot;{E24679B7-19F1-483B-A1F1-578839C43888}&quot;>Artifact: Service Model&lt;/a>&amp;nbsp;in RUP/SOMA.&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;img height=&quot;385&quot; alt=&quot;&quot; src=&quot;./resources/soma_service_model.png&quot; width=&quot;458&quot; />&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The RUP &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../soa.rup_soma/workproducts/soa_service_model_623494B9.html&quot;&#xD;
    guid=&quot;{E24679B7-19F1-483B-A1F1-578839C43888}&quot;>Artifact: Service Model&lt;/a>&amp;nbsp;is described in both a document form and&#xD;
    a UML form (&lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../soa.rup_soma/guidances/templates/soa_service_model_doc_950782A6.html&quot;&#xD;
    guid=&quot;_ZYHekE3eEduBbftZUgDxnQ&quot;>Template: Service Model in Word&lt;/a>&amp;nbsp;and &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../soa.rup_soma/guidances/templates/soa_service_model_uml_73836D53.html&quot;&#xD;
    guid=&quot;_-bpYcE3aEdupj44ytPg0iA&quot;>Template: Service Model in UML&lt;/a>) though it is more likely that a project will use&#xD;
    elements of both of these forms in presenting the results of their work.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
