| <?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="-umyCmhng09bIwqV4nWBHaA" |
| name="structuring_practice_fw_core_customization,_-WfTIKnHEd2eRp4Z7dEEOQ" guid="-umyCmhng09bIwqV4nWBHaA" |
| changeDate="2008-11-03T08:58:36.640-0800" version="7.5.0"> |
| <mainDescription><p>
 |
| <a class="elementLink" href="./../../../core.mdev.common.base/guidances/concepts/practice_fw_6DA4D54D.html"
 |
| guid="__LjaEFQsEd2uvIuuFjd1Fg">Practice Framework</a>&nbsp;core&nbsp;customizations are stored in a separate plug-ins
 |
| from the&nbsp;core elements being customized. Specifically, all core element customizations should be defined in an
 |
| Extend plug-in for the Core plug-in that contains the element to be customized. For more information on Core and Extend
 |
| plug-ins, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_lib_plugin_types_3EA8002F.html"
 |
| guid="__428YO6cEdygKbJMUVNEtg">Concept: Practice Library Plug-In Types</a>.
 |
| </p>
 |
| <p>
 |
| There are a number of different ways that you can customize the practice framework core.&nbsp;You can:&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Add a new work product slot
 |
| </li>
 |
| <li>
 |
| Customize an existing work product slot
 |
| </li>
 |
| <li>
 |
| Add a new common method content element (e.g., role, work product or guidance;&nbsp;tasks are&nbsp;generally stored
 |
| in <a class="elementLink" href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
 |
| guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>s)&nbsp;
 |
| </li>
 |
| <li>
 |
| Customize an existing common method content element&nbsp;
 |
| </li>
 |
| <li>
 |
| Add new shared domains or disciplines
 |
| </li>
 |
| <li>
 |
| Customize existing shared domains or disciplines
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The following sections describe how you would structure these customizations.&nbsp;
 |
| </p>
 |
| <p>
 |
| <strong>Add a new work product slot</strong>
 |
| </p>
 |
| <p>
 |
| Perform the following steps to define a new <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/work_product_slot_D5B44CE7.html"
 |
| guid="_Er1OcJIfEdybeduord13cg">Work Product Slot</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| If it does not already exist, create an Extend plug-in to contain the new slot.
 |
| </li>
 |
| <li>
 |
| Define a new artifact and indicate that it is a slot. For more information, see <a class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_fw_arch.base/guidances/guidelines/defining_work_product_slots_EE90888A.html"
 |
| guid="_qVnDgC2sEd2CiunvJQy6fQ">Guideline: Defining Work Product Slots</a>.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Customize an existing work product slot</strong>
 |
| </p>
 |
| <p>
 |
| Perform the following steps to customize (not just by adding guidance) an existing <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/work_product_slot_D5B44CE7.html"
 |
| guid="_Er1OcJIfEdybeduord13cg">Work Product Slot</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| If one does not exist, create an Extends&nbsp;plug-in to contain the slot customizations.
 |
| </li>
 |
| <li>
 |
| Customize the slot the same way you customize any work product. However, since slots are shared across practices,
 |
| be sure that they adhere to guidelines for slots and that the changes are applicable across practices. For more
 |
| information on slots, see <a class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_fw_arch.base/guidances/guidelines/defining_work_product_slots_EE90888A.html"
 |
| guid="_qVnDgC2sEd2CiunvJQy6fQ">Guideline: Defining Work Product Slots</a>. For more information on customizing
 |
| work products, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/customizing_method_content_element_87D73FFF.html"
 |
| guid="_5cHsoFJsEd2SzrMjC_svdw">Guideline: Customizing a Method Content Element</a>.&nbsp;&nbsp;
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Add a new common method content element</strong>
 |
| </p>
 |
| <p>
 |
| Perform the following steps to add a new common <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_content_6972AE81.html"
 |
| guid="_Ts2joB_MEdq6CKKKq4D7YA">method content</a>&nbsp;element (e.g.,&nbsp;<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">role</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
 |
| guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>)&nbsp;to the core (<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s are generally not common, but are considered practice-specific):&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| If it does not already exist, create an Extend plug-in to contain the new common element.<br />
 |
| Note: Practice frameworks generally&nbsp;implement a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/delayed_assignment_24142865.html"
 |
| guid="_rlrykJcbEd2sTqxclDgvog">Delayed Assignment</a>&nbsp;approach for roles, so it is recommended that role
 |
| definitions be placed in their own plug-in.
 |
| </li>
 |
| <li>
 |
| In the new plug-in, define the new element.&nbsp;These elements are common so be sure to only include information
 |
| that is common across practices. Do not include any associations between elements as such relationships are
 |
| better-defined in practices. For more information, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/defining_method_content_elements_21A491E3.html"
 |
| guid="_XQqJkCAmEdy1y5bWsXfCCg">Guideline: Defining Method Content Elements</a>.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <strong>Customize an existing&nbsp;common method content element</strong>
 |
| </p>
 |
| <p>
 |
| Perform the following steps to customize&nbsp;an existing common <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_content_6972AE81.html"
 |
| guid="_Ts2joB_MEdq6CKKKq4D7YA">method content</a>&nbsp;element (e.g.,&nbsp;<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">role</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
 |
| guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>)&nbsp;to the core (<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s are generally not common, but are considered practice-specific):
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| If one does not exist, create an Extends&nbsp;plug-in to contain the customizations.
 |
| </li>
 |
| <li>
 |
| Customize the elements the same way you customize any element. However, since common elements are shared across
 |
| practices, be sure to only include information that is common across practices. Do not include any associations
 |
| between elements as such relationships are better-defined in practices. For more information, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/customizing_method_content_element_87D73FFF.html"
 |
| guid="_5cHsoFJsEd2SzrMjC_svdw">Guideline: Customizing a Method Content Element</a>.&nbsp;&nbsp;
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Add a new shared domain or discipline
 |
| </h3>
 |
| <p>
 |
| Perform the following steps to add a new shared <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html"
 |
| guid="_yHEVYdnmEdmO6L4XMImrsA">domain</a>&nbsp;or <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html"
 |
| guid="_yGUuidnmEdmO6L4XMImrsA">discipline</a>:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| If one does not exist, create an Extends&nbsp;plug-in to contain the domain or discipline definitions.<br />
 |
| Note: Practice frameworks generally&nbsp;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, so it is recommended
 |
| that domain and discipline definitions be placed in their own plug-in.&nbsp;
 |
| </li>
 |
| <li>
 |
| In the new plug-in, define the new standard category. Do not assign any elements to the categories as the
 |
| categorization of elements to standard categories is done in the practices. For more information, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/categorizing_method_elements_using_std_cats_854BD33A.html"
 |
| guid="_thsRIMjnEdyoXMhaXAJ-6g">Guideline: Categorizing Method Elements Using Standard Categories</a>.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Customize existing shared domains or disciplines
 |
| </h3>
 |
| <p>
 |
| Perform the following steps to customize and existing shared <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/domain_D8238B93.html"
 |
| guid="_yHEVYdnmEdmO6L4XMImrsA">domain</a>&nbsp;or <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/discipline_7667F451.html"
 |
| guid="_yGUuidnmEdmO6L4XMImrsA">discipline</a>:
 |
| </p>
 |
| <ul class="noindent">
 |
| <li>
 |
| If one does not exist, create an Extends&nbsp;plug-in to contain the domain or discipline customizations.<br />
 |
| Note: Practice frameworks generally&nbsp;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, so it is recommended
 |
| that domain and discipline definitions be placed in their own plug-in.&nbsp;
 |
| </li>
 |
| <li>
 |
| In the new plug-in, customize the standard category. Do not add any elements to the categories as the
 |
| categorization of elements to standard categories is done in the practices. For more information, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/customizing_std_cat_7B5D3F48.html"
 |
| guid="_Y_tk0KkVEd2XsY8-UtPVvw">Guideline: Customizing a Standard Category</a>.
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
