<?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>&lt;p&gt;
    Work Products may take various shapes or forms, such as:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        A &lt;b&gt;model&lt;/b&gt;, such as the Use-Case Model or the Design Model, which contains other Artifacts.
    &lt;/li&gt;
    &lt;li&gt;
        A &lt;b&gt;model element&lt;/b&gt;; that is, an element within a model, such as a Design Class, a Use-Case or a Design
        Subsystem.
    &lt;/li&gt;
    &lt;li&gt;
        &lt;strong&gt;Project data&lt;/strong&gt; that might be kept in databases or other types of tabular information repositories
        such as spreadsheets.
    &lt;/li&gt;
    &lt;li&gt;
        Source code and executable programs&amp;nbsp;that contribute to the product or &lt;strong&gt;Solution.&lt;/strong&gt;
    &lt;/li&gt;
    &lt;li&gt;
        Various types of documents, for example a &lt;strong&gt;specification&lt;/strong&gt; document&lt;strong&gt;,&lt;/strong&gt; such as
        Requirements Specification, or a &lt;strong&gt;plan&lt;/strong&gt; document, such as the Software Requirements Plan.
    &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
    They can therefore be categorized accordingly. An example is &quot;&lt;strong&gt;Specification&lt;/strong&gt;&quot;, 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.
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>