| <?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-8_L5Edm6Nvont3uinw" |
| guid="_mtb-8_L5Edm6Nvont3uinw" version="1.0.0"> |
| <mainDescription><p>
 |
| This activity describes the tasks you perform to gather, specify, analyze, and validate a subset of
 |
| system's requirements prior to implementation and verification. This does not imply that all
 |
| requirements are detailed prior to commencing implementation. Rather, you perform this activity throughout the
 |
| lifecycle with <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>s and the entire development team collaborating to ensure that a clear,
 |
| consistent, correct, verifiable, and feasible set of requirements is available, as needed, to drive
 |
| implementation and verification.
 |
| </p>
 |
| <p>
 |
| During <b>Inception</b>, the focus is on gaining agreement on the problem to be solved, gathering stakeholder needs,
 |
| and capturing high-level system features (see activity <a class="elementLink" href="./../../openup/capabilitypatterns/initiate_project_D9C03857.html" guid="_0pWNA8lgEdmt3adZL5Dmdw">Initiate Project</a>).
 |
| </p>
 |
| <p>
 |
| During <b>Elaboration</b>, the focus shifts to defining the solution. This consists of finding those requirements that
 |
| have the most value to stakeholders, that are particularly challenging or risky, or that are architecturally significant
 |
| (See <a class="elementLinkWithType" href="./../../openup/tasks/find_and_outline_requirements_90D272B9.html" guid="_P9cMUPV_EdmdHa9MmVPgqQ">Task: Find and Outline Requirements</a>). You then describe requirements (that
 |
| are prioritized, via the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, for implementation in the early iterations) 
 |
| in sufficient detail to validate the development team's understanding of the requirements, to ensure concurrence with
 |
| stakeholders, and to permit software development to begin (see <a class="elementLinkWithType" href="./../../openup/tasks/detail_requirements_9747F71E.html" guid="_0e1mIMlgEdmt3adZL5Dmdw">Task: Detail Requirements</a>). For each of these requirements, define associated test cases to ensure that the
 |
| requirements are verifiable, and to provide the guidance needed for verification and validation (see <a class="elementLinkWithType" href="./../../openup/tasks/create_test_cases_D39E98A1.html" guid="_0iwc0clgEdmt3adZL5Dmdw">Task: Create Test Cases</a>).
 |
| </p>
 |
| <p>
 |
| During Construction, the focus shifts to refining the system definition. This consists of detailing the
 |
| remaining requirements and associated test cases as necessary to drive implementation and verification, and managing
 |
| requirements change (see activity <a class="elementLink" href="./../../openup/capabilitypatterns/ongoing_tasks_91569239.html" guid="_0pJ_xslgEdmt3adZL5Dmdw">Ongoing Tasks</a>).
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ProcessDescription> |