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