<?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" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-yVQcZlwHTZIT9-i97PVUYQ" name="test_discipline,_iGSHtlZ-EdyIUdvDLLUdeg" guid="-yVQcZlwHTZIT9-i97PVUYQ" changeDate="2009-07-29T00:10:07.000-0700" version="7.2.0">
  <mainDescription>&lt;p>&#xD;
    The purpose of this discipline is to:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Provide early and frequent &lt;em>feedback&lt;/em> about whether the system satisfies the requirements&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Objectively measure progress in small increments&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify issues with the solution, increasing the probability that the system will behave correctly&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Provide assurance that changes to the system do not introduce new defects&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Improve velocity by facilitating the discovery of issues with requirements, designs, and implementations as early&#xD;
        as possible&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    The Test discipline is iterative and incremental. It applies the strategy of &quot;test early and test often&quot; to retire&#xD;
    risks as early as possible in the system's lifecycle.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Testing occurs in each iteration of the lifecycle, beginning with the earliest builds of the system. In fact, it is&#xD;
    common for one iteration to have many test cycles, depending on the frequency of new builds.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Testing asks the question: &quot;What does the solution have to &lt;em>do&lt;/em> for us to consider a requirement implemented?&quot;&#xD;
    Tests elaborate on the requirements with specific conditions of satisfaction that the solution must meet.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    This discipline challenges the assumptions, risks, and uncertainty inherent in the development of highly technical&#xD;
    artifacts and addresses those concerns by using concrete demonstration and impartial evaluation.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The Test discipline relates to the other disciplines in the following ways:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/requirements_discipline_9520664.html&quot;&#xD;
        guid=&quot;_iGSHtVZ-EdyIUdvDLLUdeg&quot;>Requirements&lt;/a> discipline identifies the &lt;em>intent&lt;/em> of the system. Testing&#xD;
        elaborates on the requirements with detailed tests that measure how the system supports the requirements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html&quot;&#xD;
        guid=&quot;_iGSHsVZ-EdyIUdvDLLUdeg&quot;>Development&lt;/a> discipline creates incremental builds of the system that the Test&#xD;
        discipline evaluates. In each iteration, testing provides objective feedback. Effective testing enables developers&#xD;
        to focus on implementing new functionality and improving the design of the system.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html&quot;&#xD;
        guid=&quot;_iGSHtFZ-EdyIUdvDLLUdeg&quot;>Project Management&lt;/a> discipline plans the overall project and the scope of work&#xD;
        for each iteration. The Test discipline provides an objective measure of progress, which enables adaptive planning.&#xD;
    &lt;/li>&#xD;
&lt;/ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
