| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ProcessDescription 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="_mtb-6vL5Edm6Nvont3uinw" |
| guid="_mtb-6vL5Edm6Nvont3uinw" version="1.0.0"> |
| <mainDescription><p>
 |
| 
 |
| This activity is repeated throughout the project lifecycle. The main goal of this activity is to validate that the
 |
| 
 |
| current build of the system satisfies the requirements allocated to it.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| Throughout the iterations, your intent is to validate that the implemented requirements reflect a robust
 |
| 
 |
| architecture, and that the remaining requirements are consistently implemented on top of that architecture. As
 |
| 
 |
| developers implement the solution for the requirements in a given iteration, unit test the integrated source code.
 |
| 
 |
| Then, a <a class="elementlinkwithusertext" href="./../../openup/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">tester</a> conducts system-level testing in parallel with development to make sure that
 |
| 
 |
| the solution, which is continuously being integrated, satisfies the intent specified in the test cases. The tester
 |
| 
 |
| defines what techniques to use, what the data input is, and what <a class="elementLinkWithUserText" href="./../../openup/guidances/guidelines/test_suite_D54EEBED.html" guid="_0aDz0MlgEdmt3adZL5Dmdw">test suites</a> to
 |
| 
 |
| create. As tests run, defects are identified and added to the <a class="elementLinkWithUserText" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">work items list</a>, so
 |
| 
 |
| that they can be prioritized as part of the work that you will do during iterations.
 |
| 
 |
| </p>
 |
| 
 |
| <p>
 |
| 
 |
| <a class="elementLinkWithType" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Role: Stakeholder</a>s and end-users also may also be involved in performing tests to accept the release.
 |
| 
 |
| </p></mainDescription> |
| <keyConsiderations><p> 
 |
| 
 |
| 
 |
| 
 |
| 
 |
| 
 |
| </p></keyConsiderations> |
| <purpose>Develop and run test scripts to validate that the system satisfies the requirements.</purpose> |
| <howtoStaff><p>
 |
| The staff performing this activity must be integrated into the team.
 |
| </p></howtoStaff> |
| <usageNotes><p>
 |
| Testing must occur throughout the process and throughout each iteration. Testing is not a final inspection to be performed at the
 |
| end of the project. As requirements are implemented and integrated into a build, you should test them as soon as possible.
 |
| </p></usageNotes> |
| </org.eclipse.epf.uma:ProcessDescription> |
