| <?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="-So8Z4A5pkueW-mFMOnfyHA" |
| name="basic_process_concepts.kellih,_M3zToF_eEd2zpKtX6B7lBg" guid="-So8Z4A5pkueW-mFMOnfyHA" |
| changeDate="2008-08-01T08:28:26.500-0700" version="7.5.0"> |
| <mainDescription><h3>
 |
| The Basic Elements
 |
| </h3>
 |
| <p>
 |
| The basic elements of a process website are:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Work product</strong>: what is produced
 |
| </li>
 |
| <li>
 |
| <strong>Task</strong>: how to perform the work
 |
| </li>
 |
| <li>
 |
| <strong>Role</strong>: who performs the work
 |
| </li>
 |
| <li>
 |
| <strong>Process</strong>: used to define work breakdown and workflow
 |
| </li>
 |
| <li>
 |
| <strong>Guidance</strong>: templates, checklists, examples, guidelines. concepts, …
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| These "basic elements" are the building blocks from which processes are composed.
 |
| </p>
 |
| <h3>
 |
| Organizing Elements
 |
| </h3>
 |
| <p>
 |
| The basic elements are organized/grouped using the following elements: a <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_library_6E08F9E5.html"
 |
| guid="_1xELEMaFEduMlb2cQZNTYw">method library</a>, which includes <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html"
 |
| guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-in</a>s and <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
 |
| guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a>s.&nbsp;
 |
| </p>
 |
| <p>
 |
| Plug-ins consist of <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">roles</a>, <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">tasks</a>, <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a>, <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
 |
| guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>, <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
 |
| guid="_2RUJACO4EdqaNq6Ptg8uyA">capability patterns</a> and <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
 |
| guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery processes</a>. Plug-ins may be futher organized using content packages. For
 |
| example, all content related to a specific content area may be placed in the same content package. Each of these
 |
| packages might be further divided into sub-packages representing sub-topics. For example,&nbsp;within a specific
 |
| development content package,&nbsp;you may want to&nbsp;have a sub-package that&nbsp;includes specific information about
 |
| visual modeling.
 |
| </p>
 |
| <p>
 |
| From the end-user perspective, a <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
 |
| guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a>&nbsp;is a selection of <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_element_A8EA8685.html"
 |
| guid="_4svVUO7bEdyYoPJ0YfnNbQ">method element</a>s to be published.&nbsp;The published configuration is often loosely
 |
| referred to as a process website.&nbsp; Internally, configurations are a selection of plug-ins and content packages,
 |
| along with (optionally) a set of navigation views.&nbsp; Taking the earlier example a little futher, you can add or
 |
| remove&nbsp;visual modeling&nbsp;specifics from&nbsp;a configuration by just including or excluding the visual modeling
 |
| content package to/from the configuration.&nbsp;
 |
| </p>
 |
| <h3>
 |
| Details and Examples
 |
| </h3>
 |
| <p>
 |
| The following provides more detail about the basic elements and provides some examples.
 |
| </p>
 |
| <h4>
 |
| Work product
 |
| </h4>
 |
| <p>
 |
| <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
 |
| guid="_H4JXwB_SEdq6CKKKq4D7YA">Work products</a> may take various shapes or forms, such as:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Documents, such as a Vision, or a Project Plan.
 |
| </li>
 |
| <li>
 |
| A model, such as a Use-Case Model or a Design Model. These can contain model elements (sub-artifacts) such as
 |
| Design Classes, Use Cases, and Design Subsystems.
 |
| </li>
 |
| <li>
 |
| Databases, spreadsheets, and other information repositories.
 |
| </li>
 |
| <li>
 |
| Source code and executables.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Work products can be classified as "artifacts" if they are concrete things, "outcomes" if they are not concrete, and
 |
| "deliverables" if they are a packaging of artifacts.
 |
| </p>
 |
| <h4>
 |
| Role
 |
| </h4>
 |
| <p>
 |
| A <a class="elementLink" href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
 |
| guid="_yUefQNnmEdmO6L4XMImrsA">role</a>&nbsp;defines the behavior and responsibilities of an individual, or a set of
 |
| individuals working together as a team, within the context of a software engineering organization.<br />
 |
| Note that roles are not individuals; instead, roles describe responsibilities. An individual will typically take on
 |
| several roles at one time, and frequently will change roles over the duration of the project.
 |
| </p>
 |
| <p>
 |
| Some examples:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Analyst&nbsp;-</strong>&nbsp;Represents customers and end users, gathers input from stakeholders and
 |
| defines requirements.
 |
| </li>
 |
| <li>
 |
| <strong>Developer -</strong> Develops a part of the system, including designing, implementing, unit testing, and
 |
| integrating.
 |
| </li>
 |
| </ul>
 |
| <h4>
 |
| Task
 |
| </h4>
 |
| <p>
 |
| A <a class="elementLink" href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>&nbsp;is work performed by a role. It is usually defined as a series of steps
 |
| that involve creating or updating one or more work products.
 |
| </p>
 |
| <p>
 |
| Some examples:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Develop a vision -</strong> Develop an overall vision for the system, including capturing the problem to be
 |
| solved, the key stakeholders, the scope/boundary of the system, the system's key features, and any constraints.
 |
| </li>
 |
| <li>
 |
| <strong>Plan Iteration -</strong> Define the scope and responsibilities of a single iteration.
 |
| </li>
 |
| </ul>
 |
| <h4>
 |
| Guidance
 |
| </h4>
 |
| <p>
 |
| <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
 |
| guid="_83ttAB_NEdq6CKKKq4D7YA">Guidance</a> can be associated to any method element and comes in a number of different
 |
| varieties, each with their own specific characteristics (e.g., <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/checklist_D780FDF.html"
 |
| guid="_7vpJsMaCEduMlb2cQZNTYw">checklist</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/concept_BE0CD51D.html"
 |
| guid="_wMchYMaEEduMlb2cQZNTYw">concept</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/example_9C7688B0.html"
 |
| guid="_nE6fsMaFEduMlb2cQZNTYw">example</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guideline_1D590B95.html"
 |
| guid="_uK8HMMaFEduMlb2cQZNTYw">guideline</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/practice_94B5C550.html"
 |
| guid="_wxYvkMaGEduMlb2cQZNTYw">practice</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/report_701DB2E0.html"
 |
| guid="_bDCXUMaHEduMlb2cQZNTYw">report</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/reusable_asset_C02B1B80.html"
 |
| guid="_kSKZUMaHEduMlb2cQZNTYw">reusable asset</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/roadmap_466C36E0.html"
 |
| guid="_19dWYMaHEduMlb2cQZNTYw">roadmap</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/supporting_material_F91C8C5B.html"
 |
| guid="_SwvUgMaIEduMlb2cQZNTYw">supporting material</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/template_53432085.html"
 |
| guid="_1MLN8MaIEduMlb2cQZNTYw">template</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/term_definition_96553AFC.html"
 |
| guid="_6SluIMaIEduMlb2cQZNTYw">term definition</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/tool_mentor_264766F3.html"
 |
| guid="_yYy-mdnmEdmO6L4XMImrsA">tool mentor</a>, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/white_paper_7231747.html"
 |
| guid="_Kc1IIMaJEduMlb2cQZNTYw">white paper</a>, etc.)<br />
 |
| </p>
 |
| <h4>
 |
| Process
 |
| </h4>
 |
| <p>
 |
| <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/process_68E308B4.html"
 |
| guid="_yQ5m2NnmEdmO6L4XMImrsA">Processes</a> pull together tasks, work products, and roles, and add structure and
 |
| sequencing information.&nbsp; Tasks or work products can be grouped into higher level activities, called a work <a
 |
| class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/breakdown_structure_C53514C1.html"
 |
| guid="_95LCoB_QEdq6CKKKq4D7YA">breakdown structure</a>(WBS).&nbsp;&nbsp;Activities or tasks can be marked as "planned"
 |
| to identify work that you expect to assign and track.
 |
| </p><br />
 |
| <br />
 |
| <center>
 |
| <img
 |
| alt="This is an example work breakdown structure, showing a hierarchy of activities with sub-activities and tasks."
 |
| src="./resources/wbs_example.jpg" align="center" />&nbsp;<br />
 |
| Figure 1: Example Work Breakdown
 |
| </center><br />
 |
| <br />
 |
| <p>
 |
| Diagrams can be added to providing sequencing information.&nbsp; The following example shows an initial activity, "Plan
 |
| Test Cycle", followed by two activities that go in parallel, "Monitor and Control Test" and "Test".
 |
| </p><br />
 |
| <br />
 |
| <center>
 |
| <img height="453"
 |
| alt="Example UML activity diagram, showing a start, an initial activity, then two activities in parallel, and an end."
 |
| src="./resources/activity_diag_ex.jpg" width="566" align="center" /><br />
 |
| Figure&nbsp;2: Example Activity Diagram
 |
| </center><br />
 |
| <br />
 |
| <p>
 |
| Note that a&nbsp;reusable partial process is sometimes referred to as a <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
 |
| guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>, whereas a more complete, end-to-end process is sometimes
 |
| referred to as a <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
 |
| guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery process</a>.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
