| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html |
| PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html lang="en-us" xml:lang="en-us"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| <meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" /> |
| <meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" /> |
| <meta name="security" content="public" /> |
| <meta name="Robots" content="index,follow" /> |
| <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> |
| <meta name="DC.Type" content="concept" /> |
| <meta name="DC.Title" content="Method Content Categories" /> |
| <meta name="DC.Relation" scheme="URI" content="methodcontent.html#creatingreusablemethodcontents" /> |
| <meta name="DC.Relation" scheme="URI" content="createmethodcontent.html#createmethodcontent" /> |
| <meta name="DC.Relation" scheme="URI" content="methodcontentpackage.html#methodcontentpackage" /> |
| <meta name="DC.Format" content="XHTML" /> |
| <meta name="DC.Identifier" content="methodcontentcategories" /> |
| <meta name="DC.Language" content="en-us" /> |
| <!-- |
| Copyright (c) 2005, 2006 IBM Corporation and others. |
| All rights reserved. This program and the accompanying materials |
| are made available under the terms of the Eclipse Public License v1.0 |
| which accompanies this distribution, and is available at |
| http://www.eclipse.org/legal/epl-v10.html |
| Contributors: |
| IBM Corporation - initial implementation |
| --> |
| <link rel="stylesheet" type="text/css" href="./ibmdita.css" /> |
| <title>Method Content Categories</title> |
| </head> |
| <body id="methodcontentcategories"><a name="methodcontentcategories"><!-- --></a> |
| |
| <h1 class="topictitle1">Method Content Categories</h1> |
| <div><p>Method Content elements are organized into logical categories. The categories |
| can appear in your final, published Web site as views.</p> |
| <p>There are two types of category: Standard and Custom.</p> |
| <p></p> |
| <div class="section"><h4 class="sectiontitle">Standard Categories</h4><p>Standard Categories provide |
| a means to categorize core method content in line with the best practices |
| for creating structured methods. Standard Categories are linked with a specific |
| method content type, e.g. Disciplines contain only tasks. </p> |
| <div class="p">Standard |
| Category types are:<ul><li><strong>Disciplines</strong> - A discipline is a collection of <a href="task.html#task">Tasks</a> that are related to a major area of concern within |
| the overall IT environment. For example, on a software development project, |
| it is common to perform certain requirements tasks in close coordination with |
| analysis and design tasks. Separating these tasks into separate disciplines |
| makes the tasks easier to comprehend. Disciplines can be organized using Discipline |
| Groupings.</li> |
| <li><strong>Domains</strong> - A Domain is a refineable, logical, hierarchy of related <a href="workproduct.html#workproduct">Work Products</a> grouped |
| together based on timing, resources, or relationship. While a Domain categorizes |
| many work products, a work product belongs to only one Domain. Domains can |
| be further divided into sub-domains. </li> |
| <li><strong>Work Product Kinds</strong> - Work Product Kind is another category for |
| grouping <a href="workproduct.html#workproduct">Work Products</a>. |
| A work product can have many work product kinds. As an example, you might |
| want to have a series of work product kinds that correspond to the overall |
| intent of work products, such as specification, plan, or model.</li> |
| <li><strong>Role Sets</strong> - A Role Set is used to group <a href="role.html#role">Roles</a> with certain commonalities together. For example, |
| in a software development environment, an Analyst role set could be used to |
| group together roles such as Business Process Analyst, System Analyst and |
| Requirements Specifier. Each of these roles work with similar techniques and |
| have overlapping skills, but may be responsible for performing certain tasks |
| and creating certain work products. Role sets can be organized using Role |
| Set Groupings.</li> |
| <li><strong>Tools</strong> - Tools is a container for <a href="toolmentor.html#toolmentor">Tool Mentors</a>. Tools can also provide general descriptions |
| of a tool and it's general capabilities.</li> |
| </ul> |
| </div> |
| </div> |
| <div class="section"><h4 class="sectiontitle">Custom Categories</h4><p>Custom Categories are highly customizable |
| and can contain any type of element. Custom Categories allow you to categorize |
| content according to any scheme you want and can then be used to compose publishable |
| Views, providing a means to organize the method content prior to publishing. |
| For example, you could create a custom category 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> |
| </div> |
| </div> |
| <div><div class="relconcepts"><strong>Related concepts</strong><br /> |
| <div><a href="methodcontent.html#creatingreusablemethodcontents">Method Content</a></div> |
| <div><a href="methodcontentpackage.html#methodcontentpackage">Method Content Package</a></div> |
| </div> |
| <div class="reltasks"><strong>Related tasks</strong><br /> |
| <div><a href="createmethodcontent.html#createmethodcontent">Create Method Content</a></div> |
| </div> |
| </div> |
| </body> |
| </html> |