| <?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="-qxtaR_hQ6SR_o4S3KT6zrQ" |
| name="new_guideline,_V7qwIMjpEdyoXMhaXAJ-6g" guid="-qxtaR_hQ6SR_o4S3KT6zrQ" changeDate="2008-10-16T10:47:34.876-0700" |
| version="7.2.0"> |
| <mainDescription><p>
 |
| Custom categories can be used to categorize method elements so that the practitioners can find them easily and quickly.
 |
| They also form the basis of a published configuration by defining the <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/navigation_view_8F89044.html"
 |
| guid="_X_hFIPAjEdyHz_B1XFOUgA">navigation view</a>&nbsp;structure for the configuration.&nbsp;
 |
| </p>
 |
| <p>
 |
| Custom categories are highly customizable and can contain any type of element. Custom categories allow you to
 |
| categorize content according to any hierarchical scheme you want and can then be used to compose publishable views, as
 |
| well as providing a means to organize the method content prior to publishing. For example, you could create a <a
 |
| class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html"
 |
| guid="_eqw94MaFEduMlb2cQZNTYw">custom category</a>&nbsp;that logically organizes content relevant to your development
 |
| organization department, such as a Testing category that groups together all roles, work products, tasks, and guidance
 |
| elements relevant to testing.
 |
| </p>
 |
| <p>
 |
| When defining custom categories, consider the different ways you may want to access the elements, as well as the ways
 |
| in which the end-user of the method may want to access the method elements.&nbsp; The former may result in ideas for
 |
| "method management-focused" custom categories, while the latter may result in ideas for navigation view focused custom
 |
| categories. What information is needed? How does one find that information? Well crafted custom categories will help
 |
| enormously.
 |
| </p>
 |
| <p>
 |
| Custom categories can be nested to create a categorization hierarchy. For example, if you want to define a navigation
 |
| view that includes "sub-folders", you can do that by defining a sub-custom category in a navigation view custom
 |
| category for each folder you would like to be included.
 |
| </p>
 |
| <p>
 |
| Custom categories can also be nested to organize the custom categories.&nbsp;For example, if you define a set of custom
 |
| categories that are intended to represent navigation views and another set that are not.&nbsp;You may want to package
 |
| all the navigation view custom categories in a single custom category.&nbsp;In this case, the topmost custom category
 |
| is more like a package than a custom category.
 |
| </p>
 |
| <p>
 |
| You can add elements to existing categories by defining a custom category that contributes to the original custom
 |
| category and adds the desired elements.&nbsp;
 |
| </p>For methods containing a lot of elements and plug-ins, defining a shared set of custom categories can be beneficial for
 |
| the following reasons: <br />
 |
| <br />
 |
| <ul>
 |
| <li>
 |
| Method authors have a consistent way of categorizing content
 |
| </li>
 |
| <li>
 |
| Method authors and delivery practitioners can find related content more easily and reference it
 |
| </li>
 |
| <li>
 |
| Published configurations will have the same look and feel to the delivery practitioner making the web site easier
 |
| to navigate and information easier to find
 |
| </li>
 |
| <li>
 |
| Delivery practitioners will require less education and training on the set of configurations with which they work
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| For recommendations on naming custom categories, 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>.
 |
| </p>
 |
| <p>
 |
| Be sure to capture the purpose of the custom category in its description, so that the reason the custom category was
 |
| created and what it contains is maintained.&nbsp;This will make it easy for other method authors to understand when the
 |
| category should be used.
 |
| </p>
 |
| <p>
 |
| Custom categories cannot be packaged in separate packages in plug-ins.&nbsp;Thus alternative categorization schemes
 |
| must be defined in separate plug-ins.
 |
| </p>
 |
| <p>
 |
| For more information on defining navigation views, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/defining_navigation_views_76A906E.html"
 |
| guid="_67agUEyEEdu4NY1n_hCY0w">Guideline: Defining Navigation Views</a>.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
