| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:GuidanceDescription 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="-o8VsXB3dfgCwC_abptAnDw" |
| name="umf_nav_view_example,_GH_qsIMzEd2QVrMx9wDJQQ" guid="-o8VsXB3dfgCwC_abptAnDw" |
| changeDate="2008-09-30T13:46:41.062-0700" version="7.5.0"> |
| <mainDescription><p>
 |
| Figure 1 is an example of a Navigation View Definition plug-in.&nbsp;Note the definition of the "do not publish" custom
 |
| category, as well as the navigation view building blocks and a generic navigation view that includes those building
 |
| blocks.
 |
| </p>
 |
| <p>
 |
| Figure 1: Navigation View Definition Plug-In Example
 |
| </p><img alt="umf_navigation_view_plugin_example" src="./resources/umf_nav_view_plugin_ex.gif" /><br />
 |
| <p>
 |
| Figure 2 takes a closer look at one of the navigation view building blocks (the guideline list) and provides an example
 |
| of a custom category that is automatically populated with elements of a specific type (guideline) at browse and publish
 |
| time. Notice that no elements have been included in the <strong>Content elements</strong> section. Instead, the
 |
| <strong>include elements of type</strong> check box is checked and <strong>Guideline</strong> is selected from the
 |
| drop-down menu. The result is that when a configuration is browsed or published, all guidelines in that configuration
 |
| are added to the guideline_list custom category. Such auto-populated categories can be included as part of any other
 |
| navigation views.
 |
| </p>
 |
| <p>
 |
| Figure 2: Auto Populated Custom Category Example
 |
| </p>
 |
| <p>
 |
| <img height="551" alt="auto_populated_custom_category_example" src="./resources/smart_cat_example.gif"
 |
| width="511" />&nbsp;
 |
| </p>
 |
| <p>
 |
| Figure 3 provides an example of how to define additional navigation view building blocks.&nbsp;
 |
| </p>
 |
| <p>
 |
| Note the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The new navigation view building block custom categories (for different categories of practices)
 |
| </li>
 |
| <li>
 |
| The contributing custom category that adds the new building blocks to the existing navigation view build block
 |
| custom category
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Figure 3: Additional Navigation View Building Block Example
 |
| </p>
 |
| <p>
 |
| <img alt="umf_navigation_view_extension_example" src="resources/umf_nav_view_extension_ex.gif" />&nbsp;
 |
| </p>
 |
| <p>
 |
| Figure 4 shows how the navigation view building blocks and generic navigation view can be used to define a
 |
| configuration-specific navigation view. In this example,&nbsp;the&nbsp;core navigation view elements&nbsp;are
 |
| customized to support the navigation views for the OpenUP configuration.
 |
| </p>
 |
| <p>
 |
| Note the following:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The custom category that replaces the structured_practice_list custom category in the core plug-in with a practices
 |
| custom category that organizes the practices into “management” and “technical” practices.&nbsp;
 |
| </li>
 |
| <li>
 |
| The configuration-specific additions to the getting_started and release_info custom categories
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Figure 4: Configuration-Specific Navigation View Example
 |
| </p>
 |
| <p>
 |
| <img alt="umf_configuration_specified_navigation_view_example"
 |
| src="./resources/umf_config_spec_nav_view_ex.gif" /><br />
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:GuidanceDescription> |
