<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-6aefH1sLUsOce-dQonmeXg" name="new_custom_category,_Jfu6YEOTEdyBesJ014vxrg" guid="-6aefH1sLUsOce-dQonmeXg" authors="John D. McGregor" changeDate="2007-08-06T09:55:00.000-0400">
  <mainDescription>&lt;p>
    Testing is a category of software development activities. These activities are related and ordered in that each
    activity occurs at a specific point in the development process and builds on the previous testing activities but it
    also has a relationship to the other development activities that have occurred since the last testing activity. The
    figure below puts a set of testing activities into context with other development activities.
&lt;/p>
&lt;p>
    This set of web pages provides an overview of testing activities for a software product line. The activities are
    basically the same as in a non-product line method but the emphasis shifts more toward the front end of the development
    process.
&lt;/p>
&lt;p>
    &lt;img style=&quot;WIDTH: 702px; HEIGHT: 523px&quot; height=&quot;600&quot; alt=&quot;&quot; src=&quot;resources/testingPic.png&quot; width=&quot;600&quot; />
&lt;/p>&lt;br /></mainDescription>
  <keyConsiderations>The core assets used in a product line are used in multiple products, each of which varies from the others in some way.
Testing in a product line has to address this range of use.</keyConsiderations>
</org.eclipse.epf.uma:ContentDescription>
