| <?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="-n2rq5P3Y8Gb-AcFTHibPsQ" |
| name="practice_lib_plugin_types.umf,_I0aCUGVSEd2sEeXQllKBcA" guid="-n2rq5P3Y8Gb-AcFTHibPsQ" |
| changeDate="2008-11-05T10:05:43.921-0800" version="1.0.0"> |
| <mainDescription><h3>
 |
| Core plug-in subtypes
 |
| </h3>
 |
| <p>
 |
| There are a number of different types of elements that are&nbsp;intended to be shared across the framework (i.e.,
 |
| are&nbsp;contained in core plug-ins). However,&nbsp;several of these items need to be reused independently (i.e., I
 |
| want to share&nbsp;tool definitions, but I want to define my own domains).&nbsp;Thus, in addition to the above primary
 |
| plug-in types, the <a class="elementLink"
 |
| href="./../../../core.mdev.common.extend_umf/guidances/concepts/umf_C03950A8.html"
 |
| guid="_nrrn4GqHEdun45RPFGeYnA">Unified Method Framework (UMF)</a>&nbsp;also defines a number of Core
 |
| plug-in&nbsp;subtypes.
 |
| </p>
 |
| <p>
 |
| <strong>Slot</strong> plug-ins contain the <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/work_product_slot_D5B44CE7.html"
 |
| guid="_Er1OcJIfEdybeduord13cg">Work Product Slot</a>&nbsp;definitions, as well as any associated guidance.
 |
| </p>
 |
| <p>
 |
| <strong>Common</strong> plug-ins contain common reusable elements such as <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s or <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
 |
| guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that are intended to be shared across plug-ins.&nbsp;It is possible
 |
| for different practices to utilize the same underlying work products and basic guidance even though they have alternate
 |
| approaches with different techniques to produce the same work products.&nbsp;Instead of creating unnecessary
 |
| dependencies between practices that are peers, shared elements are defined as common. Common elements, by their very
 |
| nature, as defined in a practice-independent way so that multiple practices can share the common content.&nbsp;They are
 |
| written at a generic level with the expectation that they will be further specialized as needed for a particular
 |
| practice and/or process.&nbsp;Work products should be with the content that supports them.&nbsp;Only truly common work
 |
| product definitions should be in common.&nbsp;A litmus test for deciding whether a method element should be placed in a
 |
| common plug-in or not is whether the content is applicable across all contexts for which it applies.
 |
| </p>
 |
| <p>
 |
| The following are some examples of the use of common elements:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A&nbsp;light weight architecture practice and a heavy weight architecture practice can share a common definition of
 |
| an architecture work product, but not share <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s (the tasks are defined in the practice).
 |
| </li>
 |
| <li>
 |
| Two different types of development (e.g., Greenfield vs. reverse engineering approaches) produce the same work
 |
| products, but they go through different state changes, have different tasks, etc.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Role Definition</strong> plug-ins contain the <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">role</a>s&nbsp;(and optionally <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_set_396DC9DB.html"
 |
| guid="_Fs8HAMaIEduMlb2cQZNTYw">role set</a>&nbsp;definitions) that are intended to be shared across
 |
| practices.&nbsp;Since practice frameworks usually implements a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/delayed_assignment_24142865.html"
 |
| guid="_rlrykJcbEd2sTqxclDgvog">Delayed Assignment</a>&nbsp;approach for roles, the Role Definition plug-ins do not
 |
| contain the assignment of roles to <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s or <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s.
 |
| </p>
 |
| <p>
 |
| <strong>Category Definition</strong> plug-ins contain category definitions that are intended to be shared across
 |
| practices.&nbsp;In the UMF, this includes <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html"
 |
| guid="_yGUuidnmEdmO6L4XMImrsA">discipline</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html"
 |
| guid="_yHEVYdnmEdmO6L4XMImrsA">domain</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_kind_F04A382B.html"
 |
| guid="_QWhfYMaJEduMlb2cQZNTYw">work product kind</a>&nbsp;and possibly <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_set_396DC9DB.html"
 |
| guid="_Fs8HAMaIEduMlb2cQZNTYw">role set</a>&nbsp;definitions (if they are not in the Role Definition
 |
| plug-in).&nbsp;Since practice frameworks usually implement a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/delayed_assignment_24142865.html"
 |
| guid="_rlrykJcbEd2sTqxclDgvog">Delayed Assignment</a>&nbsp;approach for standard categories, the Category Definition
 |
| plug-ins do not contain the assignment of elements to these categories. <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_D0FBC781.html"
 |
| guid="_BangwMaJEduMlb2cQZNTYw">Tools</a> are defined in separate Tool Definition plug-ins, as these were envisioned to
 |
| be separately reusable from the other standard categories.
 |
| </p>
 |
| <p>
 |
| <strong>Tool Definition</strong> plug-ins contain <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_D0FBC781.html"
 |
| guid="_BangwMaJEduMlb2cQZNTYw">tool</a>&nbsp;and <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_mentor_264766F3.html"
 |
| guid="_yYy-mdnmEdmO6L4XMImrsA">tool mentor</a>&nbsp;definitions that are intended to be shared across practices. The
 |
| assignment of tools to tool mentors not generally delayed assigned, so the Tool Definition plug-ins contain the
 |
| assignment of the included tool mentors to the tools. Practice-specific tool mentors <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_mentor_264766F3.html"
 |
| guid="_yYy-mdnmEdmO6L4XMImrsA"></a>and assignment of the practice-specific tool mentors to the tools are defined in
 |
| Practice plug-ins.
 |
| </p>
 |
| <p>
 |
| <strong>Navigation View Definition</strong> plug-ins contain navigation view definitions that are intended to be shared
 |
| across plug-ins (e.g., generic navigation views and navigation view building blocks).
 |
| </p>
 |
| <p>
 |
| <strong>Release Copyright</strong> plug-ins contain the release copyrights that should be used for the plug-ins in the
 |
| framework.&nbsp;There may be any number of Release Copyright plug-ins.&nbsp;Every plug-in should have the appropriate
 |
| copyright plug-in associated to it.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
