OpenUP/OpenUP_SP/library/openup_basic/capabilitypatterns/manage_requirements/content.xmi

<?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>&lt;p&gt;
    This activity describes the tasks performed to&amp;nbsp;gather, specify, analyze and&amp;nbsp;validate&amp;nbsp;a subset of
    system's&amp;nbsp;requirements&amp;nbsp;prior to&amp;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 &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Stakeholder&lt;/a&gt;s and the entire development team collaborating to ensure that a clear,
    consistent, correct, verifiable, and feasible&amp;nbsp;set of requirements&amp;nbsp;is available, as needed, to drive
    implementation and verification.
&lt;/p&gt;
&lt;p&gt;
    During Inception, the focus is on&amp;nbsp;gaining agreement on&amp;nbsp;the problem to be solved, gathering stakeholder needs
    and capturing high-level system features&amp;nbsp;(see activity &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/capabilitypatterns/initiate_project,_0pWNA8lgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0pWNA8lgEdmt3adZL5Dmdw&quot;&gt;Initiate Project&lt;/a&gt;).
&lt;/p&gt;
&lt;p&gt;
    During Elaboration, the focus shifts to defining the solution. This consists of&amp;nbsp;finding those requirements that
    have most value to stakeholders, that are particularly challenging or risky, or that are architecturally significant
    (See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/tasks/find_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ.html&quot; guid=&quot;_P9cMUPV_EdmdHa9MmVPgqQ&quot;&gt;Task: Find and Outline Requirements&lt;/a&gt;).&amp;nbsp;Requirements&amp;nbsp;that
    are&amp;nbsp;prioritized, via the &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html&quot; guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;&gt;Work Items List&lt;/a&gt;,&amp;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 &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/tasks/detail_requirements,_0e1mIMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0e1mIMlgEdmt3adZL5Dmdw&quot;&gt;Task: Detail Requirements&lt;/a&gt;). 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 &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/tasks/create_test_case,_0iwc0clgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0iwc0clgEdmt3adZL5Dmdw&quot;&gt;Task: Create Test Cases&lt;/a&gt;).
&lt;/p&gt;
&lt;p&gt;
    During Construction, the focus shifts to refining the system definition&lt;em&gt;.&lt;/em&gt; This consists of detailing the
    remaining requirements and associated test cases as needed to drive implementation and verification, and managing
    requirements change (see&amp;nbsp;activity &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/capabilitypatterns/ongoing_tasks,_0pJ_xslgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0pJ_xslgEdmt3adZL5Dmdw&quot;&gt;Ongoing Tasks&lt;/a&gt;).
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ProcessDescription>