| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-9dyAwJH3l0cxLrzWrgsniw" |
| name="naming_method_elements,_lAphAF5-EduT-Px7fh0LSg" guid="-9dyAwJH3l0cxLrzWrgsniw" |
| changeDate="2008-09-11T07:16:41.515-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| This guidance provides general information on naming method elements.&nbsp; For method element-specific naming
 |
| guidance, see the attached guidance.
 |
| </p>
 |
| <h4>
 |
| Abbreviations
 |
| </h4>
 |
| <p>
 |
| It is a good practice is to provide a list of approved abbreviations for your project.&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.
 |
| </p>
 |
| <h3>
 |
| Name fields
 |
| </h3>
 |
| <p>
 |
| Most method elements have two name fields:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The&nbsp;<strong>Name</strong> is always present since it is the <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the element.<br />
 |
| </li>
 |
| <li>
 |
| The <strong>Presentation Name</strong> is present for some elements; it is the name&nbsp;displayed in the published
 |
| web site for the element. Thus, a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;should be used.
 |
| </li>
 |
| </ul><br />
 |
| <h3>
 |
| General naming guidelines
 |
| </h3>
 |
| <p>
 |
| In general, all method elements should following the following recommendations:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Name should reflect the essence of the element
 |
| </li>
 |
| <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)
 |
| </li>
 |
| <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
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| For general guidelines on naming variants, see the section on that topic later in this guideline.
 |
| </p><br />
 |
| <h3>
 |
| Method element-specific naming guidelines
 |
| </h3>
 |
| <p>
 |
| Table 1 provides element-specific guidelines for naming the different types of method elements.&nbsp;
 |
| </p>
 |
| <p>
 |
| <strong>Table 1: Method Element Naming Conventions</strong><br />
 |
| <br />
 |
| </p>
 |
| <table id="table3" border="1">
 |
| <tbody>
 |
| <tr align="middle">
 |
| <td width="20%">
 |
| <strong>Element</strong>
 |
| </td>
 |
| <td width="25%">
 |
| <strong>Guideline</strong>
 |
| </td>
 |
| <td width="55%">
 |
| <strong>Reason</strong>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Plug-in
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| <li>
 |
| Omit the word "plug-in" in the names (it is redundant)
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <p>
 |
| The value&nbsp;of the&nbsp;Name field determines the directory name used in the file
 |
| system.&nbsp;&nbsp;
 |
| </p>
 |
| <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.&nbsp;
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <p>
 |
| Method content package
 |
| </p>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <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&nbsp;self-explanatory.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <p>
 |
| Process package
 |
| </p>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for Name field (process&nbsp;packages only
 |
| have a single name field)
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <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&nbsp;self-explanatory.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Standard category
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul class="noindent">
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <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&nbsp;self-explanatory.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Custom category
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul class="noindent">
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| If the custom category is to be used for a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/navigation_view_8F89044.html"
 |
| guid="_X_hFIPAjEdyHz_B1XFOUgA">navigation view</a>, include "view" in both name fields.&nbsp;
 |
| </p>
 |
| </td>
 |
| <td width="50%">
 |
| <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&nbsp;self-explanatory.
 |
| </p>
 |
| <p>
 |
| The Presentation name of a custom category that is used as a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/navigation_view_8F89044.html"
 |
| guid="_X_hFIPAjEdyHz_B1XFOUgA">navigation view</a>&nbsp;is also used as the name of the tab that is
 |
| published for that view.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Configuration
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| <li>
 |
| Omit the word "configuration" in the names (it is redundant)
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <p>
 |
| The Name field determines the file name used in the file system.&nbsp;
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Role
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Task
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <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
 |
| "Acceptable Verbs" table in a later section.&nbsp; The object should be closely related to the output
 |
| work product.
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| For example:&nbsp; Define Test Specification<br />
 |
| "Define" is the verb and means "to determine the essential qualities". (see Table 2). "Test
 |
| Specification" is the main output work product for the task.
 |
| </p>
 |
| </blockquote>
 |
| <p dir="ltr">
 |
| Alternatively, the task name may reflect the objective of performing the task, instead of being closely
 |
| related to the output work product.
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p dir="ltr">
 |
| For example: Plan the Project.
 |
| </p>
 |
| </blockquote>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Work product: Artifact
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Work product: Deliverable
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Work product: Outcome
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Guidance
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Capability pattern
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <br />
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| Delivery process
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| </tbody>
 |
| </table><br />
 |
| <br />
 |
| <br />
 |
| <h3>
 |
| Acceptable verbs
 |
| </h3>
 |
| <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.
 |
| </p>
 |
| <p>
 |
| <strong>Table 2: Acceptable Verbs</strong><br />
 |
| </p>
 |
| <table id="table4" width="100%" border="1">
 |
| <tbody>
 |
| <tr>
 |
| <td width="20%">
 |
| <strong>Verb</strong>
 |
| </td>
 |
| <td width="60%">
 |
| <strong>Meaning</strong>
 |
| </td>
 |
| <td width="20%">
 |
| <strong>Comments</strong>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Acquire
 |
| </td>
 |
| <td>
 |
| To come into possession of
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Analyze
 |
| </td>
 |
| <td>
 |
| To determine the relationship of component parts
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Assemble
 |
| </td>
 |
| <td>
 |
| To fit parts together
 |
| </td>
 |
| <td>
 |
| Especially useful for deliverables
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Assess
 |
| </td>
 |
| <td>
 |
| To make a judgment of worth
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Assign
 |
| </td>
 |
| <td>
 |
| To appoint to a post or duty
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Build
 |
| </td>
 |
| <td>
 |
| To construct by putting parts or materials together
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Capture
 |
| </td>
 |
| <td>
 |
| To document
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Categorize
 |
| </td>
 |
| <td>
 |
| To analyze and group according to a particular criteria
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Cleanse
 |
| </td>
 |
| <td>
 |
| To purify
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Communicate
 |
| </td>
 |
| <td>
 |
| To transmit information so that it is understood
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Conduct
 |
| </td>
 |
| <td>
 |
| To direct or manage
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Configure
 |
| </td>
 |
| <td>
 |
| To set up for operation
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Confirm
 |
| </td>
 |
| <td>
 |
| To verify that you have what's needed
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Detail
 |
| </td>
 |
| <td>
 |
| To provide the details for an outlined artifact
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Develop
 |
| </td>
 |
| <td>
 |
| To bring to maturity;&nbsp; to provide a more specific definition
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Elicit
 |
| </td>
 |
| <td>
 |
| To draw out or evoke
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Enable
 |
| </td>
 |
| <td>
 |
| To make operational
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Estimate
 |
| </td>
 |
| <td>
 |
| To judge approximate value
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Evaluate
 |
| </td>
 |
| <td>
 |
| To determine significance or worth
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Gather
 |
| </td>
 |
| <td>
 |
| To bring together into one collection
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Gather
 |
| </td>
 |
| <td>
 |
| To locate and bring together
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Identify
 |
| </td>
 |
| <td>
 |
| To establish identifty
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Implement
 |
| </td>
 |
| <td>
 |
| To fulfill; to realize
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Initiate
 |
| </td>
 |
| <td>
 |
| To facilitate the beginning
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Install
 |
| </td>
 |
| <td>
 |
| To place in position of use
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Manage
 |
| </td>
 |
| <td>
 |
| To direct or supervise
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Obtain
 |
| </td>
 |
| <td>
 |
| To get or attain by planned action or effort
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Outline
 |
| </td>
 |
| <td>
 |
| To describe key elements
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Perform
 |
| </td>
 |
| <td>
 |
| To do
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Plan
 |
| </td>
 |
| <td>
 |
| To describe objectives, as well as a sequence and deadline for reaching a goal; to specify how to reach a
 |
| goal
 |
| </td>
 |
| <td>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Prepare
 |
| </td>
 |
| <td>
 |
| To make ready
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Prioritize
 |
| </td>
 |
| <td>
 |
| To set priorities
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Receive
 |
| </td>
 |
| <td>
 |
| To <span
 |
| style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">acquire,
 |
| come into possession</span>
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Reconcile
 |
| </td>
 |
| <td>
 |
| To check against another for accuracy and make them match
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Release
 |
| </td>
 |
| <td>
 |
| To make available for use
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Review
 |
| </td>
 |
| <td>
 |
| To examine carefully, looking for errors, omissions, ambiguity, inconsistency&nbsp;&nbsp;
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Run
 |
| </td>
 |
| <td>
 |
| To perform, generally by executing a program on a computer
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Select
 |
| </td>
 |
| <td>
 |
| To choose
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Specify
 |
| </td>
 |
| <td>
 |
| To name or state explicitly or in detail
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Ship
 |
| </td>
 |
| <td>
 |
| To trasnport an item
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Train
 |
| </td>
 |
| <td>
 |
| To teach a task or job
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Understand
 |
| </td>
 |
| <td>
 |
| To comprehend meaning
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Validate
 |
| </td>
 |
| <td>
 |
| To confirm that a solution or process is correct
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td>
 |
| Verify
 |
| </td>
 |
| <td>
 |
| To ensure correctness according to specific criteria
 |
| </td>
 |
| <td>
 |
| &nbsp;
 |
| </td>
 |
| </tr>
 |
| </tbody>
 |
| </table><br />
 |
| <br />
 |
| Do not use <em>leverage</em> because it is marketing jargon and also outdated jargon. We avoid jargon because it always
 |
| becomes outdated and doesn't translate accurately.<br />
 |
| <br />
 |
| <br />
 |
| <h3>
 |
| Naming method variants
 |
| </h3>
 |
| <p>
 |
| This section provides specific recommendations on how to name elements that have a variability relationship to another
 |
| element.
 |
| </p>
 |
| <p>
 |
| The following table provides guidance about naming specific variants.
 |
| </p>
 |
| <table id="table3" border="1">
 |
| <tbody>
 |
| <tr align="middle">
 |
| <td width="20%">
 |
| <strong>Element</strong>
 |
| </td>
 |
| <td width="25%">
 |
| <strong>Guideline</strong>
 |
| </td>
 |
| <td width="55%">
 |
| <strong>Reason</strong>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <strong>Base element</strong>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation Name field&nbsp;
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <strong>Contributor</strong>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field 
 |
| <ul>
 |
| <li>
 |
| use exactly the same name as the element to which the contribution is being made
 |
| </li>
 |
| <li>
 |
| add a suffix that identifies the plug-in providing the contribution
 |
| </li>
 |
| <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
 |
| </li>
 |
| <li>
 |
| the suffix should be distinct from the name. Use a period (.) to separate a suffix from the
 |
| name<br />
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| <li>
 |
| leave&nbsp;Presentation Name field blank (it is inherited)
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <p>
 |
| Do not specify a presentation name for contributing elements because&nbsp;it is inherited from the base
 |
| element.
 |
| </p>
 |
| <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.
 |
| </p>
 |
| <p>
 |
| To aid in distinguishing between diffierent contributors and the base element, it is a good idea to
 |
| name contributors differently from the base element.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <strong>Replacement</strong>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul class="noindent">
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation name field
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Note:&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.
 |
| </p>
 |
| </td>
 |
| <td width="50%">
 |
| A <em>replacing element</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.
 |
| </td>
 |
| </tr>
 |
| <tr>
 |
| <td width="20%">
 |
| <strong>Extension</strong>
 |
| </td>
 |
| <td valign="top" width="30%">
 |
| <ul>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/internal_name_4F809BC3.html"
 |
| guid="_IwawgOnyEduAapZyGeTI0Q">internal name</a>&nbsp;for the Name field
 |
| </li>
 |
| <li>
 |
| use <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/friendly_name_35BC1203.html"
 |
| guid="_39tdwOnwEduAapZyGeTI0Q">friendly name</a>&nbsp;for the Presentation Name field
 |
| </li>
 |
| </ul>
 |
| </td>
 |
| <td width="50%">
 |
| <p>
 |
| An extending element is a new element.&nbsp; Thus, the name of an extending element should be different
 |
| from the element being extended.
 |
| </p>
 |
| </td>
 |
| </tr>
 |
| </tbody>
 |
| </table><br /></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |