| <?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="-yVQcZlwHTZIT9-i97PVUYQ" |
| name="test_discipline,_iGSHtlZ-EdyIUdvDLLUdeg" guid="-yVQcZlwHTZIT9-i97PVUYQ" |
| changeDate="2009-07-29T21:10:07.069+0200" version="7.2.0"> |
| <mainDescription><p> |
| The purpose of this discipline is to: |
| </p> |
| <ul> |
| <li> |
| Provide early and frequent <em>feedback</em> about whether the system satisfies the requirements |
| </li> |
| <li> |
| Objectively measure progress in small increments |
| </li> |
| <li> |
| Identify issues with the solution, increasing the probability that the system will behave correctly |
| </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" to retire |
| risks as early as possible in the system's lifecycle. |
| </p> |
| <p> |
| Testing occurs in each iteration of the lifecycle, beginning with the earliest builds of the system. In fact, it is |
| 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> 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 by using concrete demonstration and impartial evaluation. |
| </p> |
| <p> |
| The Test discipline relates to the other disciplines in the following ways: |
| </p> |
| <ul> |
| <li> |
| The <a class="elementLink" |
| href="./../../core.default.cat_def.base/disciplines/requirements_discipline_9520664.html" |
| guid="_iGSHtVZ-EdyIUdvDLLUdeg">Requirements</a> discipline 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> |
| The <a class="elementLink" |
| href="./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html" |
| guid="_iGSHsVZ-EdyIUdvDLLUdeg">Development</a> discipline 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> |
| The <a class="elementLink" |
| href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html" |
| guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a> discipline 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> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |