| <?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="-qg1DmRrMT9oYmnekhEjabA" |
| name="new_guideline,_OIOSQF_zEduYvI5nsNyVYA" guid="-qg1DmRrMT9oYmnekhEjabA" changeDate="2008-11-10T10:48:46.812-0800" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| &nbsp;The following are some general guidelines when defining <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html"
 |
| guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-in</a>s:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| Name and briefly describe the plug-in. For guidelines on naming a plug-in, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/method_element_naming_conventions_4A4F743B.html"
 |
| guid="_lAphAF5-EduT-Px7fh0LSg">Guideline: Method Element Naming Conventions</a>.&nbsp;For guidelines in writing a
 |
| brief description, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/writing_brief_descriptions_D01D2F53.html"
 |
| guid="_cJbBkCAhEdy1y5bWsXfCCg">Guideline: Writing Brief Descriptions</a>.<br />
 |
| &nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| Capture the source of the information for the plug-in.&nbsp;This information is important if you ever need to
 |
| provide source information for the plug-in for documenting ownership rights.<br />
 |
| &nbsp;&nbsp;&nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| Maintain accurate change histories, as well as making sure your trademarks and copyrights are accurate.&nbsp;For
 |
| more information, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/maintaining_change_histories_and_version_numbers_B83271.html"
 |
| guid="_k91OkFpBEdutiI3y4Hpy9Q">Guideline: Maintaining Change Histories and Version Numbers</a>&nbsp;and <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/trademarks_and_copyrights_F14EB70C.html"
 |
| guid="_OxsfkH8MEdu_ipWWZJimvQ">Guideline: Trademarks and Copyrights</a>.<br />
 |
| &nbsp;
 |
| </li>
 |
| <li>
 |
| Identify any plug-ins that the plug-in must reference (in other words, the plug-ins the new plug-in depends
 |
| on).<br />
 |
| &nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| <p>
 |
| Define content packages to contain the method elements.&nbsp;Alternatively, those packages can be created on
 |
| demand, as method elements are defined in the plug-in.&nbsp; For more information, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/packaging_method_elements_E4EC8A32.html"
 |
| guid="_bAjgIIAhEd2RgsZLwhqsAA">Guideline: Packaging Method Elements</a>.
 |
| </p>
 |
| </li>
 |
| </ul>
 |
| <p style="LIST-STYLE-TYPE: none">
 |
| Consider the following when deciding whether or not to create a new plug-in:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| Don’t modify content in plug-ins that are locked or owned by other parties. Instead, create a new plug-in that
 |
| extends or replaces the base content. Standard plug-ins provided as part of a standard library should be locked to
 |
| avoid inadvertent changes. Lock any third-party plug-ins after importing them.
 |
| </li>
 |
| <li>
 |
| Each plug-in has a physical file that contains information about all of the other content elements in the plug-in.
 |
| Therefore, if several individuals are working on content for the same plug-in, that file will need to be carefully
 |
| controlled. In such cases, you may want to consider dividing the method content that will be added to the base
 |
| method content into more than one plug-in to avoid contention over the plug-in file.
 |
| </li>
 |
| <li>
 |
| Before defining new plug-ins, be sure to review the structure and content of existing method plug-ins.&nbsp;This is
 |
| especially important in those cases where you are customizing or building on an existing method.
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
