| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" |
| "http://www.w3.org/TR/html4/loose.dtd"> |
| <!-- |
| 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 |
| --> |
| |
| <html> |
| <head> |
| <title>Untitled Document</title> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| </head> |
| |
| <body> |
| <h1><a></a><a>Tutorial: Working with Processes </a></h1> |
| <p><strong><em>Process Authoring </em></strong> allows a Process Engineer to incorporate <strong><em>Method Elements </em></strong> into process structures. For example, a Work Breakdown Structure format familiar to Project Managers. The processes can be included in a configuration to be published as part of the published web site. </p> |
| <p>In <strong><em>Method </em> Authoring </strong> the Process Engineer defines roles, tasks, work products and guidance and defines the relationships between these elements. </p> |
| <p>In <strong><em>Process </em> Authoring </strong> the process engineer defines additional lifecycle elements such as <strong>Activities </strong> (summary tasks), <strong>Phases </strong>, <strong>Iterations </strong> and <strong>Milestones </strong>, that can then be used to compose the core elements into processes. A complete process corresponding to a project plan or a phase we call a <strong><em>Delivery Process </em></strong><em>(corresponding to Small RUP, for example) </em>. We can also create smaller more granular sections of process, termed <strong><em>Capability Patterns </em></strong> that can be used as building blocks to more easily compose delivery processes. </p> |
| <p>Each time a task is included in a process, a copy of that task is created in the context of the process. We call this a Task Descriptor. The same task can be included any number of times in the same process. This allows, for example, the same RUP task to be included in each Iteration in each RUP Phase. A Task Descriptor can also modify the base task without actually changing the task. For example, roles and work products can be added or suppressed, steps can be suppressed or re-sequenced. </p> |
| <p>oles and Work Products are also included in processes as Role Descriptors and Work Product Descriptors. So roles and work products can also be customized to fit with the context of the process in which they are used.</p> |
| </body> |
| </html> |
