<?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="-isqsIiw9-4dR3ProL-I-vg" name="new_guideline,_fx7TMD3REd-realK_We5vA" guid="-isqsIiw9-4dR3ProL-I-vg" changeDate="2011-10-13T15:47:19.687-0700" version="7.5.0">
  <mainDescription>&lt;h3>&#xD;
    Defining Method Content Elements&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Method content elements are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
        guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>s&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
        guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>s&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
        guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s (&lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html&quot;&#xD;
        guid=&quot;_x7cUM9nmEdmO6L4XMImrsA&quot;>artifact&lt;/a>s, &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html&quot;&#xD;
        guid=&quot;_LNAAcB_iEdqAHrsQ7-jSbw&quot;>outcome&lt;/a>s and &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html&quot;&#xD;
        guid=&quot;_yFbWoNnmEdmO6L4XMImrsA&quot;>deliverable&lt;/a>s)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html:.:.:&quot;&#xD;
         class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html&quot;&#xD;
        guid=&quot;_83ttAB_NEdq6CKKKq4D7YA&quot;>guidance&lt;/a>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Defining a method content element involves creating the plug-in that will contain the element (if&amp;nbsp;it does not&#xD;
    already exist), naming the element and briefly describing it. Any issues naming an element and briefly describing it&#xD;
    may indicate that the element is not a&amp;nbsp;good element after all.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    General Guidelines&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    The following are some general guidelines when defining method content elements:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Reduce the overall number of method content elements&lt;/strong> (e.g., the number of work products, tasks,&#xD;
        roles).&amp;nbsp;Combine similar elements.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp; &amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Document process-dependent information separate from the method content element&#xD;
        definition&lt;/strong>.&amp;nbsp;Method content&amp;nbsp;elements should&amp;nbsp;be process independent. Any minor&#xD;
        differences/tweaks to the elements based on where they occur in&amp;nbsp;a particular process or lifecycle&amp;nbsp;can be&#xD;
        captured in the processes in which the element appears (more on this below). This maximizes the reuse of the method&#xD;
        content across processes. For more information on defining processes, see &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html:.:.:&quot;&#xD;
         class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_customizing_processes_55E6CE53.html&quot;&#xD;
        guid=&quot;_E9J1kD9EEd-Xgadv74rzHA&quot;>Guideline: Defining and Customizing Processes&lt;/a>.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Start with the work products&lt;/strong>.&amp;nbsp;When identifying method content elements, its always a good&#xD;
        idea to start with identifying the work products. Work products are the manifestation of the solution to the&#xD;
        problem the method addresses. They must be clearly understood at the very beginning of a method authoring project.&#xD;
        Identifying the work products may appear to consume considerable time but unless they are clearly defined, the&#xD;
        project will fail. For more information, see the &quot;Defining work products&quot; section below.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Use guidance to supplement&lt;/strong> the basics and capture details.&amp;nbsp;Guidance elements can be used to&#xD;
        supply various kinds of information and assets to method elements so that practitioners are better equipped to&#xD;
        execute the work.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Capture the source of the information for the element&lt;/strong>.&amp;nbsp;This information is important if you&#xD;
        ever need to provide source information for the element for documenting ownership rights.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Maintain accurate change histories, as well as making sure your trademarks and copyrights are&#xD;
        accurate&lt;/strong>.&lt;br />&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Reuse existing content&lt;/strong>. When defining method content elements, it is always a good idea to reuse&#xD;
        existing content, both content inside the method being developed, as well as content available externally. This is&#xD;
        especially important in those cases where you are customizing or building on an existing method. Many elements&#xD;
        may&amp;nbsp;already be defined. It is usually better to start with an existing element than starting from scratch.&#xD;
        When reusing an existing element, make sure that the content of the element is what you expect. For more&#xD;
        information on how to leverage existing content and maximize reuse between method content elements, see&#xD;
        below.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Use content packages to organize the defined method content elements&lt;/strong>.&amp;nbsp;When defining method&#xD;
        content elements, you may find that you want to introduce some packages in order to better organize the&#xD;
        elements.&amp;nbsp;For more information, see &lt;a&#xD;
        id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html:.:.:&quot;&#xD;
         class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/creating_plugins_practices_configurations_4C84B4C2.html&quot;&#xD;
         guid=&quot;_EXvLwD3NEd-realK_We5vA&quot;>Guideline: Creating Plug-ins, Practices and Configurations&lt;/a>.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The following sections provide method-element-specific guidelines.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Defining work products&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    There are three types of &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
    guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s that can be defined:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Artifact – provides a description and definition for tangible, non-trivial work product&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Deliverable – a collection of work products, usually artifacts&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Outcome – an intangible work product that may be a result or state.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Following are the guidelines for creating each of these work product types.&lt;br />&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Defining artifacts&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html:.:.:&quot;&#xD;
     class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html&quot;&#xD;
    guid=&quot;_x7cUM9nmEdmO6L4XMImrsA&quot;>Artifacts&lt;/a> are tangible, well-defined &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
    guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s consumed, produced, or modified by &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
    guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>s.&amp;nbsp;Artifacts may be composed of other artifacts.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Artifacts are the responsibility of a single &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
    guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>, making responsibility easy to identify and understand, and promoting the idea&#xD;
    that every piece of information produced in the method requires the appropriate set of skills. Even though one role&#xD;
    might &quot;own&quot; a specific type of artifact, other roles can still use the artifacts, and perhaps even update them, if the&#xD;
    role has been given permission to do so.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Defining deliverables&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    A&amp;nbsp;&lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html&quot;&#xD;
    guid=&quot;_yFbWoNnmEdmO6L4XMImrsA&quot;>deliverable&lt;/a>&amp;nbsp;is a &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
    guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a> that provides a description and definition for packaging other work&#xD;
    products, and may be delivered to an internal or external party.&amp;nbsp;Deliverables are used to represent an output from&#xD;
    a process that has value to a client, customer or other stakeholder.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Defining outcomes&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    An &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html&quot;&#xD;
    guid=&quot;_LNAAcB_iEdqAHrsQ7-jSbw&quot;>outcome&lt;/a>&amp;nbsp;describes an intangible&amp;nbsp;&lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
    guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>&amp;nbsp;that represents a result or state, such as an installed server or&#xD;
    optimized network. Outcomes may also be used to describe work products that are not formally defined.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;h4 style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
    Defining roles&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    A &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
    guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>&amp;nbsp;defines a set of related skills and competencies. Roles are used by &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
    guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>s to specify who performs them.&amp;nbsp; Roles&amp;nbsp;may be given responsibilities&#xD;
    for specific work products.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The following are some criteria that affect what roles you define in your method:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Organization (what are the roles in the organization that the method supports)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Type of project (what roles participate in the projects that the method supports)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Style of governance (e.g., different RACI matrices)&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The smaller the number of roles, the better. Define roles to represent distinct skill sets, things a person may choose&#xD;
    to do for a living, as opposed to something that someone may do on the project at any particular point in time using&#xD;
    the skills they have with some additional guidance. For example, a person may be an analyst or a designer, but may also&#xD;
    serve as a reviewer in some circumstances, or may be responsible for implementing a change request. Thus, &quot;analyst&quot; and&#xD;
    &quot;designer&quot; are good examples of roles, where as &quot;reviewer&quot; and &quot;change request implementer&quot; are not as they perform&#xD;
    things that anyone can do using their basic skill set (plus some additional guidance like guidelines and checklists).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The following are some criteria that affect how you assign roles to work products and tasks in your method:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Work allocation in the organization and/or on the project that the method supports (who does what)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Style of governance (make very precise responsibility assignments; e.g., different RACI matrices -- RACI, RACI-VS,&#xD;
        VARISC, RASCI)&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    &lt;br />&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Defining tasks&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    A &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
    guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>&amp;nbsp;is a description of a unit of work.&amp;nbsp;The performing role&#xD;
    typically&amp;nbsp;transforms the input &lt;a&#xD;
    id=&quot;A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html:.:.:&quot;&#xD;
     class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
    guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s into output work products to achieve a well-defined goal.&amp;nbsp;This&#xD;
    description is complete and independent of when in a process lifecycle the work will actually be performed.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Describe tasks in a consistent way, both in terms of naming and in terms of scope/granularity. Try to standardize on a&#xD;
    key set of verbs and the way those verbs are used in the task names.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Define tasks so that they are independent of any specific process/lifecycle.&amp;nbsp;Tasks provide step-by-step&#xD;
    explanations, describing how specific development goals are achieved independent of the placement of these steps within&#xD;
    a specific process (e.g., development lifecycle). Processes take these method elements and relate them into&#xD;
    semi-ordered sequences that are customized to specific types of projects. For example, a software development project&#xD;
    that develops an application from scratch performs tasks such as &quot;Develop Vision&quot; or &quot;Use Case Design&quot; similar to a&#xD;
    project that extends an existing software system. However, the two projects will perform the tasks at different points&#xD;
    in time with a different emphasis, i.e., they perform the steps of these tasks at different points of time and perhaps&#xD;
    apply individual variations and additions.&#xD;
&lt;/p>&#xD;
&lt;p style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
    When identifying what tasks are needed, it is important to decide on the granularity of the task.&amp;nbsp;In doing so, the&#xD;
    following should be taken into consideration:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>A task generally has only one primary output work product&lt;/strong>.&amp;nbsp;However, there are instances where&#xD;
        more than one work product is worked on simultaneously, so it is possible that you will want to define some tasks&#xD;
        that do have more than one output&amp;nbsp;work product.&lt;br />&#xD;
        &amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>It is recommended that you define a separate task for each state change a work product product goes&#xD;
        through.&lt;/strong>&amp;nbsp;Since different states need different checklists, have different completion criteria, and&#xD;
        have different execution guidance, it makes sense to have different tasks.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>When the inputs to a task are&amp;nbsp;different&lt;/strong>, you probably have two different tasks.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>When the task is assigned to different roles&lt;/strong>, you probably want two different tasks.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    You identify a task when there is a need to transform input work products into outputs through a series of steps&#xD;
    performed by one or more roles independent of a breakdown structure.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    When defining a task, you should also define it's relationships with other method content elements.&amp;nbsp;A&#xD;
    task&amp;nbsp;can have the following relationships with other method content elements:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Roles:&lt;/strong>&amp;nbsp; Two types of roles can be specified:&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                &lt;div>&#xD;
                    &lt;strong>Primary Performer:&lt;/strong>&amp;nbsp; Each task should have a primary performer.&amp;nbsp;This is the&#xD;
                    role this is responsible for ensuring that the task is completed.&amp;nbsp;&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div>&#xD;
                    &lt;strong>Additional Performers:&lt;/strong>&amp;nbsp; Additional performers help execute the task.&amp;nbsp;They&#xD;
                    provide information and expertise.&lt;br />&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;div>&#xD;
            &lt;strong>Work Products:&lt;/strong>&amp;nbsp; This is where inputs and outputs to the task are&#xD;
            identified.&amp;nbsp;Specify:&#xD;
        &lt;/div>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                &lt;div>&#xD;
                    &lt;strong>Mandatory Inputs:&lt;/strong>&amp;nbsp; Mandatory inputs are the work products the task depends upon&#xD;
                    for its successful execution.&amp;nbsp;These are the inputs that the task cannot do without.&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div>&#xD;
                    &lt;strong>Optional Inputs:&lt;/strong>&amp;nbsp;&amp;nbsp;Optional inputs&amp;nbsp;are the work products that provide&#xD;
                    additional information or context for the task when it is being executed.&amp;nbsp;However, the task does&#xD;
                    not depend on them for successful execution.&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div>&#xD;
                    &lt;strong>Outputs:&lt;/strong>&amp;nbsp;&amp;nbsp;The output work products are those that are produced directly by&#xD;
                    this task.&amp;nbsp;Most tasks will have only one output work product.&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Defining guidance&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Guidance provides additional details to enhance method content.&amp;nbsp;In fact, methods are more flexible if the content&#xD;
    provided in specific method elements is kept as general as possible, with more detail provided as guidance.&amp;nbsp;The&#xD;
    method can be easily customized by simply adding or removing guidance. This section provides recommendations on how to&#xD;
    define guidance and how to associate the guidance with other method elements.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are many different types of guidance, all designed for specific purposes.&amp;nbsp;The guidance types are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Checklist&lt;/strong> – identifies a series of items that need to be completed or verified. Checklists are&#xD;
        often used in reviews such as walkthroughs or inspections. Checklists may also be a series of questions or a script&#xD;
        that practitioners may use to lead a discussion with the client's personnel. This might take the form of a&#xD;
        questionnaire or interview outline that focuses on the information needed for the work product or deliverable. In&#xD;
        UMA, a content element has at most one checklist. Checklists are useful in a number of contexts: they help in&#xD;
        deciding what to do, they help doing it, they help assess the quality of the work, and they help understand how a&#xD;
        particular work product relates to the rest of the process.&lt;br />&#xD;
        It is recommended that checklists only be associated with work products and not tasks.&amp;nbsp;If a checklist is&#xD;
        needed for a task, then it can be accessed via the work products associated with the task.&lt;br />&#xD;
        In general, checklists do not require a brief description.&amp;nbsp;However, if there are multiple checklists for a&#xD;
        method element, a brief description is helpful to distinguish between them.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Concept&lt;/strong> – outlines key ideas, basic principles and motivations underlying a topic central to the&#xD;
        method. Concepts normally address more general topics than guidelines and may span several work products, tasks,&#xD;
        activities, or disciplines. Examples of concepts might be In the context of risk management, performance testing,&#xD;
        implementation planning.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Example&lt;/strong> – a sample instance of a partially or fully formed work product or deliverable. The&#xD;
        instance may contain live client data (with the client's express permission to use it) or it may contain fabricated&#xD;
        data that is representative of the information required for the engagement. However, this example is necessarily&#xD;
        generic and is only a guide to what might be required in an actual work product or deliverable for a specific&#xD;
        engagement.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Guideline&lt;/strong> – provides additional details, &quot;how to&quot; information, alternatives, recommendations, or&#xD;
        rules about the use of a content element. For example, a work product typically has guidelines associated with it&#xD;
        that provides information on how to develop, evaluate, and use it. Guidelines can provide the context in which a&#xD;
        work product or other content element exists within a method. A guideline helps practitioners understand how a&#xD;
        particular content element is used and how it relates to the rest of the process in which it exists. This includes&#xD;
        formal technique papers for developing work products and deliverables.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Estimation Considerations&lt;/strong> – guidance on how to estimate the use in a project of the element with&#xD;
        which it is associated. The guidance may be textual, a spreadsheet, tool, or take some other form.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Practice&lt;/strong> – a proven way or strategy of doing work to achieve a goal that has a positive impact on&#xD;
        work product or process quality. Practices are defined orthogonal to methods and processes. They could summarize&#xD;
        aspects that impact many different parts of a method or specific processes. Examples for practices would be&#xD;
        &quot;Managing Risks&quot;, &quot;Continuously Verifying Quality&quot;, &quot;Architecture-centric and Component-based Development&quot;, and so&#xD;
        on.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Report&lt;/strong> – a predefined template of a result that is generated on the basis of one or more work&#xD;
        products as an output from some form of tool. A report is not an artifact in itself. It is, in most cases, a&#xD;
        transitory product of a process or monitoring, and a vehicle to communicate certain aspects of the evolving system;&#xD;
        it is a snapshot description of artifacts that are not documents themselves.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Reusable Asset&lt;/strong> – a type of guidance that references assets that lie outside the method. These&#xD;
        assets may be too large or volatile to be embedded. These assets may also be third party products or services for&#xD;
        which usage permission has been granted by the owner.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Roadmap&lt;/strong> – represents important documentation for the activity or process it is related to. Often a&#xD;
        complex activity such as a process can be much more easily understood by providing a walkthrough with a linear&#xD;
        thread of a typical instantiation of this activity. In addition to making the process practitioner understand how&#xD;
        work in the process is being performed, a roadmap provides additional information about how activities and tasks&#xD;
        relate to each other over time. Road maps are also used to show how specific aspects are distributed over a whole&#xD;
        process providing a kind of filter on the process for this information.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp; &amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Supporting Material&lt;/strong> – this is a catch-all for assets that do not fit in another type.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Template&lt;/strong> – a version of a work product or deliverable instance that does not contain data so that&#xD;
        the practitioner may use it to &quot;fill in the blanks&quot;. This is usually a form or set of fields that define the data&#xD;
        to be collected and may assist in analyzing the data to produce the information for the completed work product or&#xD;
        deliverable. Taken together the example and the template form a powerful pair for the practitioner. In the first,&#xD;
        the practitioner sees a completes or partially completed work product while the second offers a convenient means of&#xD;
        producing the work product as rapidly and as accurately as possible.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Term Definition&lt;/strong> – a definition of a word or phrase that is not in the glossary and that&#xD;
        practitioner need to understand for the method plug-in.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Tool Mentor&lt;/strong> – a description of how to achieve certain goals with a specific tool. Tool mentors&#xD;
        link tasks with tools such as IBM&amp;reg; Rational&amp;reg; Method Composer. They almost completely encapsulate the dependencies&#xD;
        of the content on the tool set, keeping the tasks free from tool details.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>White Paper&lt;/strong> – an externally published paper that can be read and understood in isolation of other&#xD;
        content elements and guidance&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Guidance should be written with a specific scope in mind.&amp;nbsp; For example:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Guidance can be more &lt;em>&lt;strong>general&lt;/strong>&lt;/em>, written with regards to a set of elements (e.g., workshops,&#xD;
        collaboration, lifecycle families, etc.)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Guidance can be &lt;strong>&lt;em>method-element specific&lt;/em>&lt;/strong> (e.g., written regarding a specific work product,&#xD;
        task, role, process) , or&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The name of a guidance element should reflect that scope. Specifically, method element-specific guidance should include&#xD;
    the method element name in its name.&amp;nbsp;For example,&amp;nbsp;Guideline: Detailing a Use Case, Template: Use-Case&#xD;
    Template.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Guidance may be attached to any method element and guidance should be attached to method elements, as needed. However,&#xD;
    decreasing the number of relationships defined between elements in the method helps to reduce the overall perceived&#xD;
    complexity of the method.&amp;nbsp;In general, guidance should be associated with the smallest number of elements possible.&#xD;
    Having &quot;everything associated with everything&quot; is a bad idea as it directly affects the usage of the published web&#xD;
    site.&lt;br />&#xD;
    For example, avoid associating the same guidance with work products and tasks that produce the work products as this&#xD;
    creates unnecessary dependencies since the same content will be linked in via one of the other relationships&#xD;
    anyway.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Guidance should be associated with the element that reflects its scope (i.e., the element where the end-user would be&#xD;
    expected to look for it).&amp;nbsp; Method element-specific guidance should be associated with the method element it&#xD;
    describes:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If the guidance is about notation or representation of a work product (e.g., template, example, checklist) then it&#xD;
        should be associated with the work product&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        If the guidance describes a specific technique about how to produce the work product then it should be associated&#xD;
        with a task that produces the work product&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        General guidance should be associated with &quot;general&quot; elements (e.g., slots, standard categories, reference&#xD;
        workflows, etc.) or possibly just included in custom categories (aka navigation views)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Roles are not a common place for associating guidance, unless that guidance is specific to the role (and not to a&#xD;
        task the role performs or a work product the role is responsible for)&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Most guidance should be associated with at least one element. Of course, there are exceptions:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Guidance that is about the method, as opposed to being part of the method (e.g.,&amp;nbsp; Welcome pages, About pages,&#xD;
        What's new pages, etc.).&amp;nbsp;Such guidance is usually only referred to from navigation views.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        General guidance (e.g., concepts, white papers) sometimes need to be associated with &quot;general&quot;&#xD;
        elements.&amp;nbsp;&lt;br />&#xD;
        Some possible associations for general concepts are associating to them from standard categories, custom&#xD;
        categories/navigation views, etc.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    When defining guidance elements, you must constantly weigh reuse concerns versus complexity:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If you define fine-grained guidance elements, then you can assign the guidance elements to specific method&#xD;
        elements, which provides just the guidance you need, but&amp;nbsp;then you have many guidance elements, which can be&#xD;
        construed as being more complex).&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        If you define course-grained guidance elements, then have a smaller number of guidance elements, but then the same&#xD;
        guidance elements is attached to multiple elements and you have to find what you are looking for by scrolling&#xD;
        through the course-grained guidance element.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Make the best choice based on your circumstances and let end-user feedback be your guide.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Roles in the UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    The Unified Method Framework (UMF)&amp;nbsp;defines some constraints with regards to the definition and use of &lt;a&#xD;
    class=&quot;elementLink&quot; href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
    guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>s and &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_set_396DC9DB.html&quot;&#xD;
    guid=&quot;_Fs8HAMaIEduMlb2cQZNTYw&quot;>role set&lt;/a>s.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The UMF implements a delayed role assignment&amp;nbsp;approach, which means that the assignment of roles to method content&#xD;
    elements is NOT done as part of the definition of the method content elements.&amp;nbsp; In addition, in the UMF, role&#xD;
    definitions are intended to be shared.&amp;nbsp; Thus, in the UMF, the roles and role sets&amp;nbsp;are defined separately from&#xD;
    the method content elements they can be assigned to (e.g., work products and tasks), as well as from the assignments&#xD;
    themselves.&amp;nbsp;Roles and role sets may be shared across practices or may be practice-specific and this decision&#xD;
    affects what plug-ins their definitions and assignments are placed.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Shared roles and role sets:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Shared roles and role sets are &lt;strong>&lt;em>defined&lt;/em>&lt;/strong> in a Role Definition Base plug-in.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Shared roles are assigned to shared role sets in a Role Definition Base plug-in.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Shared roles are &lt;strong>&lt;em>assigned&lt;/em>&lt;/strong> to &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
        guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>s and &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
        guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s in the Assign plug-in associated with the Base plug-in where the&#xD;
        element to be assigned to the role (work product or task) is defined.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Practice-specific roles and role sets:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Practice-specific roles and role sets are defined in the Practice Assign plug-in.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Practice-specific roles are assigned to practice-specific role sets in the Practice Assign plug-in.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Practice-specific roles are &lt;strong>&lt;em>assigned&lt;/em>&lt;/strong> to &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html&quot;&#xD;
        guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;>task&lt;/a>s and &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html&quot;&#xD;
        guid=&quot;_H4JXwB_SEdq6CKKKq4D7YA&quot;>work product&lt;/a>s in the Practice Assign plug-in.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The benefits to the UMF approach to roles are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Roles and role sets can be shared across practices (shared Role Definition plug-ins)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Alternate role assignments can be defined (provide alternate Assign plug-ins)&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Note: If you are developing a method where the role assignments can NEVER change, then late role assignment is overkill&#xD;
    and the role assignments can be done directly in Base plug-ins.&#xD;
&lt;/p>&lt;br />&#xD;
&lt;h3>&#xD;
    Scaling Method Elements in the UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    When there is a need to scale, you need to define a base plug-in (or plug-ins) that have a scope&amp;nbsp;generic enough to&#xD;
    be scaled. For example, we define an open source core plug-in (or plug-ins) that may have a scope that is broader than&#xD;
    OpenUp Basic in open source layer. OpenUp Basic could then be built on that open source core (as would the rest of the&#xD;
    IBM methods), possibly using only a subset of the elements in the core. That way, users can have access to the OpenUp&#xD;
    Basic content, as well as the broader open source core that is built to be scaled up.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Example of using packaging technique to scale&#xD;
&lt;/h4>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;h5>&#xD;
            Scaling by adding techniques&#xD;
        &lt;/h5>&#xD;
        &lt;p>&#xD;
            Sometimes we want to offer a specialized technique or alternative technique from which the&amp;nbsp;user can pick&#xD;
            and choose. You can either package the technique in a separate technique plug-in or package the technique in&#xD;
            its own content package.&#xD;
        &lt;/p>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Create a Technique Plug-in &#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        This method is nice because it captures all the work products, tasks, etc, across all disciplines&#xD;
                        in one place. &amp;nbsp;Selection of the technique is simply a matter of choosing the plug-in.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Alternative techniques can be offered using multiple plug-ins&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Document restrictions in the Plug-in description (available in the configuration editor) for which&#xD;
                        techniques can be used together and which cannot.&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Create a Content Package &#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        This method is useful for small, isolated techniques&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Note: avoid creating dependencies on content package selection (eg, must choose two or none).&amp;nbsp;&#xD;
                        If the user will need to select multiple content packages to properly choose the technique, it&#xD;
                        would be better to use a technique plug-in instead.&lt;br />&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;h5>&#xD;
            Scaling by adding resource plug-ins&#xD;
        &lt;/h5>&#xD;
        &lt;p>&#xD;
            Isolating resources, such as examples and templates, to their own plug-in allows users to select which set of&#xD;
            resources they want. For example: cmr.res.sw_dev.formal, cmr.res.sw_dev.informal.&#xD;
        &lt;/p>&#xD;
        &lt;p>&#xD;
            Don't worry about elaborate content packaging of templates: assume that errors in configurations caused by&#xD;
            templates not having a WP home because the package containing the WP was deselected.&#xD;
        &lt;/p>&#xD;
        &lt;p>&#xD;
            Note:&amp;nbsp; When you have more than one template for a particular work product:&#xD;
        &lt;/p>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                &lt;p>&#xD;
                    If the content of the templates is the same, just the format is different (eg, letter, A4, MS Word,&#xD;
                    HTML), then you can just add the additional template to the same template guidance element.&#xD;
                &lt;/p>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;p>&#xD;
                    If the content of the templates is different, then use another Template guidance element to attach the&#xD;
                    second template.&#xD;
                &lt;/p>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Common guidelines on scaling&#xD;
&lt;/h4>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Tasks, activities, and steps should be used to describe actionable elements. &amp;nbsp;Do not add tasks, activities,&#xD;
        and steps to amplify &quot;how&quot; a need should be satisfied. That is &quot;guidance&quot; not &quot;work&quot;.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Resist the temptation to artificially increase the number of actionable items. Project Managers will simply not&#xD;
        entertain a work structure with 1100 elements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Use activities, tasks, and steps to define a work road map and put road signs up about the work. &amp;nbsp;Keep the&#xD;
        guidance in the guidance.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Define base elements very generically, with add-on concepts that describe where more detailed elements fit in.&#xD;
        Example: &amp;nbsp;describe that DB design is part of design and is covered in design elements, even though separate&#xD;
        elements are not defined.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Scaling guidance elements in the UMF&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    The following sections describe some strategies&amp;nbsp;for scaling guidance elements.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategies&amp;nbsp;for scaling guidance&#xD;
&lt;/h5>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        When the content of an existing guidance method content element can be reused in a higher layer,&#xD;
        &lt;strong>&lt;u>contribute&lt;/u>&lt;/strong> more detail to&amp;nbsp;the existing guidance.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        If the content of an existing guidance element cannot be reused in the higher layer,&#xD;
        &lt;strong>&lt;u>replace&lt;/u>&lt;/strong> the guidance with more appropriate and elaborate guidance.&#xD;
    &lt;/li>&#xD;
&lt;/ol>&#xD;
&lt;h5>&#xD;
    Strategy&amp;nbsp;for scaling checklists&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    You can contribute additional items to the list&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy&amp;nbsp;for scaling templates&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    You can contribute additional templates, but it's probably better to create a different template guidance altogether,&#xD;
    rather than add different template formats to the same one.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Scaling roles in the UMF&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    This guideline describe some strategies&amp;nbsp;for scaling roles.&amp;nbsp;For example,&amp;nbsp;in one context, you may have one&#xD;
    role set and a few roles.&amp;nbsp;At the next level, single roles may become role sets&amp;nbsp;comprised of multiple&#xD;
    roles.&amp;nbsp;Scaling roles is much easier as a result of UMF's delayed role assignment approach, which supports the easy&#xD;
    definition of alternate role and role set definitions and assignments.&amp;nbsp;For more information, see the topic above&#xD;
    Roles in the UMF.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Scaling tasks in the UMF&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    The following sections describe some strategies&amp;nbsp;for scaling tasks.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 1: Packaging&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    Consider the following:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Package generic tasks (ie, a that task includes no details) in a sub-package of the work product&amp;nbsp;it produces&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Package specific tasks in your context. For tasks that are likely to need to be ‘split' later, package them in&#xD;
        their own package.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h5>&#xD;
    Strategy 2: Add guidance&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    Rather than creating more tasks, consider adding more specialized guidance to explain the detail of specific tasks.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 3: Contribute steps to a task&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    You can add a step between steps or at the end of the base task steps.&amp;nbsp; You cannot add to the wording of a&#xD;
    particular step.&amp;nbsp; For example, if you add a new sub-work product to the work product, you can contribute a new&#xD;
    step to create the sub-work product.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Tactical Workaround: When you really want to add to a particular step, indicate you are providing a specialized step by&#xD;
    naming your step the same as the one you wanted to append to and&amp;nbsp;adding a qualifier in brackets: eg, &quot;Determine&#xD;
    how elements collaborate [UML modeling]&quot;&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 4: Create new tasks&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    Create a new task when: a new role performs the task, it is a unit of work that should be tracked (ie, want it in the&#xD;
    WBS), it has different inputs or outputs.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 5:&amp;nbsp;Suggest a&amp;nbsp;change to the base task&amp;nbsp;&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    You could suggest a change to the tasks in the base (eg, OpenUP), so that the base task becomes something you can scale&#xD;
    from.&amp;nbsp; For example, suggest that the text be updated to only describe what is done, not how.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 6: Make a task an activity and its steps become tasks&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    Currently, RMC Tool cannot support this strategy.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Tactical workaround:&#xD;
&lt;/p>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        Deselect the package containing the task you are splitting (if it's not in a separate package, put it in a separate&#xD;
        package)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Create the new tasks&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Create a Process Pattern (activity) with the same name as the base task&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Add the new tasks to the activity&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Reconstruct relationships that were to the task to the appropriate new tasks&#xD;
    &lt;/li>&#xD;
&lt;/ol>&#xD;
&lt;h4>&#xD;
    Scaling work products in the UMF&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    The following sections describe some strategies&amp;nbsp;for scaling work products.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy&amp;nbsp;1: Use the notion of container work products in the base.&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    The base layer (the open source layer) includes a generic work product that can be used as the container for several&#xD;
    work products in lower levels. Scale by creating child work products of the base container. Contribute to the base work&#xD;
    products when possible, to reinforce the scaling connection, you could add text to say: &quot; For details about WPx see&#xD;
    &amp;lt;hyperlink to added WPx&amp;gt;&quot;.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Note:&amp;nbsp; You may need to suggest a change to the base work product to make it more scalable.&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;img&#xD;
    id=&quot;A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/example%20of%20scaling%20work%20products.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/example%20of%20scaling%20work%20products.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/example%20of%20scaling%20work%20products.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/example%20of%20scaling%20work%20products.gif:.:.:&quot;&#xD;
     border=&quot;0&quot; alt=&quot;Example of Scaling Work Products&quot; src=&quot;resources/example%20of%20scaling%20work%20products.gif&quot; />&#xD;
&lt;/p>&#xD;
&lt;p align=&quot;center&quot;>&#xD;
    &lt;b>Figure 1:&lt;/b> Example of scaling &quot;Design&quot; Work Product using the notion of container technique&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Figure 1 shows example when scaling up design from the open source layer. In the open source layer, the primary work&#xD;
    product is Design. Design is scaling to include conceptual design, logical design, operational design, subsystem&#xD;
    design, etc... in the commercial layer. Scaling to the commercial layer, the open source Design sub-WP is reused for&#xD;
    small projects (assuming some content proposals are accepted). For medium and large projects, content is contributed to&#xD;
    the Design work product which becomes a container for added sub-work products. Again, the licensable layer will reuse&#xD;
    commercial layer work products with some content contribution to the Design container work product.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Guideline: Use the most specific work product as input and output that makes sense&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Note: Extension is generally not a useful feature because too many associations are kept.&#xD;
&lt;/p>&#xD;
&lt;h5>&#xD;
    Strategy 2: Split a work product into two&#xD;
&lt;/h5>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        Before attempting to split a work product, consider recommending a change to the&amp;nbsp;base layer to add&#xD;
        the&amp;nbsp;work product&amp;nbsp;you need&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Define a custom category that contains the work product to remove and select that category in the do not publish&#xD;
        part of the configuration.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Create the new work product(s) and include them in your configuration.&#xD;
    &lt;/li>&#xD;
&lt;/ol>&#xD;
&lt;h5>&#xD;
    Strategy 3: Adding new work products&#xD;
&lt;/h5>&#xD;
&lt;p>&#xD;
    If you cannot scale using strategy 1 or 2, create a new work product. However, avoid just adding work&#xD;
    products.&amp;nbsp;Where possible, try to consolidate them under a container work product or consider whether&amp;nbsp;the open&#xD;
    source layer&amp;nbsp;should include the work product.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Note:&amp;nbsp;If you just cannot scale from a work product in&amp;nbsp;the&amp;nbsp;base layer, you may need to suggest a change&#xD;
    to the work product in&amp;nbsp;that base&amp;nbsp;(eg, suggest that the description be made more generic).&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Tool Information in the UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Tool information can come in many forms: &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_D0FBC781.html&quot;&#xD;
    guid=&quot;_BangwMaJEduMlb2cQZNTYw&quot;>tool&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_mentor_264766F3.html&quot;&#xD;
    guid=&quot;_yYy-mdnmEdmO6L4XMImrsA&quot;>tool mentor&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/example_9C7688B0.html&quot;&#xD;
    guid=&quot;_nE6fsMaFEduMlb2cQZNTYw&quot;>example&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/template_53432085.html&quot;&#xD;
    guid=&quot;_1MLN8MaIEduMlb2cQZNTYw&quot;>template&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/supporting_material_F91C8C5B.html&quot;&#xD;
    guid=&quot;_SwvUgMaIEduMlb2cQZNTYw&quot;>supporting material&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html&quot;&#xD;
    guid=&quot;_2RUJACO4EdqaNq6Ptg8uyA&quot;>capability pattern&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/white_paper_7231747.html&quot;&#xD;
    guid=&quot;_Kc1IIMaJEduMlb2cQZNTYw&quot;>white paper&lt;/a>s, etc.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    In the Unified Method Framework (UMF), tool information is defined in multiple plug-ins.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Tools (the standard categories) are defined in the Core in a Tool Definition&amp;nbsp;Base plug-in where they can be shared&#xD;
    between &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html&quot;&#xD;
    guid=&quot;_qhCTAFRREd2CWscN8Mx6rg&quot;>Practice&lt;/a>s.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Other tool information is defined according to its scope:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;em>General&lt;/em> tool information (as opposed to practice-specific tool information) is defined in the Tool&#xD;
        Definition Base plug-in.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;em>Practice-specific&lt;/em> tool information is defined in the Practice Base (or Extend) plug-in.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The UMF does NOT implement&amp;nbsp;a Delayed Assignment&amp;nbsp;approach for &lt;strong>tools&lt;/strong> because the assignment of&#xD;
    tool mentors to tools does not change (tool mentors are written for&amp;nbsp;a specific tool).&amp;nbsp;Thus:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Tool guidance is assigned to tasks in the Practice Base (or Extend) plug-in where the task is defined.&amp;nbsp;The&#xD;
        assignment is done directly in the task definition.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Tool mentors are assigned to the appropriate Tool standard categories&amp;nbsp;in the plug-in where the tool mentors&#xD;
        are defined. The assignment is done by defining a contributor to the Tool standard category (defined in a Tool&#xD;
        Definition plug-in) and then assigning the tool mentor to the Tool in the contributor.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Work Product Slots in the UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    In the Unified Method Framework (UMF),&amp;nbsp;Work Product Slots are defined as artifacts in Slot plug-ins.&amp;nbsp; When&#xD;
    authoring work products slots, be aware that the content cannot be practice or technique specific. Work product slots&#xD;
    are intended to be generic. Thus, the most important thing to document is the information the work product slot&#xD;
    represents, not its specific representation or the technique use to develop it.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Using Method Content Variability&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    This guideline explains how to utilize method content variability to modify an existing element without directly&#xD;
    changing the original element's base definition, or to create a new element based on an existing element. Changes are&#xD;
    defined in a separate content package or plug-in, and the original plug-in is kept intact. Thus, it allows you to&#xD;
    change method elements by simply changing a configuration (in other words, changing what plug-ins and packages are&#xD;
    included in the configuration).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Variability involves textual attributes and relationships.&amp;nbsp; In other words you can use variability to add, delete&#xD;
    change, or reuse&amp;nbsp;both text and relationships.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Variability is defined between two elements of the same type:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Base element: The target of the variability; the element being changed (or used as a base for new element)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Variability element: The element containing the changes (or new content or relationships) to be combined with the&#xD;
        base&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The base element is never changed directly. All changes (or new content) is defined in the variability element. The&#xD;
    variability element specifies which element is the base.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    As shown in Figure 1, when both the base element and the variability element are included in a configuration, the&#xD;
    configuration &quot;resolves&quot; the variability to produce the result, where that result depends on what variability was used.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;strong>Figure 1. Method content variability elements&lt;/strong>&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;img&#xD;
    id=&quot;A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:A_-_-_file:///C:/AMasell_cc_view/umf/lib751/shared/practice.mgmt.spi.base/guidances/guidelines/resources/variability.gif:.:.:&quot;&#xD;
     border=&quot;0&quot; alt=&quot;variability_elements&quot; src=&quot;resources/variability.gif&quot; />&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are different types of variability, each with their own characteristics, rules, pros and cons. Table 1 provides a&#xD;
    summary of the different types of variability and when you might want to use them.&lt;br />&#xD;
    &lt;br />&#xD;
&lt;/p>&lt;br />&#xD;
&lt;br />&#xD;
&lt;table title=&quot;Method Content Variability Summary&quot; border=&quot;1&quot; cellspacing=&quot;0&quot;&#xD;
summary=&quot;summary of different types of method content variability&quot; cellpadding=&quot;2&quot; width=&quot;85%&quot;>&#xD;
    &lt;caption>&#xD;
        &lt;strong>Table 1. Method Content Variability Summary&lt;/strong>&#xD;
    &lt;/caption>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>Variability Type&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Result&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Possible Uses&lt;/strong>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Contributes&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Contributing element adds to the base element&lt;br />&#xD;
                    (result = base element plus contributed characteristics)&#xD;
                &lt;/p>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Contributing (variability) element adds to the base element.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        The base appears in the published Web site, but the contributing element does not.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Incoming and outgoing relationships from the contributing element are added to the base&lt;br />&#xD;
                        Exception: If the relationship is a &quot;to one&quot; relationship (for example, a task has at most one&#xD;
                        primary performing role) then the relationship in the contributor is ignored if the base already&#xD;
                        has one.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Text from the contributing element is appended to corresponding base sections.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        A base element can have more then one contributor.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Contributes works transitively (a contributing element contributes its own contributors).&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Add guidance to an existing element&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Add steps to an existing task&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Add responsibility for a work product to a role&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Add a primary performing role to a task&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Add a work product to a task (as an input or output work product)&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Add text to existing elements&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Adding method elements to existing categories&lt;br />&#xD;
                        &lt;br />&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Replaces&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Replacing element replaces parts of the base element (incoming relationships remain)&lt;br />&#xD;
                    (result = new element, no base element)&#xD;
                &lt;/p>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Replacing (variability)&amp;nbsp;element replaces parts of the base element.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        The replacing element&amp;nbsp;appears in the published Web site but the base element does not.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Outgoing relationships in the replacing element are maintained, and the base's are ignored.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Incoming relationships to the base are maintained and added to the replacing element.&lt;br />&#xD;
                        Exception: If the replacing element has an incoming to-one relationship (for example, a replacing a&#xD;
                        role that includes a task performs the role relationship),&amp;nbsp;the replacing element&amp;nbsp;replaces&#xD;
                        that relationship in the&amp;nbsp;base element.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Text in the replacing element is left maintained, the base's text is ignored.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        A base element can only be replaced by one replacing element at a time. If two elements replace the&#xD;
                        same base element,&amp;nbsp;only one can be used for interpretation (the plug-in containing one of the&#xD;
                        replacing elements needs to be removed from the configuration or no replacement will take place).&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Replacement works transitively (if a replacing element is replaced itself, then&amp;nbsp;the final&#xD;
                        replacing element will prevail).&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Replace an existing method content element with another method content element&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Extends&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Extending element inherits characteristics of the base element&lt;br />&#xD;
                    (result = base element + new element)&#xD;
                &lt;/p>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Extending (variability) element inherits characteristics of the base element. The base element is&#xD;
                        unchanged.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Both the extending element&amp;nbsp;and the base appear in the published Web site.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Outgoing relationships from the base are added to the extending element.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Incoming relationships in the extending element&amp;nbsp;are maintained, and the base's are ignored.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Text is included in the extending element from the base element if the extending element&amp;nbsp;did&#xD;
                        not include any text for the given section.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Extends works transitively (if an extending element is extended itself the second extension&#xD;
                        inherits from its direct and indirect base elements).&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Define a new element that looks just like an existing element, with some modifications (in other&#xD;
                        words, define a variant or a specialization of an existing element)&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Extends is not used to modify an existing element&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Extends-Replaces&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;p>&#xD;
                    Replacing element replaces only values that have been redefined in the replacer&lt;br />&#xD;
                    (result = new element, no base element)&#xD;
                &lt;/p>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Combines the effects of extends and replaces variability, allowing you to selectively replace&#xD;
                        specific attributes and relationships of the base element.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Extending-replacing (variability) element replaces values in the base element that have been&#xD;
                        redefined in the&amp;nbsp;extending-replacing element . All other values of the base element are&#xD;
                        unaffected.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Both the extending-replacing element&amp;nbsp;and the base appear in the published Web&#xD;
                        site.&amp;nbsp;&amp;nbsp;&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Rename an existing element&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Replace a specific textual attribute of a method element&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Replace the outgoing relationships of an existing method element&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Replace the incoming relationships of an existing method element&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&lt;br />&#xD;
&lt;br />&#xD;
&lt;h4>&#xD;
    Order of evaluation&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Contribution precedes replacement (the contributes relationship is resolved first, followed by the replaces&#xD;
    relationship). The evaluation of contribution and replacement is performed top-down in the specialization hierarchy.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Handy tricks&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    If you ever find that you want to create an element that looks just like an existing element, but includes some&#xD;
    additional content, you can use a combination of extends and contributes to achieve the desired result.&amp;nbsp; To do&#xD;
    this, perform the following steps:&#xD;
&lt;/p>&#xD;
&lt;ol>&#xD;
    &lt;li>&#xD;
        Define a method element that that extends the original base element. This results in a new element that looks just&#xD;
        like the original element.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Define another method element that contributes to the extending element and add the desired content. This results&#xD;
        in adding the new content to the new element that already includes the original content.&#xD;
    &lt;/li>&#xD;
&lt;/ol>&#xD;
&lt;p>&#xD;
    The net result:&amp;nbsp;A new element that includes the original content plus the new content.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
