| <?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="-iEvCqr8UvGNsKj3pZyJ3JQ" |
| name="navigation_view_elements_in_the_umf,_apOmQMj7EdyoXMhaXAJ-6g" guid="-iEvCqr8UvGNsKj3pZyJ3JQ" |
| changeDate="2008-11-03T06:52:41.906-0800" version="7.2.0"> |
| <mainDescription><p>
 |
| The <a class="elementLink" href="./../../../core.mdev.common.extend_umf/guidances/concepts/umf_C03950A8.html"
 |
| guid="_nrrn4GqHEdun45RPFGeYnA">Unified Method Framework (UMF)</a>&nbsp;defines two types of navigation view elements:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Configuration-specific</strong>, meaning they are intended to be published as part of a specific
 |
| configuration
 |
| </li>
 |
| <li>
 |
| <strong>Common</strong>, meaning they are intended to be shared across plug-ins and configurations. The UMF defines
 |
| <em>navigation view building blocks</em>, which are intended to be used across <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/navigation_view_8F89044.html"
 |
| guid="_X_hFIPAjEdyHz_B1XFOUgA">navigation view</a>s, as well as generic navigation views that can be used as-is or
 |
| in parts in other navigation views.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Where the navigation view elements are defined and how elements are assigned to them is different for each.
 |
| </p>
 |
| <p>
 |
| <strong>Navigation view building blocks</strong> are elements that may be used across a number of navigation
 |
| views.&nbsp;The UMF navigation view building blocks categorize method elements by "types" as defined in the meta model
 |
| (i.e., <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">role</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/artifact_F635D25.html"
 |
| guid="_x7cUM9nmEdmO6L4XMImrsA">artifact</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/deliverable_BFE1A5A9.html"
 |
| guid="_yFbWoNnmEdmO6L4XMImrsA">deliverable</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/outcome_797E7695.html"
 |
| guid="_LNAAcB_iEdqAHrsQ7-jSbw">outcome</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/checklist_D780FDF.html"
 |
| guid="_7vpJsMaCEduMlb2cQZNTYw">checklist</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guideline_1D590B95.html"
 |
| guid="_uK8HMMaFEduMlb2cQZNTYw">guideline</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
 |
| guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
 |
| guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery process</a>es, etc), as well as some other key ones (e.g., release
 |
| information).&nbsp;The navigation view building blocks are defined as <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html"
 |
| guid="_eqw94MaFEduMlb2cQZNTYw">custom categories</a>&nbsp;in Navigation View Definition plug-ins, where they can be
 |
| shared across plug-ins. If you want to define additional navigation view building blocks, define an Extends plug-in
 |
| that includes the new building blocks and include the new building blocks in a custom category that contributes to the
 |
| base navigation view building blocks custom category.&nbsp;Using such "super custom categories" will keep the list of
 |
| top-level custom categories from getting too long.
 |
| </p>
 |
| <p>
 |
| <strong>Generic navigation views</strong> are navigation views that may be applicable in multiple
 |
| configurations.&nbsp;They are also defined as custom categories in Navigation View Definition plug-ins, where they can
 |
| be shared across plug-ins.&nbsp;Generic navigation views assemble navigation view building blocks into something that
 |
| can be used as a whole or in parts as a publishable navigation view.&nbsp;For example, a generic navigation view can be
 |
| used to provide a view of everything in the configuration. These navigation views can be used for specific method
 |
| configurations as-is, or tweaked to address the specific needs of the configuration (e.g., extend/replace it or ignore
 |
| and build their own).&nbsp;The benefits of sharing navigation view elements is that you automatically get consistent
 |
| navigation views.
 |
| </p>
 |
| <p>
 |
| <strong>Configuration-specific navigation views</strong> are defined as custom categories in the Publish plug-in for
 |
| the configuration that is to be published.&nbsp;The configuration-specific navigation views indicate what elements
 |
| elements (or navigation view building blocks) are to be included.&nbsp;When defining a configuration-specific
 |
| navigation view, you can:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Create a new view using existing navigation view elements
 |
| </li>
 |
| <li>
 |
| Reuse the common generic navigation view, replacing and/or adding to selected elements, as needed.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Custom categories that are designed to be navigation views should include "view" in the name.&nbsp;Also, the custom
 |
| categories that represent the navigation view tabs for the configuration should be "packaged" in a parent custom
 |
| category with "view tabs" in the name.&nbsp;This makes it easy to identify the custom categories that have been
 |
| designed to serve as the navigation views for the configuration.
 |
| </p>
 |
| <p>
 |
| <br />
 |
| </p>
 |
| <p>
 |
| The UMF also defines a <strong>“Do Not Publish” category</strong>. It is also defined as a custom category in
 |
| Navigation View Definition Base plug-ins, where it can be shared across plug-ins.&nbsp;Plug-ins can map specific method
 |
| elements to this custom category to keep the elements from being published. This category is especially useful for
 |
| publish plug-ins that are constructing custom views for publishing.&nbsp;The elements in&nbsp;this category should be
 |
| removed from all publishable configurations.&nbsp;For more information on publishable configurations, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_lib_config_types_B96A959A.html"
 |
| guid="_1gchoO6dEdygKbJMUVNEtg">Concept: Practice Library Configuration Types</a>.
 |
| </p>
 |
| <p>
 |
| For more information on the UMF plug-in types (e.g., Navigation View Definition plug-ins, Publish plug-ins, etc.), 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></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
