| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_FuQswLv-EdmmUvZAZjqE3g" |
| name="test,_0TkKQMlgEdmt3adZL5Dmdw" guid="_FuQswLv-EdmmUvZAZjqE3g" changeDate="2007-07-24T11:14:40.953-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| The purpose of this discipline is to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Provide early and frequent <em>feedback</em> that the system satisfies the requirements
 |
| </li>
 |
| <li>
 |
| Objectively measure progress in small increments
 |
| </li>
 |
| <li>
 |
| Identify issues with the solution
 |
| </li>
 |
| <li>
 |
| Provide assurance that changes to the system do not introduce new defects
 |
| </li>
 |
| <li>
 |
| Improve velocity by facilitating the discovery of issues with requirements, designs, and implementations as early
 |
| as possible
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The Test discipline is iterative and incremental. It applies the strategy of “test early and test often” in order to
 |
| retire risks as early in the system’s lifecycle as possible.
 |
| </p>
 |
| <p>
 |
| Testing occurs in each iteration of the lifecycle, beginning with the earliest builds of the system. In fact, it’s
 |
| common for one iteration to have many test cycles, depending on the frequency of new builds.
 |
| </p>
 |
| <p>
 |
| Testing asks the question: “What does the Solution have to <em>do</em> in order for us to consider a requirement
 |
| implemented?” Tests elaborate on the requirements with specific conditions of satisfaction that the Solution must meet.
 |
| </p>
 |
| <p>
 |
| This discipline challenges the assumptions, risks, and uncertainty inherent in the development of highly technical
 |
| artifacts, and addresses those concerns using concrete demonstration and impartial evaluation.
 |
| </p>
 |
| <p>
 |
| The Test discipline relates to the other disciplines in the following ways:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a href="./../../openup/disciplines/requirements.html" guid="_0TR2ZMlgEdmt3adZL5Dmdw">Discipline: Requirements</a>
 |
| identifies the <em>intent</em> of the system. Testing elaborates on the requirements with detailed tests that
 |
| measure how the system supports the requirements.
 |
| </li>
 |
| <li>
 |
| <a href="./../../openup/disciplines/development.html" guid="_0TeDoMlgEdmt3adZL5Dmdw">Discipline: Development</a>
 |
| creates incremental builds of the system that the Test discipline evaluates. In each iteration, testing provides
 |
| objective feedback. Effective testing enables Developers to focus on implementing new functionality, and improving
 |
| the design of the system.
 |
| </li>
 |
| <li>
 |
| <a href="./../../openup/disciplines/project_management.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Discipline: Project
 |
| Management</a> plans the overall project, and the scope of work, for each iteration. The Test discipline provides
 |
| an objective measure of progress, which enables adaptive planning.
 |
| </li>
 |
| <li>
 |
| <a href="./../../openup/disciplines/config_and_change_management.html" guid="_0TwXgMlgEdmt3adZL5Dmdw">Discipline:
 |
| Configuration and Change Management</a> controls changes within the project. The test effort verifies that each
 |
| change to the Solution is tested appropriately. Test assets are kept under configuration management.
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
