<?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="-nrz-IicWH5L_Tq9NhtzBSA" name="programming_and_test_manual,_qinbcLjYEe2ItPaV9bHRfA" guid="-nrz-IicWH5L_Tq9NhtzBSA" changeDate="2023-03-05T22:45:30.963+0330">
  <mainDescription>Product documentation is created for the benefit of the marketing arm of an organization, the program manager, and those&#xD;
people who must assess the business value of a particular system. &#xD;
&lt;p>&#xD;
    This is an often overlooked aspect of development team implementation. The team should consider that the customers of a&#xD;
    particular release usually are not technical themselves, but do require a detailed enough understanding of how their&#xD;
    product operates and how it meets stated business goals and needs.&#xD;
&lt;/p></mainDescription>
  <purpose>The purpose of this work product is to provide documentation about the product for a product owner and their constituents&#xD;
to be able to manage the product during its development and after the project is completed.</purpose>
</org.eclipse.epf.uma:ArtifactDescription>
