<?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="-TPAUpjDlUfq2jYIEwi8dZw" name="categorizing,_kY8j4EH-Ed-bmYzvomIdMg" guid="-TPAUpjDlUfq2jYIEwi8dZw" changeDate="2011-10-10T12:17:24.693-0700" version="7.5.0">
  <mainDescription>&lt;h3>&#xD;
    Categorizing Method Elements Using Standard Categories&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Standard Categories provide a means to categorize core method content in line with the best practices for creating&#xD;
    structured methods. Standard Categories are linked to a specific method content type.&amp;nbsp; The Standard Category types&#xD;
    are:&#xD;
&lt;/p>&#xD;
&lt;ul dir=&quot;ltr&quot;>&#xD;
    &lt;li>&#xD;
        &lt;strong>Disciplines&lt;/strong>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        A &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html&quot;&#xD;
        guid=&quot;_yGUuidnmEdmO6L4XMImrsA&quot;>discipline&lt;/a>&amp;nbsp;is a category of &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 that are related to a major area of concern within the overall IT&#xD;
        environment. A task can belong to only one discipline.&amp;nbsp; For example, on a software development project, it is&#xD;
        common to perform certain requirements tasks in close coordination with analysis and design tasks. Separating these&#xD;
        tasks into separate disciplines makes the tasks easier to comprehend. Disciplines can be organized using Discipline&#xD;
        Groupings.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Initial recommendations are to develop separate discipline groupings for each major context and standardize on the&#xD;
        set of disciplines within that context, allowing for overlap between contexts where appropriate. While disciplines&#xD;
        may have many similarities to domains for some areas, no formal relationship between the two has been defined.&#xD;
        Disciplines are currently intended to be independent of role sets.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        In general, the following are some criteria that affect how you assign tasks to specific disciplines in your&#xD;
        method:&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Number of tasks: The more tasks you have, the more there is a need to organize them into disciplines&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Published representation of the method: How do consumers of the method want to see the tasks organized;&#xD;
                    define disciplines for those organizational elements&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Governance: How the tasks are governed; define separate domains for tasks that are governed differently&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
    &lt;p style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Processes can also be associated with disciplines as&amp;nbsp;Reference&amp;nbsp;Workflows.&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/p>&#xD;
    &lt;p style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Note: In some cases, the&amp;nbsp;disciplines and&amp;nbsp;domains are&amp;nbsp;the same (i.e., the same set of names is used&#xD;
        for&amp;nbsp;both).&amp;nbsp; This approach minimizes the number of different ways you categorize&amp;nbsp;things, which some&#xD;
        see as an advantage.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul dir=&quot;ltr&quot;>&#xD;
    &lt;li>&#xD;
        &lt;strong>Domains&lt;/strong>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        A &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html&quot;&#xD;
        guid=&quot;_yHEVYdnmEdmO6L4XMImrsA&quot;>domain&lt;/a>&amp;nbsp;is a refineable, logical, categorization of related &lt;a&#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 grouped together based on timing, resources, or relationship.&#xD;
        While a Domain categorizes many work products, a work product belongs to only one Domain. Domains can be further&#xD;
        divided into sub-domains.&lt;br />&#xD;
        &amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Domains are seen by some to be more context-neutral than disciplines (i.e., disciplines tend to be more&#xD;
        context-specific).&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        It is recommended that only parent work products be mapped to a domain, not child work products. This will yield a&#xD;
        more pleasing tree structure in the published web site because child work products will only show up under their&#xD;
        parent. If child work products are assigned to a domain, then they will also be displayed in the tree view at the&#xD;
        ‘top level' under the discipline, as well as under its parent.&lt;br />&#xD;
        &amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        In general, the following are some criteria that affect how you assign work products to specific domains in your&#xD;
        method:&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Number of work products: The more work products you have, the more there is a need to organize them into&#xD;
                domains&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Published representation of the method: How do consumers of the method want to see the work products&#xD;
                    organized; define domains for those organizational elements&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Governance: How the work products are governed; define separate domains for work products that are&#xD;
                    governed differently&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
    &lt;p style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Note: In some cases, the&amp;nbsp;domains and&amp;nbsp;disciplines are&amp;nbsp;the same (i.e., the same set of names is used&#xD;
        for&amp;nbsp;both).&amp;nbsp; This approach minimizes the number of different ways you categorize&amp;nbsp;things, which some&#xD;
        see as an advantage.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul dir=&quot;ltr&quot;>&#xD;
    &lt;li>&#xD;
        &lt;strong>Work Product Kinds&lt;/strong>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        A &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_kind_F04A382B.html&quot;&#xD;
        guid=&quot;_QWhfYMaJEduMlb2cQZNTYw&quot;>work product kind&lt;/a>&amp;nbsp;is another category for grouping &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.&amp;nbsp; A work product can have many work product kinds. As an&#xD;
        example, you might want to have a series of work product kinds that correspond to the overall intent of work&#xD;
        products, such as specification, plan, or model.&amp;nbsp; The use of work product kinds is optional.&lt;br />&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        In general, the following are some criteria that affect how you assign work products to specific work product kinds&#xD;
        in your method: &#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Type of work product: Different work product kinds can be defined for artifacts vs outcomes&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Number of work products: The more work products you have, the more there is a need to organize them&#xD;
                    into work product kinds&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                        Published representation of the method: How do consumers of the method want to see the work&#xD;
                        products organized; do they want to see an alternate organization for the work products, in&#xD;
                        addition to the domain organization.&amp;nbsp; Define role sets for those organizational elements..&#xD;
                    &lt;/div>&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
    &lt;p style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        Work product kinds are usually more general than domains and usable across contexts.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul dir=&quot;ltr&quot;>&#xD;
    &lt;li>&#xD;
        &lt;strong>Role Sets&lt;/strong>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        A &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>&amp;nbsp;is used to categorize &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
        guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>s with certain commonalities together. For example, in a software&#xD;
        development environment, an Analyst role set could be used to group together roles such as Business Process&#xD;
        Analyst, System Analyst and Requirements Specifier. Each of these roles work with similar techniques and have&#xD;
        overlapping skills, but may be responsible for performing certain tasks and creating certain work products. Role&#xD;
        sets can be organized using &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_set_grouping_1BF92F71.html&quot;&#xD;
        guid=&quot;_D8F28KNfEdyMFYhoCpD11Q&quot;>role set grouping&lt;/a>s.&lt;br />&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        In general, the following are some criteria that affect how you define role sets and how you assign roles to&#xD;
        specific role sets: &#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Number of roles: The more roles you have, the more there is a need to organize them into role sets&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Published representation of the method: How do consumers of the method want to see the roles organized;&#xD;
                    define role sets for those organizational elements&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                &lt;div style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
                    Governance: How the roles and role sets are governed; define separate role sets for roles that are&#xD;
                    governed differently&lt;br />&#xD;
                &lt;/div>&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Tools&lt;/strong>&#xD;
    &lt;/li>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        A &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>&amp;nbsp;is a category for &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. Tools can also provide general descriptions of a tool and it's&#xD;
        general capabilities.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p style=&quot;LIST-STYLE-TYPE: none&quot; dir=&quot;ltr&quot;>&#xD;
    You should define a standard category any time you have a need to categorize method elements.&amp;nbsp; Multiple levels of&#xD;
    categories are possible, but you should only define what you need to manage your method content.&amp;nbsp; For example, if&#xD;
    your method only contains&amp;nbsp;two tasks, do you really need a discipline?&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    An important part of defining an element is naming it.&amp;nbsp; For recommendations on naming standard categories, see&#xD;
    topic Method Element Naming Conventions in the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/general_naming_conventions_5651B0CC.html&quot;&#xD;
    guid=&quot;__I8S0D2kEd-lU6YVR9_PJQ&quot;>Guideline: General Naming Conventions&lt;/a>.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    You may also want to capture guidance on how to decide what tasks belong in the discipline in the &lt;strong>Key&#xD;
    considerations&lt;/strong> property of the category.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Once the categories are defined, method elements can be assigned to them and the resulting categories can be used to&#xD;
    access the information in the method, as well as in custom categories as part of navigation views.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Standard categories cannot be packaged in separate packages in plug-ins, thus alternative categorization schemes must&#xD;
    be defined in separate plug-ins.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Guidance can also be associated with standard categories. Such guidance should be applicable to the category as a&#xD;
    whole,&amp;nbsp;and should not be all guidance that is associated with each of the elements categorized to that category.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Customizing a Standard Categories&amp;nbsp;&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    It is assumed that the&amp;nbsp;standard category&amp;nbsp;(e.g., &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html&quot;&#xD;
    guid=&quot;_yHEVYdnmEdmO6L4XMImrsA&quot;>domain&lt;/a>&amp;nbsp;or &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html&quot;&#xD;
    guid=&quot;_yGUuidnmEdmO6L4XMImrsA&quot;>discipline&lt;/a>) being customized cannot be modified directly. Thus, all changes must be&#xD;
    stored in a separate plug-in from the&amp;nbsp;standard category being customized. To see the resulting changes, you need&#xD;
    to browse or publish a configuration that includes the original standard category plus the customizations. If&amp;nbsp;you&#xD;
    can modify the standard category directly, you should follow the guidelines described in the topic Categorizing Method&#xD;
    Elements Using Standard Categories below.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are a number of different ways that you can customize an existing standard category.&amp;nbsp;You can:&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Assign elements to the category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Remove elements from the category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Replace an existing standard category with a new standard category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Rename the standard category&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Specific standard category customization scenarios are described in the remaining sections of this guideline.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Assign elements to the category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to add a method element to an existing standard category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the standard category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a standard category that contributes to the existing standard category and assign the&#xD;
        new elements. For more information on contribution, see the topic Using Method Content Variability in the &lt;a&#xD;
        class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html&quot;&#xD;
        guid=&quot;_fx7TMD3REd-realK_We5vA&quot;>Guideline: Defining Method Elements&lt;/a>.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Remove elements from the category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to remove a method element from an existing standard category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the standard category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a standard category and assign the same elements as in the original standard category,&#xD;
        except for the element you want to remove.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Change the definition of the new standard category to extends-replace the original standard category.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Replace an existing standard category with a new&amp;nbsp;standard category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to replace an existing standard category with a new standard category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the standard category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define the standard category and assign the desired elements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Change the definition of the new standard category to replace the original standard category.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Rename an existing standard category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to rename an existing standard category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the standard category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a standard category and give it the desired presentation name. Specify that the new&#xD;
        standard category is to extend-replace the existing standard category.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Standard Categories 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 standard&#xD;
    categories.&amp;nbsp;Those constraints vary for the different standard category types.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The UMF implements a Delayed Assignment&amp;nbsp;approach for &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html&quot;&#xD;
    guid=&quot;_yGUuidnmEdmO6L4XMImrsA&quot;>discipline&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html&quot;&#xD;
    guid=&quot;_yHEVYdnmEdmO6L4XMImrsA&quot;>domain&lt;/a>s and &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_kind_F04A382B.html&quot;&#xD;
    guid=&quot;_QWhfYMaJEduMlb2cQZNTYw&quot;>work product kind&lt;/a>s.&amp;nbsp;It does not implement&amp;nbsp;a delayed category assignment&#xD;
    for &lt;strong>role sets&lt;/strong> because the definition of roles and role sets are strongly linked.&amp;nbsp;Roles are&#xD;
    assigned to role sets in the same plug-in as where the roles are defined, the Role Definition plug-in (their&#xD;
    definitions are shared).&amp;nbsp;For more information on roles in the UMF, see the topic Roles in the UMF in the &lt;a&#xD;
    class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html&quot;&#xD;
    guid=&quot;_fx7TMD3REd-realK_We5vA&quot;>Guideline: Defining Method Elements&lt;/a>. The UMF also does not implement&amp;nbsp;a delayed&#xD;
    category assignment for &lt;strong>tools&lt;/strong> because the assignment of tool mentors to tools does not change (tool&#xD;
    mentors are written for&amp;nbsp;a specific tool).&amp;nbsp;For more information on tools in the UMF, see the&#xD;
    topic&amp;nbsp;Tool&amp;nbsp;Information in the UMF in the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html&quot;&#xD;
    guid=&quot;_fx7TMD3REd-realK_We5vA&quot;>Guideline: Defining Method Elements&lt;/a>.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;br />&#xD;
    The &quot;delayed standard categories&quot; (disciplines, domains and work product kinds) are &lt;strong>&lt;em>defined&lt;/em>&lt;/strong>&#xD;
    in a Category Definition Base plug-in.&amp;nbsp;Elements are &lt;em>&lt;strong>assigned&lt;/strong>&lt;/em> to these categories in the&#xD;
    Assign plug-ins associated with the Base plug-in that contains the elements to be assigned (tasks and work&#xD;
    products).&amp;nbsp;For information on how these assignments are defined, see the topic Delayed Assignment in the UMF in&#xD;
    the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html&quot;&#xD;
    guid=&quot;_fx7TMD3REd-realK_We5vA&quot;>Guideline: Defining Method Elements&lt;/a>.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The benefits to the UMF approach to standard categories are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        The same categories can be used with different element assignments (shared Category Definition plug-ins)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Alternate category definitions and element assignments can be defined (provide alternate Category Definition and&#xD;
        Assign plug-ins)&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Defining Navigation Views&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    This guideline provides recommendations on how to use custom categories to define navigation views. For general&#xD;
    information on custom categories, see the topic Categorizing Method Elements Using Custom Categories below.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Navigation views are defined as custom categories that define the structure and content of the published method. In&#xD;
    general, the following are some criteria that affect how you define navigation views for your method:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Number of elements: The more elements you have, the more there is a need to organize them for easy navigation&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Published representation of the method: How do consumers of the method want to navigate the published&#xD;
        method.&amp;nbsp;Define navigation views to support the desired navigation paths.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    When defining navigation views, it is important to consider the intended audience and usage model of the&#xD;
    view,&amp;nbsp;since this will drive the overall organization/hierarchy of the view. For example, will the view be&#xD;
    organized by element type or by process area?&amp;nbsp;This information can be captured in the description of the custom&#xD;
    category itself.&amp;nbsp;Such information will be helpful to the person who may may want to consider including the&#xD;
    navigation view in their configuration for publication.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    When defining the navigation views, it is a good idea to create a navigation views that represents a natural reading&#xD;
    sequence.&amp;nbsp;The guideline to the user would be: &quot;Yes, you CAN click on the links within pages, but that's only if&#xD;
    you want to jump to another location in the website, or do some free exploration. If you want to read the material in&#xD;
    the recommended order, and make sure you didn't miss anything, then use this navigation view&quot;.&amp;nbsp;In such a &quot;natural&#xD;
    reading sequence&quot; navigation view,&amp;nbsp;&amp;nbsp;each topic should appear only once.&amp;nbsp;The benefits of this approach&#xD;
    are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        You can print the configuration&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        You can browse the expanded tree to find a topic (rather than use the &quot;search&quot; feature)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        You can look for information by logically figuring out what category it logically belongs to.&amp;nbsp;That way even&#xD;
        if&amp;nbsp;you&amp;nbsp;don't know the name of a page,&amp;nbsp;you can find it by expanding the appropriate nodes in the&#xD;
        navigation view.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The following are some navigation views that you my want to consider defining for your method:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Welcome&lt;/strong> view: Includes a Welcome page, as well as About and What's New pages.&amp;nbsp;Provides a&#xD;
        starting point for first time users, no matter what their role.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Getting Started&lt;/strong> view: Provides quick access to key concepts, Web site structure&amp;nbsp;and usage&#xD;
        information for the new user.&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Key Elements&lt;/strong> view: Provides quick access to the key elements of the method -- processes, roles,&#xD;
        tasks, work products and processes (it is assumed that guidance is accessible from those&#xD;
        elements).&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Team&lt;/strong> view: Provides access to all elements in the configuration, organized by method element type&#xD;
        and then by category.&amp;nbsp;This views serves as a type of index to all elements in the method.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Role-based&lt;/strong> views: Provides access to the elements of most interest to the role .&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Process-based&lt;/strong> views: Provides access to the elements that support the process.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Organization/Project-based&lt;/strong> views: Provides access the the elements of most interest to the&#xD;
        organization/project.&amp;nbsp;This view&amp;nbsp;connects the abstractness of the method (content elements and guidance)&#xD;
        with the concreteness of project life (physical work products) and encourages the team to live the process. It is&#xD;
        minimalist and thus largely artifact-based, but may also include: &#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Links to the current version of artifacts&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Elements of the development case,&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Selected guidance&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Project team information&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Change Request information&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Discussion forums&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Navigation views in the UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    The Unified Method Framework (UMF)&amp;nbsp;defines two types of navigation view elements:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Configuration-specific&lt;/strong>, meaning they are intended to be published as part of a specific&#xD;
        configuration&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Common&lt;/strong>, meaning they are intended to be shared across plug-ins and configurations. The UMF defines&#xD;
        &lt;em>navigation view building blocks&lt;/em>, which are intended to be used across navigation views, as well as generic&#xD;
        navigation views that can be used as-is or in parts in other navigation views.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Where the navigation view elements are defined and how elements are assigned to them is different for each.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;strong>Navigation view building blocks&lt;/strong> are elements that may be used across a number of navigation&#xD;
    views.&amp;nbsp;The UMF navigation view building blocks categorize method elements by &quot;types&quot; as defined in the meta model&#xD;
    (i.e., &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html&quot;&#xD;
    guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;>role&lt;/a>s, &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, &lt;a 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 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, &lt;a 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, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/checklist_D780FDF.html&quot;&#xD;
    guid=&quot;_7vpJsMaCEduMlb2cQZNTYw&quot;>checklist&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/guideline_1D590B95.html&quot;&#xD;
    guid=&quot;_uK8HMMaFEduMlb2cQZNTYw&quot;>guideline&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/delivery_process_BCDF50B7.html&quot;&#xD;
    guid=&quot;_ZufeMCO3EdqaNq6Ptg8uyA&quot;>delivery process&lt;/a>es, etc), as well as some other key ones (e.g., release&#xD;
    information).&amp;nbsp;The navigation view building blocks are defined as &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html&quot;&#xD;
    guid=&quot;_eqw94MaFEduMlb2cQZNTYw&quot;>custom categories&lt;/a>&amp;nbsp;in Navigation View Definition plug-ins, where they can be&#xD;
    shared across plug-ins. If you want to define additional navigation view building blocks, define an Extends plug-in&#xD;
    that includes the new building blocks and include the new building blocks in a custom category that contributes to the&#xD;
    base navigation view building blocks custom category.&amp;nbsp;Using such &quot;super custom categories&quot; will keep the list of&#xD;
    top-level custom categories from getting too long.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;strong>Generic navigation views&lt;/strong> are navigation views that may be applicable in multiple&#xD;
    configurations.&amp;nbsp;They are also defined as custom categories in Navigation View Definition plug-ins, where they can&#xD;
    be shared across plug-ins.&amp;nbsp;Generic navigation views assemble navigation view building blocks into something that&#xD;
    can be used as a whole or in parts as a publishable navigation view.&amp;nbsp;For example, a generic navigation view can be&#xD;
    used to provide a view of everything in the configuration. These navigation views can be used for specific method&#xD;
    configurations as-is, or tweaked to address the specific needs of the configuration (e.g., extend/replace it or ignore&#xD;
    and build their own).&amp;nbsp;The benefits of sharing navigation view elements is that you automatically get consistent&#xD;
    navigation views.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;strong>Configuration-specific navigation views&lt;/strong> are defined as custom categories in the Publish plug-in for&#xD;
    the configuration that is to be published.&amp;nbsp;The configuration-specific navigation views indicate what elements&#xD;
    elements (or navigation view building blocks) are to be included.&amp;nbsp;When defining a configuration-specific&#xD;
    navigation view, you can:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Create a new view using existing navigation view elements&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Reuse the common generic navigation view, replacing and/or adding to selected elements, as needed.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Custom categories that are designed to be navigation views should include &quot;view&quot; in the name.&amp;nbsp;Also, the custom&#xD;
    categories that represent the navigation view tabs for the configuration should be &quot;packaged&quot; in a parent custom&#xD;
    category with &quot;view tabs&quot; in the name.&amp;nbsp;This makes it easy to identify the custom categories that have been&#xD;
    designed to serve as the navigation views for the configuration.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;br />&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The UMF also defines a &lt;strong>&quot;Do Not Publish&quot; category&lt;/strong>. It is also defined as a custom category in&#xD;
    Navigation View Definition Base plug-ins, where it can be shared across plug-ins.&amp;nbsp;Plug-ins can map specific method&#xD;
    elements to this custom category to keep the elements from being published. This category is especially useful for&#xD;
    publish plug-ins that are constructing custom views for publishing.&amp;nbsp;The elements in&amp;nbsp;this category should be&#xD;
    removed from all publishable configurations.&amp;nbsp;For more information on publishable configurations, see [Concept:&#xD;
    Practice Library Configuration Types].&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    For more information on the UMF plug-in types (e.g., Navigation View Definition plug-ins, Publish plug-ins, etc.), see&#xD;
    [Concept: Practice Library Plug-In Types].&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Navigation Views in the IBM UMF&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    RMC 7.5 (not EPF Composer) has a feature for &quot;tag-based queries&quot; that provides some additional improvements to the&#xD;
    common navigation view elements.&amp;nbsp; Using that feature, specific method elements can be tagged with a special key&#xD;
    word which is then included as part of a query in a custom category, where the results of the query populate the custom&#xD;
    category.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The following are some specific ways in which that feature has been leveraged in the UMF content:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Release information&lt;/strong>: &quot;Release information&quot; is not a type, so we can't use the &quot;Include elements of&#xD;
        type&quot; feature in the base common navigation view element. So instead, we tag all release information method&#xD;
        elements with a &quot;release_info&quot; tag and then replace the placeholder common navigation view element with a custom&#xD;
        category that does a tag-based query.&amp;nbsp;&lt;u>&lt;em>[*** I checked and none of the practice release information is&#xD;
        tagged.&amp;nbsp; ***]&lt;/em>&lt;/u>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;strong>Structured practice list&lt;/strong>.&amp;nbsp; We tagged all technical practices with&amp;nbsp;a &quot;technical&quot; tag and&#xD;
        defined a &quot;technical practice list&quot; custom category that does a tag-based query on &quot;technical&quot;.&amp;nbsp; We tagged all&#xD;
        management practices with&amp;nbsp;a &quot;management&quot; tag and defined a &quot;management practice list&quot; custom category that&#xD;
        does a tag-based query on &quot;management&quot;.&amp;nbsp; We then replaced the &quot;structured practice list&quot; placeholder in the&#xD;
        common navigation view elements with a custom category that contains the &quot;technical&quot; and &quot;management&quot;&#xD;
        tag-based-query custom&amp;nbsp;categories. This way, if you add a new technical practice, you just have to tag the&#xD;
        practice element with &quot;technical&quot; and it will appear correctly in the view.&amp;nbsp; &lt;em>&lt;u>[*** I checked and none of&#xD;
        the practice release information is tagged.&amp;nbsp; ***]&lt;/u>&lt;/em>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    These tag-based-query custom categories are defined in the commercial-level extensions to the base navigation view&#xD;
    definition plug-in.&amp;nbsp; These new custom categories are defined to replace the non-query-based custom categories in&#xD;
    the base navigation view definition plug-in.&amp;nbsp;&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Categorizing Method Elements Using Custom Categories&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Custom categories can be used to categorize method elements so that the practitioners can find them easily and quickly.&#xD;
    They also form the basis of a published configuration by defining the navigation view&amp;nbsp;structure for the&#xD;
    configuration.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Custom categories are highly customizable and can contain any type of element. Custom categories allow you to&#xD;
    categorize content according to any hierarchical scheme you want and can then be used to compose publishable views, as&#xD;
    well as providing a means to organize the method content prior to publishing. For example, you could create a &lt;a&#xD;
    class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html&quot;&#xD;
    guid=&quot;_eqw94MaFEduMlb2cQZNTYw&quot;>custom category&lt;/a>&amp;nbsp;that logically organizes content relevant to your development&#xD;
    organization department, such as a Testing category that groups together all roles, work products, tasks, and guidance&#xD;
    elements relevant to testing.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    When defining custom categories, consider the different ways you may want to access the elements, as well as the ways&#xD;
    in which the end-user of the method may want to access the method elements.&amp;nbsp; The former may result in ideas for&#xD;
    &quot;method management-focused&quot; custom categories, while the latter may result in ideas for navigation view focused custom&#xD;
    categories. What information is needed? How does one find that information? Well crafted custom categories will help&#xD;
    enormously.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Custom categories can be nested to create a categorization hierarchy. For example, if you want to define a navigation&#xD;
    view that includes &quot;sub-folders&quot;, you can do that by defining a sub-custom category in a navigation view custom&#xD;
    category for each folder you would like to be included.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Custom categories can also be nested to organize the custom categories.&amp;nbsp;For example, if you define a set of custom&#xD;
    categories that are intended to represent navigation views and another set that are not.&amp;nbsp;You may want to package&#xD;
    all the navigation view custom categories in a single custom category.&amp;nbsp;In this case, the topmost custom category&#xD;
    is more like a package than a custom category.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    You can add elements to existing categories by defining a custom category that contributes to the original custom&#xD;
    category and adds the desired elements.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    For methods containing a lot of elements and plug-ins, defining a shared set of custom categories can be beneficial for&#xD;
    the following reasons:&lt;br />&#xD;
    &lt;br />&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Method authors have a consistent way of categorizing content&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Method authors and delivery practitioners can find related content more easily and reference it&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Published configurations will have the same look and feel to the delivery practitioner making the web site easier&#xD;
        to navigate and information easier to find&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Delivery practitioners will require less education and training on the set of configurations with which they work&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    For recommendations on naming custom categories, see the topic Method Element Naming Conventions in the &lt;a&#xD;
    class=&quot;elementLinkWithType&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/general_naming_conventions_5651B0CC.html&quot;&#xD;
    guid=&quot;__I8S0D2kEd-lU6YVR9_PJQ&quot;>Guideline: General Naming Conventions&lt;/a>.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Be sure to capture the purpose of the custom category in its description, so that the reason the custom category was&#xD;
    created and what it contains is maintained.&amp;nbsp;This will make it easy for other method authors to understand when the&#xD;
    category should be used.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Custom categories cannot be packaged in separate packages in plug-ins.&amp;nbsp;Thus alternative categorization schemes&#xD;
    must be defined in separate plug-ins.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Customizing a Custom Category&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    It is assumed that the &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html&quot;&#xD;
    guid=&quot;_eqw94MaFEduMlb2cQZNTYw&quot;>custom category&lt;/a>&amp;nbsp;being customized cannot be modified directly. Thus, all changes&#xD;
    must be stored in a separate plug-in from the&amp;nbsp;custom category being customized. To see the resulting changes, you&#xD;
    need to browse or publish a configuration that includes the original custom category plus the customizations.&#xD;
    If&amp;nbsp;you can modify the custom category directly, you should follow the guidelines described&amp;nbsp; above in&#xD;
    Categorizing Method Elements Using Custom Categories.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    There are a number of different ways that you can customize an existing custom category.&amp;nbsp;You can:&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Add elements to an existing custom category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Re-order the elements in an existing custom category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Replace an existing custom category&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Rename an existing custom category&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Specific custom category view customization scenarios are described in the remaining sections of this guideline.&#xD;
&lt;/p>&#xD;
&lt;h4>&#xD;
    Add elements to an existing custom category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to add a method element to an existing custom category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the custom category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a custom category that contributes to the existing custom category. For more information&#xD;
        on contribution, see the topic Using Method Content Variability in the &lt;a class=&quot;elementLinkWithType&quot;&#xD;
        href=&quot;./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html&quot;&#xD;
        guid=&quot;_fx7TMD3REd-realK_We5vA&quot;>Guideline: Defining Method Elements&lt;/a>.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the contributor, assign the elements you would like to see added to the category. If you want to add a&#xD;
        sub-custom category to the category, define a sub-custom category. You can even control the order in which the&#xD;
        elements appear in the category, relative to the existing elements.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Re-order the elements in an existing custom category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to reorder the elements in an existing custom category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the custom category&amp;nbsp;customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a custom category and assign all the same elements as the original custom category.&#xD;
        Re-order the elements in the custom category, as desired.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Change the definition of the new custom category to replace the original&amp;nbsp;custom category&amp;nbsp;using method&#xD;
        content variability.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Replace an existing custom category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to replace an existing custom category&amp;nbsp;with a new custom category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the custom category&amp;nbsp;customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a custom category and assign all desired elements to the custom category. Re-order the&#xD;
        elements in the custom category, as desired.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Change the definition of the new custom category to replace the original custom category using method content&#xD;
        variability.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h4>&#xD;
    Rename an existing custom category&#xD;
&lt;/h4>&#xD;
&lt;p>&#xD;
    Perform the following steps to rename an existing custom category:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        If it does not already exist, create a plug-in to contain the custom category customizations.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        In the new plug-in, define a custom category that extends and replaces the existing custom category using method&#xD;
        content variability.&amp;nbsp;&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Give the new custom category the desired presentation name.&#xD;
    &lt;/li>&#xD;
&lt;/ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
