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