| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\disciplines\test.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: test.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_0TkKQMlgEdmt3adZL5Dmdw CRC: 2018365746 -->Test<!-- END:presentationName,_0TkKQMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_0TkKQMlgEdmt3adZL5Dmdw CRC: 2572793515 -->This discipline defines the minimal set of tasks required to plan, implement, run and evaluate the testing of a system.<!-- END:briefDescription,_0TkKQMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_FuQswLv-EdmmUvZAZjqE3g CRC: 1829718713 --><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 configuration management.<br /> |
| </li> |
| </ul><!-- END:mainDescription,_FuQswLv-EdmmUvZAZjqE3g --> |
| </body> |
| </html> |
