| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-NHao3cbpesderphl_fDlDw" name="product_documentation,_E8QEgEVtEeC6_c5S_pc9RA" guid="-NHao3cbpesderphl_fDlDw" changeDate="2012-05-30T13:55:07.824-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| Product documentation is created for the benefit of the marketing arm of an organization, the program manager, and
 |
| those people who must assess the business value of a particular system.
 |
| </p>
 |
| <p>
 |
| This is an often overlooked aspect of development team implementation. The team should consider that the customers of a
 |
| particular release usually are not technical themselves, but do require a detailed enough understanding of how their
 |
| product operates and how it meets stated business goals and needs.
 |
| </p></mainDescription> |
| <purpose>The purpose of this work product is to provide documentation about the product for a product owner and their constituents
 |
| to be able to manage the product during its development and after the project is completed.</purpose> |
| </org.eclipse.epf.uma:ArtifactDescription> |
