| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="_FuQswLv-EdmmUvZAZjqE3g" name="test,_0TkKQMlgEdmt3adZL5Dmdw" guid="_FuQswLv-EdmmUvZAZjqE3g" changeDate="2006-09-29T09:24:16.091-0700" version="1.0.0"> |
| <mainDescription><p> |
| The purpose of this discipline is to: |
| </p> |
| <ul> |
| <li> |
| Find and document defects. |
| </li> |
| <li> |
| Validate and prove the assumptions made in design and requirement specifications through concrete demonstration. |
| </li> |
| <li> |
| Validate that the software product works as designed. |
| </li> |
| <li> |
| Validate that the requirements are implemented appropriately. |
| </li> |
| </ul> |
| <p> |
| A good test effort is based on the philosophy of test early and test often. In addition, it is driven by questions such |
| as: |
| </p> |
| <ul> |
| <li> |
| How could this software break? |
| </li> |
| <li> |
| In what possible situations could this software fail to work predictably? |
| </li> |
| </ul> |
| <p> |
| Testing challenges the assumptions, risks, and uncertainty inherent in the work of other disciplines, and addresses |
| those concerns using concrete demonstration and impartial evaluation. |
| </p> |
| <p> |
| The Test discipline is related to the other disciplines in the following ways: |
| </p> |
| <ul> |
| <li> |
| The <a class="elementLinkWithUserText" href="./../../openup_basic/disciplines/requirements,_0TR2ZMlgEdmt3adZL5Dmdw.html" guid="_0TR2ZMlgEdmt3adZL5Dmdw">Requirements</a> discipline captures requirements for the software product, which is |
| one of the primary inputs for identifying what tests to perform. |
| </li> |
| <li> |
| The <a class="elementLinkWithUserText" href="./../../openup_basic/disciplines/analysis_and_design,_0TX9AMlgEdmt3adZL5Dmdw.html" guid="_0TX9AMlgEdmt3adZL5Dmdw">Analysis and Design</a> discipline determines the appropriate design for the |
| software product, which is another important input for identifying what tests to perform. |
| </li> |
| <li> |
| The <a class="elementLinkWithUserText" href="./../../openup_basic/disciplines/implementation,_0TeDoMlgEdmt3adZL5Dmdw.html" guid="_0TeDoMlgEdmt3adZL5Dmdw">Implementation</a> discipline produces builds of the software product that are |
| validated by the Test discipline. Within an iteration, multiple builds will be tested - typically one per test |
| cycle. |
| </li> |
| <li> |
| The <a class="elementLinkWithUserText" href="./../../openup_basic/disciplines/project_management,_0TqQ4MlgEdmt3adZL5Dmdw.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a> discipline plans the project and the necessary work in each |
| iteration. Described in an Iteration Plan, this artifact is an important input used when you define the correct |
| evaluation mission for the test effort. |
| </li> |
| <li> |
| The <a class="elementLinkWithUserText" href="./../../openup_basic/disciplines/config_and_change_management,_0TwXgMlgEdmt3adZL5Dmdw.html" guid="_0TwXgMlgEdmt3adZL5Dmdw">Configuration and Change Management</a> discipline controls changes within the |
| project. The test effort verifies that each change has been completed appropriately. Test assets are kept |
| under&nbsp;configuration management.<br /> |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |