| <?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="_VRz4gBUGEdqrUt4zetC1gg" name="work_product_kind,_VRhkoBUGEdqrUt4zetC1gg" guid="_VRz4gBUGEdqrUt4zetC1gg" changeDate="2005-10-14T01:31:27.275-0700"> |
| <mainDescription><p> |
| Work Products may take various shapes or forms, such as: |
| </p> |
| <ul> |
| <li> |
| A <b>model</b>, such as the Use-Case Model or the Design Model, which contains other Artifacts. |
| </li> |
| <li> |
| A <b>model element</b>; that is, an element within a model, such as a Design Class, a Use-Case or a Design |
| Subsystem. |
| </li> |
| <li> |
| <strong>Project data</strong> that might be kept in databases or other types of tabular information repositories |
| such as spreadsheets. |
| </li> |
| <li> |
| Source code and executable programs&nbsp;that contribute to the product or <strong>Solution.</strong> |
| </li> |
| <li> |
| Various types of documents, for example a <strong>specification</strong> document<strong>,</strong> such as |
| Requirements Specification, or a <strong>plan</strong> document, such as the Software Requirements Plan. |
| </li> |
| </ul> |
| <p> |
| They can therefore be categorized accordingly. An example is "<strong>Specification</strong>", which categorizes |
| requirements specifications that define a system with a well-defined system boundary, such as use case or functional |
| requirements specification. Unlike in Domains, a single Work Product can be categorized in multiple Work Product Kinds. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |