commit 293427b95d600408b29b706c5d100680bc3bf229
author bmacisaac <bmacisaac> Wed Jul 06 22:36:34 2011 +0000
committer bmacisaac <bmacisaac> Wed Jul 06 22:36:34 2011 +0000
tree 988c330ea212a027c9efd3abec4fda9f4d92bb42
parent a6e6a67c42d6994f82683975a1bc854a83571253

Bugzilla 351377
Removed out-dated naming example taken from Method Development practices that no longer exist (and were never in EPF anyways).

epf_prac_151/practice.bus.mdev.base/guidances/guidelines/general_naming_conventions.xmi

diff --git a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/general_naming_conventions.xmi b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/general_naming_conventions.xmi
index 1d703b1..65f932f 100644
--- a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/general_naming_conventions.xmi
+++ b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/general_naming_conventions.xmi
@@ -1,1436 +1,1382 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-UMwO0Odv_iQVxPV40lG2kA" name="new_guideline,__I8S0D2kEd-lU6YVR9_PJQ" guid="-UMwO0Odv_iQVxPV40lG2kA" changeDate="2010-04-21T10:11:28.000-0700" version="7.5.0">
-  <mainDescription>&lt;h3>
-    General Naming Conventions
-&lt;/h3>
-&lt;p>
-    This guidance provides general information on naming method elements.&amp;nbsp; For method element-specific naming
-    guidance, see the attached guidance.
-&lt;/p>
-&lt;h5>
-    Abbreviations
-&lt;/h5>
-&lt;p>
-    It is a good practice is to provide a list of approved abbreviations for your project.&amp;nbsp;Using a standard set of
-    abbreviations simplifies searches for not only the method authoring team, but also for users of your published web
-    site.
-&lt;/p>
-&lt;h4>
-    Name fields
-&lt;/h4>
-&lt;p>
-    Most method elements have two name fields:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        The&amp;nbsp;&lt;strong>Name&lt;/strong> is always present since it is the internal name&amp;nbsp;for the element.&lt;br />
-    &lt;/li>
-    &lt;li>
-        The &lt;strong>Presentation Name&lt;/strong> is present for some elements; it is the name&amp;nbsp;displayed in the published
-        web site for the element. Thus, a friendly name&amp;nbsp;should be used.
-    &lt;/li>
-&lt;/ul>
-&lt;h4>
-    General naming guidelines
-&lt;/h4>
-&lt;p>
-    In general, all method elements should following the following recommendations:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        Name should reflect the essence of the element
-    &lt;/li>
-    &lt;li>
-        Where an element has both a name and a Presentation Name field, try to name them consistently (though abbreviations
-        may be used in the internal name)
-    &lt;/li>
-    &lt;li>
-        Abbreviations should be either very common to the plug-in domain (for example, J2EE for Java 2 Enterprise Edition)
-        or they should be taken out of a list of common abbreviations for the project. If abbreviations are not
-        standardized, it is very likely that similar but not quite identical abbreviations will occur here and there,
-        introducing confusion and errors later on
-    &lt;/li>
-&lt;/ul>
-&lt;p>
-    For general guidelines on naming variants, see the section on that topic later in this guideline.&lt;br />
-&lt;/p>
-&lt;h4>
-    Method element-specific naming guidelines
-&lt;/h4>
-&lt;p>
-    Table 1 provides element-specific guidelines for naming the different types of method elements.&amp;nbsp;
-&lt;/p>
-&lt;p>
-    &lt;strong>Table 1: Method Element Naming Conventions&lt;/strong>&lt;br />
-    &lt;br />
-&lt;/p>
-&lt;table id=&quot;table3&quot; border=&quot;1&quot;>
-    &lt;tbody>
-        &lt;tr align=&quot;middle&quot;>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Element&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;25%&quot;>
-                &lt;strong>Guideline&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;55%&quot;>
-                &lt;strong>Reason&lt;/strong>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Plug-in
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use&amp;nbsp; internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                    &lt;li>
-                        Omit the word &quot;plug-in&quot; in the names (it is redundant)
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    The value&amp;nbsp;of the&amp;nbsp;Name field determines the directory name used in the file
-                    system.&amp;nbsp;&amp;nbsp;
-                &lt;/p>
-                &lt;p>
-                    Compound names, separated by periods, can be used in the Name field to organize the list of plug-ins in
-                    the library view to make them easier to navigate for process authors.&amp;nbsp;
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;p>
-                    Method content package
-                &lt;/p>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use&amp;nbsp; internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Method content package names are displayed when viewing the method library. They are also the elements
-                    that users can choose to include or exclude from their configurations. Thus, these names need to be
-                    easy to understand and&amp;nbsp;self-explanatory.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;p>
-                    Process package
-                &lt;/p>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use friendly name&amp;nbsp;friendly name&amp;nbsp;for Name field (process&amp;nbsp;packages only have a single
-                        name field)
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Process package names are displayed when viewing the method library. They are also the elements that
-                    users can choose to include or exclude from their configurations. Thus, these names should be easy to
-                    understand and&amp;nbsp;self-explanatory.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Standard category
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul class=&quot;noindent&quot;>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Standard Category names are displayed when viewing the method library. They are also the elements that
-                    users can choose to include or exclude from their configurations, as well as to include or exclude from
-                    other custom categories. Thus, these names should be easy to understand and&amp;nbsp;self-explanatory.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Custom category
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul class=&quot;noindent&quot;>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-                &lt;p>
-                    If the custom category is to be used for a navigation view, include &quot;view&quot; in both name fields.&amp;nbsp;
-                &lt;/p>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Custom Category names are displayed when viewing the method library. They are also the elements that
-                    users can choose to include or exclude from their configurations, as well as to include or exclude from
-                    other custom categories. Thus, these names should be easy to understand and&amp;nbsp;self-explanatory.
-                &lt;/p>
-                &lt;p>
-                    The Presentation name of a custom category that is used as a navigation view&amp;nbsp;is also used as the
-                    name of the tab that is published for that view.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Configuration
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                    &lt;li>
-                        Omit the word &quot;configuration&quot; in the names (it is redundant)
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    The Name field determines the file name used in the file system.&amp;nbsp;
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Role
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Task
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Task names should form a verb object phrase. The verb should be carefully chosen to ensure that the
-                    action to be performed is clear to the practitioner. For a list of acceptable verbs, see the
-                    &quot;Acceptable Verbs&quot; table in a later section.&amp;nbsp; The object should be closely related to the output
-                    work product.
-                &lt;/p>
-                &lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>
-                    &lt;p>
-                        For example:&amp;nbsp; Define Test Specification&lt;br />
-                        &quot;Define&quot; is the verb and means &quot;to determine the essential qualities&quot;. (see Table 2). &quot;Test
-                        Specification&quot; is the main output work product for the task.
-                    &lt;/p>
-                &lt;/blockquote>
-                &lt;p dir=&quot;ltr&quot;>
-                    Alternatively, the task name may reflect the objective of performing the task, instead of being closely
-                    related to the output work product.
-                &lt;/p>
-                &lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>
-                    &lt;p dir=&quot;ltr&quot;>
-                        For example: Plan the Project.
-                    &lt;/p>
-                &lt;/blockquote>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Work product: Artifact
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Work product: Deliverable
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Work product: Outcome
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Guidance
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Capability pattern
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;br />
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                Delivery process
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-    &lt;/tbody>
-&lt;/table>&lt;br />
-&lt;br />
-&lt;h4>
-    Acceptable verbs
-&lt;/h4>
-&lt;p>
-    Table 2 provides a starter set of verbs. Method authors may add verbs but they should do so in such a way that avoids
-    duplication. If a new verb is created, ensure that the definition of what it means is included in the configuration.
-&lt;/p>
-&lt;p>
-    &lt;strong>Table 2: Acceptable Verbs&lt;/strong>&lt;br />
-&lt;/p>
-&lt;table id=&quot;table4&quot; border=&quot;1&quot; width=&quot;100%&quot;>
-    &lt;tbody>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Verb&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;60%&quot;>
-                &lt;strong>Meaning&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Comments&lt;/strong>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Acquire
-            &lt;/td>
-            &lt;td>
-                To come into possession of
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Analyze
-            &lt;/td>
-            &lt;td>
-                To determine the relationship of component parts
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Assemble
-            &lt;/td>
-            &lt;td>
-                To fit parts together
-            &lt;/td>
-            &lt;td>
-                Especially useful for deliverables
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Assess
-            &lt;/td>
-            &lt;td>
-                To make a judgment of worth
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Assign
-            &lt;/td>
-            &lt;td>
-                To appoint to a post or duty
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Build
-            &lt;/td>
-            &lt;td>
-                To construct by putting parts or materials together
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Capture
-            &lt;/td>
-            &lt;td>
-                To document
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Categorize
-            &lt;/td>
-            &lt;td>
-                To analyze and group according to a particular criteria
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Cleanse
-            &lt;/td>
-            &lt;td>
-                To purify
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Communicate
-            &lt;/td>
-            &lt;td>
-                To transmit information so that it is understood
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Conduct
-            &lt;/td>
-            &lt;td>
-                To direct or manage
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Configure
-            &lt;/td>
-            &lt;td>
-                To set up for operation
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Confirm
-            &lt;/td>
-            &lt;td>
-                To verify that you have what's needed
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Detail
-            &lt;/td>
-            &lt;td>
-                To provide the details for an outlined artifact
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Develop
-            &lt;/td>
-            &lt;td>
-                To bring to maturity;&amp;nbsp; to provide a more specific definition
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Elicit
-            &lt;/td>
-            &lt;td>
-                To draw out or evoke
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Enable
-            &lt;/td>
-            &lt;td>
-                To make operational
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Estimate
-            &lt;/td>
-            &lt;td>
-                To judge approximate value
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Evaluate
-            &lt;/td>
-            &lt;td>
-                To determine significance or worth
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Gather
-            &lt;/td>
-            &lt;td>
-                To bring together into one collection
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Gather
-            &lt;/td>
-            &lt;td>
-                To locate and bring together
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Identify
-            &lt;/td>
-            &lt;td>
-                To establish identity
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Implement
-            &lt;/td>
-            &lt;td>
-                To fulfill; to realize
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Initiate
-            &lt;/td>
-            &lt;td>
-                To facilitate the beginning
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Install
-            &lt;/td>
-            &lt;td>
-                To place in position of use
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Manage
-            &lt;/td>
-            &lt;td>
-                To direct or supervise
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Obtain
-            &lt;/td>
-            &lt;td>
-                To get or attain by planned action or effort
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Outline
-            &lt;/td>
-            &lt;td>
-                To describe key elements
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Perform
-            &lt;/td>
-            &lt;td>
-                To do
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Plan
-            &lt;/td>
-            &lt;td>
-                To describe objectives, as well as a sequence and deadline for reaching a goal; to specify how to reach a
-                goal
-            &lt;/td>
-            &lt;td>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Prepare
-            &lt;/td>
-            &lt;td>
-                To make ready
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Prioritize
-            &lt;/td>
-            &lt;td>
-                To set priorities
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Receive
-            &lt;/td>
-            &lt;td>
-                To &lt;span
-                style=&quot;FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA&quot;>acquire,
-                come into possession&lt;/span>
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Reconcile
-            &lt;/td>
-            &lt;td>
-                To check against another for accuracy and make them match
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Release
-            &lt;/td>
-            &lt;td>
-                To make available for use
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Review
-            &lt;/td>
-            &lt;td>
-                To examine carefully, looking for errors, omissions, ambiguity, inconsistency&amp;nbsp;&amp;nbsp;
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Run
-            &lt;/td>
-            &lt;td>
-                To perform, generally by executing a program on a computer
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Select
-            &lt;/td>
-            &lt;td>
-                To choose
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Specify
-            &lt;/td>
-            &lt;td>
-                To name or state explicitly or in detail
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Ship
-            &lt;/td>
-            &lt;td>
-                To transport an item
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Train
-            &lt;/td>
-            &lt;td>
-                To teach a task or job
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Understand
-            &lt;/td>
-            &lt;td>
-                To comprehend meaning
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Validate
-            &lt;/td>
-            &lt;td>
-                To confirm that a solution or process is correct
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td>
-                Verify
-            &lt;/td>
-            &lt;td>
-                To ensure correctness according to specific criteria
-            &lt;/td>
-            &lt;td>
-                &amp;nbsp;
-            &lt;/td>
-        &lt;/tr>
-    &lt;/tbody>
-&lt;/table>&lt;br />
-&lt;br />
-Do not use &lt;em>leverage&lt;/em> because it is marketing jargon and also outdated jargon. We avoid jargon because it always
-becomes outdated and doesn't translate accurately.&lt;br />
-&lt;br />
-&lt;h4>
-    Naming method variants
-&lt;/h4>
-&lt;p>
-    This section provides specific recommendations on how to name elements that have a variability relationship to another
-    element.
-&lt;/p>
-&lt;p>
-    The following table provides guidance about naming specific variants.
-&lt;/p>
-&lt;table id=&quot;table3&quot; border=&quot;1&quot;>
-    &lt;tbody>
-        &lt;tr align=&quot;middle&quot;>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Element&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;25%&quot;>
-                &lt;strong>Guideline&lt;/strong>
-            &lt;/td>
-            &lt;td width=&quot;55%&quot;>
-                &lt;strong>Reason&lt;/strong>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Base element&lt;/strong>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation Name field&amp;nbsp;
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Contributor&lt;/strong>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field 
-                        &lt;ul>
-                            &lt;li>
-                                use exactly the same name as the element to which the contribution is being made
-                            &lt;/li>
-                            &lt;li>
-                                add a suffix that identifies the plug-in providing the contribution
-                            &lt;/li>
-                            &lt;li>
-                                if there are multiple contributions to the same element from different packages in the same
-                                plug-in, it may also be necessary to identify the content package in the suffix
-                            &lt;/li>
-                            &lt;li>
-                                the suffix should be distinct from the name. Use a period (.) to separate a suffix from the
-                                name&lt;br />
-                            &lt;/li>
-                        &lt;/ul>
-                    &lt;/li>
-                    &lt;li>
-                        leave&amp;nbsp;Presentation Name field blank (it is inherited)
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    Do not specify a presentation name for contributing elements because&amp;nbsp;it is inherited from the base
-                    element.
-                &lt;/p>
-                &lt;p>
-                    The Method Composer tool often provides an indication of the variability type, the content element
-                    affected and the plug-in containing the content element affected. It does not do so everywhere,
-                    especially in search dialogs. Thus, it is recommended to use the same name as the base as the first
-                    part of the name and then include a post-fix to help clarify the plug-in or content package that
-                    contains the variant.
-                &lt;/p>
-                &lt;p>
-                    To aid in distinguishing between different contributors and the base element, it is a good idea to name
-                    contributors differently from the base element.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Replacement&lt;/strong>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul class=&quot;noindent&quot;>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation name field
-                    &lt;/li>
-                &lt;/ul>
-                &lt;p>
-                    Note:&amp;nbsp; If the presentation name of the replacement is identical to the element that it replaces,
-                    then follow the naming convention for naming a contributor.
-                &lt;/p>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                A &lt;em>replacing element&lt;/em> replaces the original and results in a new element; therefore, follow the
-                conventions for naming a new element. If you are not changing the presentation name, follow the naming
-                convention for naming a contributor.
-            &lt;/td>
-        &lt;/tr>
-        &lt;tr>
-            &lt;td width=&quot;20%&quot;>
-                &lt;strong>Extension&lt;/strong>
-            &lt;/td>
-            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>
-                &lt;ul>
-                    &lt;li>
-                        use internal name&amp;nbsp;for the Name field
-                    &lt;/li>
-                    &lt;li>
-                        use friendly name&amp;nbsp;for the Presentation Name field
-                    &lt;/li>
-                &lt;/ul>
-            &lt;/td>
-            &lt;td width=&quot;50%&quot;>
-                &lt;p>
-                    An extending element is a new element.&amp;nbsp; Thus, the name of an extending element should be different
-                    from the element being extended.
-                &lt;/p>
-            &lt;/td>
-        &lt;/tr>
-    &lt;/tbody>
-&lt;/table>
-&lt;h4>
-    UMF naming conventions
-&lt;/h4>
-&lt;p>
-    The Unified Method Framework (UMF)&amp;nbsp;defines a naming convention for each library element: &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html&quot;
-    guid=&quot;_D4TLgMaGEduMlb2cQZNTYw&quot;>method plug-in&lt;/a>s, &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html&quot;
-    guid=&quot;__V7pAMaEEduMlb2cQZNTYw&quot;>method configuration&lt;/a>s, plug-in projects, configuration projects and tag groups.
-&lt;/p>
-&lt;p>
-    The UMF naming convention divides the element names into name parts, where each name part is separated by a dot
-    (‘.').&amp;nbsp;For example, the plug-in name &quot;core.tech.com.base&quot; has&amp;nbsp;four name parts.
-&lt;/p>
-&lt;p>
-    The benefits of UMF's naming convention is that it takes advantage of Method Composer support for a hierarchical
-    library view where a new level is introduced for each name part. The resulting hierarchy is defined to optimize
-    configuration of the method.&amp;nbsp;The most important categorization for someone configuring the process is listed
-    first: the plug-in or configuration type.&amp;nbsp; Licensing level is applied as a suffix and no suffix means open source
-    (in other words, open source method elements do not have a licensing level suffix).
-&lt;/p>
-&lt;h5>
-    UMF plug-in naming conventions
-&lt;/h5>
-&lt;p>
-    UMF plug-in naming convention: &amp;lt;&lt;strong>plug-in
-    type&lt;/strong>&amp;gt;.[&amp;lt;&lt;strong>context&lt;/strong>&amp;gt;].&amp;lt;&lt;strong>descriptive name&lt;/strong>&amp;gt;.&amp;lt;&lt;strong>plug-in
-    part&lt;/strong>&amp;gt;[_&amp;lt;&lt;strong>part qualifier&lt;/strong>&amp;gt;][-&amp;lt;&lt;strong>source/licensing level&lt;/strong>&amp;gt;]
-&lt;/p>
-&lt;p>
-    Where:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        &lt;strong>Plug-in type&lt;/strong>:&amp;nbsp; The following are the possible values for the plug-in type.&amp;nbsp; For more
-        information on the plug-in types, see [Concept: Practice Library Plug-In Types]. 
-        &lt;ul>
-            &lt;li>
-                core = Core
-            &lt;/li>
-            &lt;li>
-                practice = Practice
-            &lt;/li>
-            &lt;li>
-                process = Process
-            &lt;/li>
-            &lt;li>
-                publish = Publish
-            &lt;/li>
-            &lt;li>
-                meth_mgmt = Method Management
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-&lt;/ul>
-&lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>
-    &lt;br />
-&lt;/blockquote>
-&lt;ul>
-    &lt;li>
-        &lt;strong>Context&lt;/strong>: Not required (some plug-ins are &quot;context-free&quot; meaning that they are not specific to any
-        context).&amp;nbsp;&amp;nbsp;The following are some examples of contexts:&amp;nbsp; 
-        &lt;ul>
-            &lt;li>
-                gen = general purpose (&lt;em>general purpose&lt;/em> means applies across multiple contexts.&amp;nbsp; This is NOT
-                the same as context-free)
-            &lt;/li>
-            &lt;li>
-                tech = technology
-            &lt;/li>
-            &lt;li>
-                bus = business
-            &lt;/li>
-            &lt;li>
-                mgmt = management
-            &lt;/li>
-            &lt;li>
-                legacy = legacy
-            &lt;/li>
-            &lt;li>
-                mdev&amp;nbsp;= method development&amp;nbsp;
-            &lt;/li>
-            &lt;li>
-                sdpl = solution deployment
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-&lt;/ul>
-&lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>
-    &lt;p>
-        Note: If you would like to implement &quot;nested&quot; contexts, you can break the context name into multiple &quot;parts&quot;, where
-        each of those parts are separated by a dot (period) so that Method Composer creates a hierarchical view of the
-        related plug-ins. For example: You could define an authoring&amp;nbsp;(auth)&amp;nbsp;context that is a sub-context of
-        method development (mdev).&amp;nbsp;In such a case,&amp;nbsp;the name of the context would be
-        &quot;mdev.auth&quot;.&amp;nbsp;&amp;nbsp;&amp;nbsp;
-    &lt;/p>
-&lt;/blockquote>
-&lt;ul>
-    &lt;li>
-        &lt;strong>Descriptive name&lt;/strong>: The following conventions apply to the Descriptive name part of of a plug-in
-        name:
-    &lt;/li>
-    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>
-        &lt;ul>
-            &lt;li>
-                Actual names will vary, but the name should be descriptive of what the plug-in contains, should be pretty
-                close to the presentation name for the plug-in, using UMF Approved Acronyms.&amp;nbsp;&amp;nbsp;
-            &lt;/li>
-            &lt;li>
-                For example:&amp;nbsp;Descriptive name:&amp;nbsp;practice_auth;&amp;nbsp;Presentation name: Practice Authoring.&lt;br />
-                &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Plug-in part&lt;/strong>: The following are the possible values for the plug-in part.&amp;nbsp; For more
-        information on the plug-in parts, see [Concept: Practice Library Plug-In Types]. 
-        &lt;ul>
-            &lt;li>
-                base = base plug-in
-            &lt;/li>
-            &lt;li>
-                assign = assign plug-in
-            &lt;/li>
-            &lt;li>
-                extend = extend plug-in&lt;br />
-                &amp;nbsp;&amp;nbsp;&amp;nbsp;
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Part qualifier&lt;/strong>: Not required. This can be used to provide some additional information about the
-        plug-in part.&amp;nbsp; This is most applicable for Extend plug-ins, where the part qualifier can be used to indicate
-        the reason for the extension.&amp;nbsp; For example, UMF-specific extensions to an existing plug-in may be indicated
-        with a &quot;_umf&quot; part qualifier (e.g., &quot;&amp;lt;some plug-in&amp;gt;.extend_umf&quot;).&amp;nbsp;&amp;nbsp; Another example of a qualifier
-        is &quot;gbl&quot; for globalization&quot;.&lt;br />
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Source/licensing level suffix&lt;/strong>.&amp;nbsp; Can be used to indicate the company that the plug-in applies
-        to and/or the licensing level of the plug-in. Open source plug-ins do not include a licensing level in their
-        names.&lt;br />
-        Note: The use of a hyphen (-) rather than a dot or period (.) is intentional because the
-        source/licensing&amp;nbsp;level&amp;nbsp;is not intended to be another hierarchical level.&amp;nbsp; Do no use a hyphen in any
-        other place in the name&amp;nbsp;except to separate the actual plug-in name from the suffix.
-    &lt;/li>
-&lt;/ul>
-&lt;p>
-    Figure 1 provides examples of UMF plug-in names that use these conventions:
-&lt;/p>
-&lt;p>
-    Figure 1: Example: Method authoring practice naming conventions
-&lt;/p>
-&lt;p>
-    &lt;img style=&quot;WIDTH: 685px; HEIGHT: 514px&quot; alt=&quot;umf_plugin_name_examples&quot; src=&quot;resources/umf_plugin_name_examples.jpg&quot;
-    width=&quot;600&quot; height=&quot;514&quot; />
-&lt;/p>
-&lt;p>
-    Notice the following points shown in Figure 1:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        All practices are grouped together because the first part of their names is &quot;practice&quot;
-    &lt;/li>
-    &lt;li>
-        All the practices that support a specific context are grouped under the content name (&quot;mdev&quot; in this example)
-    &lt;/li>
-    &lt;li>
-        All plug-ins that support method authoring are grouped together because a new name level was introduced in the
-        descriptive name (&quot;auth&quot; in this example)
-    &lt;/li>
-    &lt;li>
-        All plug-in &quot;parts&quot; for a practice are grouped together because the practice descriptive name is the same
-    &lt;/li>
-    &lt;li>
-        The reason for the extension is included as part of the Extend plug-in name, separated from the word &quot;extend&quot; with
-        an underscore and not a&amp;nbsp;hyphen. For example: practice.mdev.auth.practice_auth.extend_umf and
-        practice.mdev.auth.practice_auth.extend_umf-ibm
-    &lt;/li>
-    &lt;li>
-        The licensing level is separated from the rest of the plug-in name with a hyphen.&amp;nbsp; For example:
-        practice.mdev.auth.practice_auth.extend_umf-ibm and practice.mdev.auth.practice_auth.extend_umf-ibm_int.
-    &lt;/li>
-&lt;/ul>
-&lt;h5>
-    UMF plug-in project naming conventions
-&lt;/h5>
-&lt;p>
-    Plug-in projects should be named exactly the same as the plug-ins they contain. See the earlier section on plug-in
-    naming conventions for more information.
-&lt;/p>
-&lt;h5>
-    UMF configuration naming conventions
-&lt;/h5>
-&lt;p>
-    UMF configuration naming convention: &amp;lt;&lt;strong>configuration
-    type&lt;/strong>&amp;gt;[.&lt;strong>context&lt;/strong>].&amp;lt;&lt;strong>descriptive name&amp;gt;[-&amp;lt;source/licensing level&amp;gt;]&lt;/strong>
-&lt;/p>
-&lt;p>
-    Where:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        &lt;strong>Configuration type&lt;/strong>: The following are the possible values for the&amp;nbsp;configuration
-        type.&amp;nbsp;For more information on UMF configuration types, see [Concept: Practice Library Configuration Types]. 
-        &lt;ul>
-            &lt;li>
-                publish = Publish Configuration
-            &lt;/li>
-            &lt;li>
-                zconstruct = Process Construction Configuration&lt;br />
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Context&lt;/strong>: Same as for plug-ins.&lt;br />
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Descriptive name&lt;/strong>: The following conventions apply to the Descriptive name part of of a
-        configuration name:&amp;nbsp;&amp;nbsp; 
-        &lt;ul>
-            &lt;li>
-                For Publish configurations, the Practice Configuration&amp;nbsp;name being published&amp;nbsp;makes a&amp;nbsp;good
-                descriptive name
-            &lt;/li>
-            &lt;li>
-                For Process Construction configurations, the name of the plug-in that contains the process makes a good
-                descriptive name&lt;br />
-            &lt;/li>
-        &lt;/ul>
-    &lt;/li>
-    &lt;li>
-        &lt;strong>Source/licensing level&lt;/strong>: Same as for plug-ins.
-    &lt;/li>
-&lt;/ul>
-&lt;p>
-    The following are some examples of UMF&amp;nbsp;configuration names that use these conventions:
-&lt;/p>
-&lt;p>
-    Figure&amp;nbsp;2 provides an&amp;nbsp;example of UMF configuration names that use these conventions.
-&lt;/p>
-&lt;p>
-    Figure 2: Example: UMF configuration naming conventions
-&lt;/p>
-&lt;p>
-    &lt;img alt=&quot;umf_config_name_examples&quot; src=&quot;resources/umf_config_name_examples.jpg&quot; width=&quot;600&quot; height=&quot;465&quot; />
-&lt;/p>
-&lt;p>
-    Notice the following points shown in Figure 2:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        All configurations of the same type are grouped together because the first part of the configuration name is the
-        configuration type
-    &lt;/li>
-    &lt;li>
-        All configurations that support a specific context are grouped under the content name (&quot;mdev&quot; in this example)
-    &lt;/li>
-    &lt;li>
-        The publish configurations for a specific configurations are easy to spot because the configuration name is in the
-        descriptive name
-    &lt;/li>
-    &lt;li>
-        The configuration to be used as the default configuration when constructing a process in a plug-in is easy to spot
-        because the owning plug-in name is in the descriptive name
-    &lt;/li>
-    &lt;li>
-        The unique identifier suffix is used to indicate the licensing level of the configurations (e.g., -ibm for
-        commercial content and -ibm_int for internal IBM content)
-    &lt;/li>
-&lt;/ul>
-&lt;h5>
-    UMF configuration project naming conventions
-&lt;/h5>
-&lt;p>
-    UMF configuration project naming convention: &lt;strong>configs[-&lt;/strong>&amp;lt;&lt;strong>descriptive
-    name&amp;gt;][-&amp;lt;source/licensing level&amp;gt;]&lt;/strong>
-&lt;/p>
-&lt;p>
-    Where:
-&lt;/p>
-&lt;p>
-    Descriptive name: This is optional (i.e., you may only have one tag group per licensing level).&amp;nbsp; If you use one,
-    the descriptive name should be a name that represents a specific set or category of configurations.&amp;nbsp; For example:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        mdev: Method Development
-    &lt;/li>
-    &lt;li>
-        mdev.auth: Method authoring (s sub set of method development)
-    &lt;/li>
-    &lt;li>
-        mdev.meth_mgmt: Method Development Method Management
-    &lt;/li>
-&lt;/ul>
-&lt;p>
-    Source/licensing level: Same as for plug-ins.
-&lt;/p>
-&lt;p>
-    Figure&amp;nbsp;3 provides some examples of UMF&amp;nbsp;configuration project names that use these conventions.
-&lt;/p>
-&lt;p>
-    Figure 3: Example: UMF configuration project naming conventions
-&lt;/p>
-&lt;p>
-    &lt;img style=&quot;WIDTH: 682px; HEIGHT: 537px&quot; alt=&quot;umf_config_proj_name_examples&quot;
-    src=&quot;resources/umf_config_proj_name_examples.jpg&quot; width=&quot;600&quot; height=&quot;537&quot; />
-&lt;/p>
-&lt;h5>
-    UMF tag group naming conventions
-&lt;/h5>
-&lt;p>
-    UMF tag group naming convention: &lt;strong>tags-&lt;/strong>&amp;lt;&lt;strong>descriptive name&amp;gt;[-&amp;lt;source/licensing
-    level&amp;gt;]&lt;/strong>
-&lt;/p>
-&lt;p>
-    Where:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        Descriptive name: A name that represents a specific set or category of tags.&amp;nbsp; For example: mdev: Method
-        Development
-    &lt;/li>
-    &lt;li>
-        Source/licensing level: Same as for plug-ins.
-    &lt;/li>
-&lt;/ul>
-&lt;p>
-    Figure&amp;nbsp;4 provides some examples of UMF&amp;nbsp;tag group names that use these conventions.
-&lt;/p>
-&lt;p>
-    Figure 4: Example: UMF tag group naming conventions
-&lt;/p>
-&lt;p>
-    &lt;img alt=&quot;umf_tag_group_name_examples&quot; src=&quot;resources/umf_tag_group_name_examples.jpg&quot; width=&quot;124&quot; height=&quot;39&quot; />
-&lt;/p>
-&lt;h4>
-    IBM Licensing Levels
-&lt;/h4>
-&lt;p>
-    The following are the unique identifiers being used for elements defined at the commercial level and above (they
-    reflect the UMF Licensing Levels:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        ibm = part of IBM's commercial methods (licensing level =&amp;nbsp; commercial)
-    &lt;/li>
-    &lt;li>
-        ibm_int = part of IBM's internal methods (licensing level =&amp;nbsp; internal)
-    &lt;/li>
-    &lt;li>
-        ibm_lic = part of IBM's licensable methods (licensing level = licensable)
-    &lt;/li>
-    &lt;li>
-        ibm_prp = part of IBM's licensable methods (licensing level = proprietary)&amp;nbsp;&lt;br />
-    &lt;/li>
-&lt;/ul>
-&lt;h3>
-    Writing Brief Descriptions
-&lt;/h3>
-&lt;p>
-    In general, all non-contributing method elements&amp;nbsp;need a brief description. A brief description provides a one or
-    two sentence description of what the element is (in other words, what content the element contains).
-&lt;/p>
-&lt;p>
-    Brief descriptions should be written at the time the element is identified.&amp;nbsp;A well-written description is
-    important because if you find it hard to describe what an element is, it may not be a good element
-&lt;/p>
-&lt;p>
-    Follow these guidelines when developing method element brief descriptions:
-&lt;/p>
-&lt;ul>
-    &lt;li>
-        Do not include presentation names in brief descriptions because that makes it harder to change the presentation
-        name. Instead, refer to &quot;this &amp;lt;element type&amp;gt;&quot;, where &amp;lt;element type&amp;gt; is the type of method element. For
-        example, &quot;this role&quot;... or &quot;this guidance&quot;.
-    &lt;/li>
-    &lt;li>
-        Do not state the obvious. The brief description should not just repeat what can be understood from the element type
-        and the presentation name. For example, for Concept: Pattern, don't just say, &quot;This concept describes what a
-        Pattern is&quot;.&amp;nbsp;Such information does not provide any value.&amp;nbsp;Instead,&amp;nbsp;provide a one or two sentence
-        summary of what the element contains.&amp;nbsp;For example, &quot;This concept describes&amp;nbsp;s generalized solution that
-        can be implemented and applied in a problem situation (a context) and thereby eliminate one or more of the inherent
-        problems.&quot;
-    &lt;/li>
-    &lt;li>
-        Avoid repeating the brief description in other fields of the method element. If there is nothing more to add to
-        what is in the brief description, then omit the other description fields.
-    &lt;/li>
-    &lt;li>
-        Make sure that there is a period at the end of the brief description.
-    &lt;/li>
-    &lt;li>
-        Check for general spelling and spacing errors.
-    &lt;/li>
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-UMwO0Odv_iQVxPV40lG2kA" name="new_guideline,__I8S0D2kEd-lU6YVR9_PJQ" guid="-UMwO0Odv_iQVxPV40lG2kA" changeDate="2011-07-05T15:55:53.599-0700" version="7.5.0">
+  <mainDescription>&lt;h3>&#xD;
+    General Naming Conventions&#xD;
+&lt;/h3>&#xD;
+&lt;p>&#xD;
+    This guidance provides general information on naming method elements.&amp;nbsp; For method element-specific naming&#xD;
+    guidance, see the attached guidance.&#xD;
+&lt;/p>&#xD;
+&lt;h5>&#xD;
+    Abbreviations&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    It is a good practice is to provide a list of approved abbreviations for your project.&amp;nbsp;Using a standard set of&#xD;
+    abbreviations simplifies searches for not only the method authoring team, but also for users of your published web&#xD;
+    site.&#xD;
+&lt;/p>&#xD;
+&lt;h4>&#xD;
+    Name fields&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    Most method elements have two name fields:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        The&amp;nbsp;&lt;strong>Name&lt;/strong> is always present since it is the internal name&amp;nbsp;for the element.&lt;br />&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The &lt;strong>Presentation Name&lt;/strong> is present for some elements; it is the name&amp;nbsp;displayed in the published&#xD;
+        web site for the element. Thus, a friendly name&amp;nbsp;should be used.&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;h4>&#xD;
+    General naming guidelines&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    In general, all method elements should following the following recommendations:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        Name should reflect the essence of the element&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Where an element has both a name and a Presentation Name field, try to name them consistently (though abbreviations&#xD;
+        may be used in the internal name)&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Abbreviations should be either very common to the plug-in domain (for example, J2EE for Java 2 Enterprise Edition)&#xD;
+        or they should be taken out of a list of common abbreviations for the project. If abbreviations are not&#xD;
+        standardized, it is very likely that similar but not quite identical abbreviations will occur here and there,&#xD;
+        introducing confusion and errors later on&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;p>&#xD;
+    For general guidelines on naming variants, see the section on that topic later in this guideline.&lt;br />&#xD;
+&lt;/p>&#xD;
+&lt;h4>&#xD;
+    Method element-specific naming guidelines&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    Table 1 provides element-specific guidelines for naming the different types of method elements.&amp;nbsp;&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    &lt;strong>Table 1: Method Element Naming Conventions&lt;/strong>&lt;br />&#xD;
+    &lt;br />&#xD;
+&lt;/p>&#xD;
+&lt;table id=&quot;table3&quot; border=&quot;1&quot;>&#xD;
+    &lt;tbody>&#xD;
+        &lt;tr align=&quot;middle&quot;>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Element&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;25%&quot;>&#xD;
+                &lt;strong>Guideline&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;55%&quot;>&#xD;
+                &lt;strong>Reason&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Plug-in&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use&amp;nbsp; internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        Omit the word &quot;plug-in&quot; in the names (it is redundant)&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    The value&amp;nbsp;of the&amp;nbsp;Name field determines the directory name used in the file&#xD;
+                    system.&amp;nbsp;&amp;nbsp;&#xD;
+                &lt;/p>&#xD;
+                &lt;p>&#xD;
+                    Compound names, separated by periods, can be used in the Name field to organize the list of plug-ins in&#xD;
+                    the library view to make them easier to navigate for process authors.&amp;nbsp;&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Method content package&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use&amp;nbsp; internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Method content package names are displayed when viewing the method library. They are also the elements&#xD;
+                    that users can choose to include or exclude from their configurations. Thus, these names need to be&#xD;
+                    easy to understand and&amp;nbsp;self-explanatory.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Process package&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;friendly name&amp;nbsp;for Name field (process&amp;nbsp;packages only have a single&#xD;
+                        name field)&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Process package names are displayed when viewing the method library. They are also the elements that&#xD;
+                    users can choose to include or exclude from their configurations. Thus, these names should be easy to&#xD;
+                    understand and&amp;nbsp;self-explanatory.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Standard category&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul class=&quot;noindent&quot;>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Standard Category names are displayed when viewing the method library. They are also the elements that&#xD;
+                    users can choose to include or exclude from their configurations, as well as to include or exclude from&#xD;
+                    other custom categories. Thus, these names should be easy to understand and&amp;nbsp;self-explanatory.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Custom category&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul class=&quot;noindent&quot;>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+                &lt;p>&#xD;
+                    If the custom category is to be used for a navigation view, include &quot;view&quot; in both name fields.&amp;nbsp;&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Custom Category names are displayed when viewing the method library. They are also the elements that&#xD;
+                    users can choose to include or exclude from their configurations, as well as to include or exclude from&#xD;
+                    other custom categories. Thus, these names should be easy to understand and&amp;nbsp;self-explanatory.&#xD;
+                &lt;/p>&#xD;
+                &lt;p>&#xD;
+                    The Presentation name of a custom category that is used as a navigation view&amp;nbsp;is also used as the&#xD;
+                    name of the tab that is published for that view.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Configuration&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        Omit the word &quot;configuration&quot; in the names (it is redundant)&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    The Name field determines the file name used in the file system.&amp;nbsp;&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Role&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Task&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Task names should form a verb object phrase. The verb should be carefully chosen to ensure that the&#xD;
+                    action to be performed is clear to the practitioner. For a list of acceptable verbs, see the&#xD;
+                    &quot;Acceptable Verbs&quot; table in a later section.&amp;nbsp; The object should be closely related to the output&#xD;
+                    work product.&#xD;
+                &lt;/p>&#xD;
+                &lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
+                    &lt;p>&#xD;
+                        For example:&amp;nbsp; Define Test Specification&lt;br />&#xD;
+                        &quot;Define&quot; is the verb and means &quot;to determine the essential qualities&quot;. (see Table 2). &quot;Test&#xD;
+                        Specification&quot; is the main output work product for the task.&#xD;
+                    &lt;/p>&#xD;
+                &lt;/blockquote>&#xD;
+                &lt;p dir=&quot;ltr&quot;>&#xD;
+                    Alternatively, the task name may reflect the objective of performing the task, instead of being closely&#xD;
+                    related to the output work product.&#xD;
+                &lt;/p>&#xD;
+                &lt;blockquote style=&quot;MARGIN-RIGHT: 0px&quot; dir=&quot;ltr&quot;>&#xD;
+                    &lt;p dir=&quot;ltr&quot;>&#xD;
+                        For example: Plan the Project.&#xD;
+                    &lt;/p>&#xD;
+                &lt;/blockquote>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Work product: Artifact&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Work product: Deliverable&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Work product: Outcome&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Guidance&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Capability pattern&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;br />&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                Delivery process&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+    &lt;/tbody>&#xD;
+&lt;/table>&lt;br />&#xD;
+&lt;br />&#xD;
+&lt;h4>&#xD;
+    Acceptable verbs&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    Table 2 provides a starter set of verbs. Method authors may add verbs but they should do so in such a way that avoids&#xD;
+    duplication. If a new verb is created, ensure that the definition of what it means is included in the configuration.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    &lt;strong>Table 2: Acceptable Verbs&lt;/strong>&lt;br />&#xD;
+&lt;/p>&#xD;
+&lt;table id=&quot;table4&quot; border=&quot;1&quot; width=&quot;100%&quot;>&#xD;
+    &lt;tbody>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Verb&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;60%&quot;>&#xD;
+                &lt;strong>Meaning&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Comments&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Acquire&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To come into possession of&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Analyze&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To determine the relationship of component parts&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Assemble&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To fit parts together&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                Especially useful for deliverables&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Assess&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To make a judgment of worth&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Assign&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To appoint to a post or duty&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Build&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To construct by putting parts or materials together&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Capture&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To document&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Categorize&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To analyze and group according to a particular criteria&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Cleanse&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To purify&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Communicate&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To transmit information so that it is understood&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Conduct&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To direct or manage&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Configure&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To set up for operation&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Confirm&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To verify that you have what's needed&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Detail&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To provide the details for an outlined artifact&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Develop&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To bring to maturity;&amp;nbsp; to provide a more specific definition&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Elicit&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To draw out or evoke&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Enable&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To make operational&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Estimate&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To judge approximate value&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Evaluate&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To determine significance or worth&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Gather&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To bring together into one collection&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Gather&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To locate and bring together&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Identify&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To establish identity&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Implement&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To fulfill; to realize&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Initiate&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To facilitate the beginning&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Install&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To place in position of use&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Manage&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To direct or supervise&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Obtain&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To get or attain by planned action or effort&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Outline&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To describe key elements&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Perform&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To do&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Plan&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To describe objectives, as well as a sequence and deadline for reaching a goal; to specify how to reach a&#xD;
+                goal&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Prepare&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To make ready&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Prioritize&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To set priorities&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Receive&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To &lt;span&#xD;
+                style=&quot;FONT-FAMILY: Arial; FONT-SIZE: 10pt; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA&quot;>acquire,&#xD;
+                come into possession&lt;/span>&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Reconcile&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To check against another for accuracy and make them match&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Release&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To make available for use&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Review&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To examine carefully, looking for errors, omissions, ambiguity, inconsistency&amp;nbsp;&amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Run&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To perform, generally by executing a program on a computer&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Select&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To choose&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Specify&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To name or state explicitly or in detail&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Ship&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To transport an item&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Train&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To teach a task or job&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Understand&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To comprehend meaning&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Validate&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To confirm that a solution or process is correct&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td>&#xD;
+                Verify&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                To ensure correctness according to specific criteria&#xD;
+            &lt;/td>&#xD;
+            &lt;td>&#xD;
+                &amp;nbsp;&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+    &lt;/tbody>&#xD;
+&lt;/table>&lt;br />&#xD;
+&lt;br />&#xD;
+Do not use &lt;em>leverage&lt;/em> because it is marketing jargon and also outdated jargon. We avoid jargon because it always&#xD;
+becomes outdated and doesn't translate accurately.&lt;br />&#xD;
+&lt;br />&#xD;
+&lt;h4>&#xD;
+    Naming method variants&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    This section provides specific recommendations on how to name elements that have a variability relationship to another&#xD;
+    element.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    The following table provides guidance about naming specific variants.&#xD;
+&lt;/p>&#xD;
+&lt;table id=&quot;table3&quot; border=&quot;1&quot;>&#xD;
+    &lt;tbody>&#xD;
+        &lt;tr align=&quot;middle&quot;>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Element&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;25%&quot;>&#xD;
+                &lt;strong>Guideline&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;55%&quot;>&#xD;
+                &lt;strong>Reason&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Base element&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation Name field&amp;nbsp;&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Contributor&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field &#xD;
+                        &lt;ul>&#xD;
+                            &lt;li>&#xD;
+                                use exactly the same name as the element to which the contribution is being made&#xD;
+                            &lt;/li>&#xD;
+                            &lt;li>&#xD;
+                                add a suffix that identifies the plug-in providing the contribution&#xD;
+                            &lt;/li>&#xD;
+                            &lt;li>&#xD;
+                                if there are multiple contributions to the same element from different packages in the same&#xD;
+                                plug-in, it may also be necessary to identify the content package in the suffix&#xD;
+                            &lt;/li>&#xD;
+                            &lt;li>&#xD;
+                                the suffix should be distinct from the name. Use a period (.) to separate a suffix from the&#xD;
+                                name&lt;br />&#xD;
+                            &lt;/li>&#xD;
+                        &lt;/ul>&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        leave&amp;nbsp;Presentation Name field blank (it is inherited)&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    Do not specify a presentation name for contributing elements because&amp;nbsp;it is inherited from the base&#xD;
+                    element.&#xD;
+                &lt;/p>&#xD;
+                &lt;p>&#xD;
+                    The Method Composer tool often provides an indication of the variability type, the content element&#xD;
+                    affected and the plug-in containing the content element affected. It does not do so everywhere,&#xD;
+                    especially in search dialogs. Thus, it is recommended to use the same name as the base as the first&#xD;
+                    part of the name and then include a post-fix to help clarify the plug-in or content package that&#xD;
+                    contains the variant.&#xD;
+                &lt;/p>&#xD;
+                &lt;p>&#xD;
+                    To aid in distinguishing between different contributors and the base element, it is a good idea to name&#xD;
+                    contributors differently from the base element.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Replacement&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul class=&quot;noindent&quot;>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+                &lt;p>&#xD;
+                    Note:&amp;nbsp; If the presentation name of the replacement is identical to the element that it replaces,&#xD;
+                    then follow the naming convention for naming a contributor.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                A &lt;em>replacing element&lt;/em> replaces the original and results in a new element; therefore, follow the&#xD;
+                conventions for naming a new element. If you are not changing the presentation name, follow the naming&#xD;
+                convention for naming a contributor.&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+        &lt;tr>&#xD;
+            &lt;td width=&quot;20%&quot;>&#xD;
+                &lt;strong>Extension&lt;/strong>&#xD;
+            &lt;/td>&#xD;
+            &lt;td valign=&quot;top&quot; width=&quot;30%&quot;>&#xD;
+                &lt;ul>&#xD;
+                    &lt;li>&#xD;
+                        use internal name&amp;nbsp;for the Name field&#xD;
+                    &lt;/li>&#xD;
+                    &lt;li>&#xD;
+                        use friendly name&amp;nbsp;for the Presentation Name field&#xD;
+                    &lt;/li>&#xD;
+                &lt;/ul>&#xD;
+            &lt;/td>&#xD;
+            &lt;td width=&quot;50%&quot;>&#xD;
+                &lt;p>&#xD;
+                    An extending element is a new element.&amp;nbsp; Thus, the name of an extending element should be different&#xD;
+                    from the element being extended.&#xD;
+                &lt;/p>&#xD;
+            &lt;/td>&#xD;
+        &lt;/tr>&#xD;
+    &lt;/tbody>&#xD;
+&lt;/table>&#xD;
+&lt;h4>&#xD;
+    UMF naming conventions&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    The Unified Method Framework (UMF)&amp;nbsp;defines a naming convention for each library element: &lt;a class=&quot;elementLink&quot;&#xD;
+    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html&quot;&#xD;
+    guid=&quot;_D4TLgMaGEduMlb2cQZNTYw&quot;>method plug-in&lt;/a>s, &lt;a class=&quot;elementLink&quot;&#xD;
+    href=&quot;./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html&quot;&#xD;
+    guid=&quot;__V7pAMaEEduMlb2cQZNTYw&quot;>method configuration&lt;/a>s, plug-in projects, configuration projects and tag groups.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    The UMF naming convention divides the element names into name parts, where each name part is separated by a dot&#xD;
+    (‘.').&amp;nbsp;For example, the plug-in name &quot;core.tech.com.base&quot; has&amp;nbsp;four name parts.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    The benefits of UMF's naming convention is that it takes advantage of Method Composer support for a hierarchical&#xD;
+    library view where a new level is introduced for each name part. The resulting hierarchy is defined to optimize&#xD;
+    configuration of the method.&amp;nbsp;The most important categorization for someone configuring the process is listed&#xD;
+    first: the plug-in or configuration type.&amp;nbsp; Licensing level is applied as a suffix and no suffix means open source&#xD;
+    (in other words, open source method elements do not have a licensing level suffix).&#xD;
+&lt;/p>&#xD;
+&lt;h5>&#xD;
+    UMF plug-in naming conventions&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    UMF plug-in naming convention: &amp;lt;&lt;strong>plug-in&#xD;
+    type&lt;/strong>&amp;gt;.[&amp;lt;&lt;strong>context&lt;/strong>&amp;gt;].&amp;lt;&lt;strong>descriptive name&lt;/strong>&amp;gt;.&amp;lt;&lt;strong>plug-in&#xD;
+    part&lt;/strong>&amp;gt;[_&amp;lt;&lt;strong>part qualifier&lt;/strong>&amp;gt;][-&amp;lt;&lt;strong>source/licensing level&lt;/strong>&amp;gt;]&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Where:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Plug-in type&lt;/strong>:&amp;nbsp; The following are the possible values for the plug-in type.&amp;nbsp; For more&#xD;
+        information on the plug-in types, see [Concept: Practice Library Plug-In Types]. &#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                core = Core&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                practice = Practice&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                process = Process&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                publish = Publish&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                meth_mgmt = Method Management&#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;br />&#xD;
+&lt;/blockquote>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Context&lt;/strong>: Not required (some plug-ins are &quot;context-free&quot; meaning that they are not specific to any&#xD;
+        context).&amp;nbsp;&amp;nbsp;The following are some examples of contexts:&amp;nbsp; &#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                gen = general purpose (&lt;em>general purpose&lt;/em> means applies across multiple contexts.&amp;nbsp; This is NOT&#xD;
+                the same as context-free)&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                tech = technology&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                bus = business&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                mgmt = management&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                legacy = legacy&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                mdev&amp;nbsp;= method development&amp;nbsp;&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                sdpl = solution deployment&#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>&#xD;
+        Note: If you would like to implement &quot;nested&quot; contexts, you can break the context name into multiple &quot;parts&quot;, where&#xD;
+        each of those parts are separated by a dot (period) so that Method Composer creates a hierarchical view of the&#xD;
+        related plug-ins. For example: You could define an authoring&amp;nbsp;(auth)&amp;nbsp;context that is a sub-context of&#xD;
+        method development (mdev).&amp;nbsp;In such a case,&amp;nbsp;the name of the context would be&#xD;
+        &quot;mdev.auth&quot;.&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
+    &lt;/p>&#xD;
+&lt;/blockquote>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Descriptive name&lt;/strong>: The following conventions apply to the Descriptive name part of of a plug-in&#xD;
+        name:&#xD;
+    &lt;/li>&#xD;
+    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                Actual names will vary, but the name should be descriptive of what the plug-in contains, should be pretty&#xD;
+                close to the presentation name for the plug-in, using UMF Approved Acronyms.&amp;nbsp;&amp;nbsp;&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                For example:&amp;nbsp;Descriptive name:&amp;nbsp;practice_auth;&amp;nbsp;Presentation name: Practice Authoring.&lt;br />&#xD;
+                &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
+            &lt;/li>&#xD;
+        &lt;/ul>&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Plug-in part&lt;/strong>: The following are the possible values for the plug-in part.&amp;nbsp; For more&#xD;
+        information on the plug-in parts, see [Concept: Practice Library Plug-In Types]. &#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                base = base plug-in&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                assign = assign plug-in&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                extend = extend plug-in&lt;br />&#xD;
+                &amp;nbsp;&amp;nbsp;&amp;nbsp;&#xD;
+            &lt;/li>&#xD;
+        &lt;/ul>&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Part qualifier&lt;/strong>: Not required. This can be used to provide some additional information about the&#xD;
+        plug-in part.&amp;nbsp; This is most applicable for Extend plug-ins, where the part qualifier can be used to indicate&#xD;
+        the reason for the extension.&amp;nbsp; For example, UMF-specific extensions to an existing plug-in may be indicated&#xD;
+        with a &quot;_umf&quot; part qualifier (e.g., &quot;&amp;lt;some plug-in&amp;gt;.extend_umf&quot;).&amp;nbsp;&amp;nbsp; Another example of a qualifier&#xD;
+        is &quot;gbl&quot; for globalization&quot;.&lt;br />&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Source/licensing level suffix&lt;/strong>.&amp;nbsp; Can be used to indicate the company that the plug-in applies&#xD;
+        to and/or the licensing level of the plug-in. Open source plug-ins do not include a licensing level in their&#xD;
+        names.&lt;br />&#xD;
+        Note: The use of a hyphen (-) rather than a dot or period (.) is intentional because the&#xD;
+        source/licensing&amp;nbsp;level&amp;nbsp;is not intended to be another hierarchical level.&amp;nbsp; Do no use a hyphen in any&#xD;
+        other place in the name&amp;nbsp;except to separate the actual plug-in name from the suffix.&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;p>&#xD;
+    Note the following:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        All practices are grouped together because the first part of their names is &quot;practice&quot;&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        All the practices that support a specific context are grouped under the content name&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        All plug-in &quot;parts&quot; for a practice are grouped together because the practice descriptive name is the same&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The reason for the extension is included as part of the Extend plug-in name, separated from the word &quot;extend&quot; with&#xD;
+        an underscore and not a&amp;nbsp;hyphen.&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The licensing level is separated from the rest of the plug-in name with a hyphen.&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;h5>&#xD;
+    UMF plug-in project naming conventions&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    Plug-in projects should be named exactly the same as the plug-ins they contain. See the earlier section on plug-in&#xD;
+    naming conventions for more information.&#xD;
+&lt;/p>&#xD;
+&lt;h5>&#xD;
+    UMF configuration naming conventions&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    UMF configuration naming convention: &amp;lt;&lt;strong>configuration&#xD;
+    type&lt;/strong>&amp;gt;[.&lt;strong>context&lt;/strong>].&amp;lt;&lt;strong>descriptive name&amp;gt;[-&amp;lt;source/licensing level&amp;gt;]&lt;/strong>&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Where:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Configuration type&lt;/strong>: The following are the possible values for the&amp;nbsp;configuration&#xD;
+        type.&amp;nbsp;For more information on UMF configuration types, see [Concept: Practice Library Configuration Types]. &#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                publish = Publish Configuration&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                zconstruct = Process Construction Configuration (not commonly used since the advent of configuration-free&#xD;
+                processes)&lt;br />&#xD;
+            &lt;/li>&#xD;
+        &lt;/ul>&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Context&lt;/strong>: Same as for plug-ins.&lt;br />&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Descriptive name&lt;/strong>: The following conventions apply to the Descriptive name part of of a&#xD;
+        configuration name:&amp;nbsp;&amp;nbsp; &#xD;
+        &lt;ul>&#xD;
+            &lt;li>&#xD;
+                For Publish configurations, the Practice Configuration&amp;nbsp;name being published&amp;nbsp;makes a&amp;nbsp;good&#xD;
+                descriptive name&#xD;
+            &lt;/li>&#xD;
+            &lt;li>&#xD;
+                For Process Construction configurations, the name of the plug-in that contains the process makes a good&#xD;
+                descriptive name&lt;br />&#xD;
+            &lt;/li>&#xD;
+        &lt;/ul>&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        &lt;strong>Source/licensing level&lt;/strong>: Same as for plug-ins.&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;p>&#xD;
+    Note the following :&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        All configurations of the same type are grouped together because the first part of the configuration name is the&#xD;
+        configuration type&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        All configurations that support a specific context are grouped under the content name&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The publish configurations for a specific configuration are easy to spot because the configuration name is in the&#xD;
+        descriptive name&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The configuration to be used as the default configuration when constructing a process in a plug-in is easy to spot&#xD;
+        because the owning plug-in name is in the descriptive name&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        The unique identifier suffix is used to indicate the licensing level of the configurations (e.g., -ibm for&#xD;
+        commercial content and -ibm_int for internal IBM content)&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;h5>&#xD;
+    UMF configuration project naming conventions&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    UMF configuration project naming convention: &lt;strong>configs[-&lt;/strong>&amp;lt;&lt;strong>descriptive&#xD;
+    name&amp;gt;][-&amp;lt;source/licensing level&amp;gt;]&lt;/strong>&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Where:&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Descriptive name: This is optional (i.e., you may only have one tag group per licensing level).&amp;nbsp; If you use one,&#xD;
+    the descriptive name should be a name that represents a specific set or category of configurations.&amp;nbsp;&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Source/licensing level: Same as for plug-ins.&#xD;
+&lt;/p>&#xD;
+&lt;h5>&#xD;
+    UMF tag group naming conventions&#xD;
+&lt;/h5>&#xD;
+&lt;p>&#xD;
+    UMF tag group naming convention: &lt;strong>tags-&lt;/strong>&amp;lt;&lt;strong>descriptive name&amp;gt;[-&amp;lt;source/licensing&#xD;
+    level&amp;gt;]&lt;/strong>&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Where:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        Descriptive name: A name that represents a specific set or category of tags.&amp;nbsp; For example: mdev: Method&#xD;
+        Development&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Source/licensing level: Same as for plug-ins.&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;h4>&#xD;
+    IBM Licensing Levels&#xD;
+&lt;/h4>&#xD;
+&lt;p>&#xD;
+    The following are the unique identifiers being used for elements defined at the commercial level and above (they&#xD;
+    reflect IBM's licensing Levels:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        ibm = part of IBM's commercial methods (licensing level =&amp;nbsp; commercial)&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        ibm_int = part of IBM's internal methods (licensing level =&amp;nbsp; internal)&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        ibm_lic = part of IBM's licensable methods (licensing level = licensable)&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        ibm_prp = part of IBM's licensable methods (licensing level = proprietary)&amp;nbsp;&#xD;
+    &lt;/li>&#xD;
+&lt;/ul>&#xD;
+&lt;p>&#xD;
+    Other companies may defined their own licensing levels following similar conventions.&#xD;
+&lt;/p>&#xD;
+&lt;h3>&#xD;
+    Writing Brief Descriptions&#xD;
+&lt;/h3>&#xD;
+&lt;p>&#xD;
+    In general, all non-contributing method elements&amp;nbsp;need a brief description. A brief description provides a one or&#xD;
+    two sentence description of what the element is (in other words, what content the element contains).&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Brief descriptions should be written at the time the element is identified.&amp;nbsp;A well-written description is&#xD;
+    important because if you find it hard to describe what an element is, it may not be a good element&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    Follow these guidelines when developing method element brief descriptions:&#xD;
+&lt;/p>&#xD;
+&lt;ul>&#xD;
+    &lt;li>&#xD;
+        Do not include presentation names in brief descriptions because that makes it harder to change the presentation&#xD;
+        name. Instead, refer to &quot;this &amp;lt;element type&amp;gt;&quot;, where &amp;lt;element type&amp;gt; is the type of method element. For&#xD;
+        example, &quot;this role&quot;... or &quot;this guidance&quot;.&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Do not state the obvious. The brief description should not just repeat what can be understood from the element type&#xD;
+        and the presentation name. For example, for Concept: Pattern, don't just say, &quot;This concept describes what a&#xD;
+        Pattern is&quot;.&amp;nbsp;Such information does not provide any value.&amp;nbsp;Instead,&amp;nbsp;provide a one or two sentence&#xD;
+        summary of what the element contains.&amp;nbsp;For example, &quot;This concept describes&amp;nbsp;s generalized solution that&#xD;
+        can be implemented and applied in a problem situation (a context) and thereby eliminate one or more of the inherent&#xD;
+        problems.&quot;&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Avoid repeating the brief description in other fields of the method element. If there is nothing more to add to&#xD;
+        what is in the brief description, then omit the other description fields.&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Make sure that there is a period at the end of the brief description.&#xD;
+    &lt;/li>&#xD;
+    &lt;li>&#xD;
+        Check for general spelling and spacing errors.&#xD;
+    &lt;/li>&#xD;
 &lt;/ul></mainDescription>
 </org.eclipse.epf.uma:ContentDescription>