| <?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.3/uma.ecore" xmi:id="_0FDb4BUJEdqrUt4zetC1gg" name="work_product,_0ErBYBUJEdqrUt4zetC1gg" guid="_0FDb4BUJEdqrUt4zetC1gg" changeDate="2006-04-13T15:27:03.074-0700"> |
| <mainDescription><p> |
| A Work Product is an abstract concept which provides a generalization for the concrete work product types <a |
| class="elementLink" href="./../../base_concepts/guidances/concepts/artifact,_fdRfkBUJEdqrUt4zetC1gg.html" |
| guid="_fdRfkBUJEdqrUt4zetC1gg">Artifact</a>, <a class="elementLink" |
| href="./../../base_concepts/guidances/concepts/outcome,_pROF4BUJEdqrUt4zetC1gg.html" |
| guid="_pROF4BUJEdqrUt4zetC1gg">Outcome</a>, and <a class="elementLink" |
| href="./../../base_concepts/guidances/concepts/deliverable,_lBgkMBUJEdqrUt4zetC1gg.html" |
| guid="_lBgkMBUJEdqrUt4zetC1gg">Deliverable</a>. Work Product descriptions actually represents work product types, i.e. |
| an instance of Work Product is a description of a specific type of work product and not an individual work product |
| instance.&nbsp; However, for simplicity reasons and because of low risk of misinterpretation we did not append the word |
| 'type' to every element in UMA. |
| </p> |
| <p> |
| A Work Product is an abstraction for descriptions of content elements that are used to define anything used, produced, |
| or modified by a task.&nbsp; Roles use Work Products to perform Tasks and produce Work Products in the course of |
| performing Tasks.&nbsp; Work Products are the responsibility of a single Role, making responsibility easy to identify |
| and understand, and promoting the idea that every piece of information produced in the method requires the appropriate |
| set of skills. Even though one Role might "own" a specific type of Work Products, other Roles can still use the Work |
| Products; perhaps even update them if the Role has been given permission to do so. |
| </p> |
| <p align="center"> |
| <img height="569" |
| alt="Popular Work Products in Software Development, and the approximate dependency relationships between them" |
| src="./../guidances/concepts/resources/overview.gif" width="536" border="0" /> |
| </p> |
| <p class="picturetext" align="center"> |
| Popular Work Products in Software Development, and the approximate dependency relationships between them. |
| </p> |
| <p> |
| Note that Work Product is the term used to describe what other processes denote using terms such as Artifact, work |
| unit, and so on. In UMA, Deliverables are only considered to be the subsets of all Work Products that will end up being |
| delivered into the hands of the customers and users, usually as part of a formal or contractually agreed hand-over. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |