OpenUP/OpenUP_baseline_EN/library/openup_basic/tasks/find_and_outline_requirements.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription 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="_P9iS8PV_EdmdHa9MmVPgqQ" name="find_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ" guid="_P9iS8PV_EdmdHa9MmVPgqQ" changeDate="2006-09-29T15:32:02.476-0700" version="1.0.0">
  <keyConsiderations>Close collaboration with stakeholders on this task is critical for the success of project.</keyConsiderations>
  <sections xmi:id="_ckG-cCY-EdqNHcQ-rAojXw" name="Gather information" guid="_ckG-cCY-EdqNHcQ-rAojXw">
    <sectionDescription>&lt;p&gt;
    Be prepared by gathering and reviewing information related to the problem domain, problem statement, business
    environment and key stakeholders.&amp;nbsp; Most of this information should be available in the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Vision&lt;/a&gt;.&amp;nbsp;&amp;nbsp;You can use various techniques to make gathering
    requirements easier. Face-to-face meetings with stakeholders is the most effective way to understand stakeholder needs
    and to gather and validate requirements, but you&amp;nbsp;must prepare in order for&amp;nbsp;these meetings to run efficiently.
    See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/req_gathering_techniques,_OnoNQNSAEdmLhZ9H5Plxyw.html&quot; guid=&quot;_OnoNQNSAEdmLhZ9H5Plxyw&quot;&gt;Guideline: Requirements Gathering Techniques&lt;/a&gt;&amp;nbsp;for more information.&amp;nbsp;
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_GAr3IOz3Edq2wJOsmRwmhg" name="Identify and capture domain terms" guid="_GAr3IOz3Edq2wJOsmRwmhg">
    <sectionDescription>Work closely with stakeholder to make sure that ambiguous or domain-specific terms are clearly defined in the&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/workproducts/glossary,_Wn7HcNcEEdqz_d2XWoVt6Q.html&quot; guid=&quot;_Wn7HcNcEEdqz_d2XWoVt6Q&quot;&gt;Glossary&lt;/a&gt; and that you use these terms consistently.</sectionDescription>
  </sections>
  <sections xmi:id="_fDbgkCY-EdqNHcQ-rAojXw" name="Capture requirements" guid="_fDbgkCY-EdqNHcQ-rAojXw">
    <sectionDescription>Identify the types of requirements relevant to your system (see &lt;a class=&quot;elementlinkwithtype&quot; href=&quot;./../../openup_basic/guidances/concepts/requirements,_0Wh-sMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0Wh-sMlgEdmt3adZL5Dmdw&quot;&gt;Concept: Requirements&lt;/a&gt;). 
&lt;p&gt;
    Work with stakeholders to identify and capture&amp;nbsp;the actors and Use Cases. See &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/find_and_outline_actors_and_ucs,_eyL0wCu-EdqSxKAVa9kmvA.html&quot; guid=&quot;_eyL0wCu-EdqSxKAVa9kmvA&quot;&gt;Guideline: Find and Outline Actors and Use Cases&lt;/a&gt;&amp;nbsp;for more information.
&lt;/p&gt;
&lt;p&gt;
    Work with stakeholders to identify and capture&amp;nbsp;the other types of requirements relevant&amp;nbsp;to your system. See
    &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/supporting_requirements,_wr24gNcGEdqz_d2XWoVt6Q.html&quot; guid=&quot;_wr24gNcGEdqz_d2XWoVt6Q&quot;&gt;Guideline: Supporting Requirements&lt;/a&gt;&amp;nbsp;for more information.
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_0WhHsN-eEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_0WhHsN-eEdqiM_wFaqLjNg">
    <sectionDescription>Conduct a review&amp;nbsp;of the&amp;nbsp;requirements with relevant &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Stakeholders&lt;/a&gt;
and the development team to ensure consistency with the &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;&gt;Vision&lt;/a&gt;,
assess quality, and identify any required changes. See&amp;nbsp;&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/effective_req_reviews,_E-dPIL-GEdqb7N6KIeDL8Q.html&quot; guid=&quot;_E-dPIL-GEdqb7N6KIeDL8Q&quot;&gt;Guideline: Effective Requirement Reviews&lt;/a&gt;&amp;nbsp;for more information.</sectionDescription>
  </sections>
  <sections xmi:id="_Mgb9IC4DEduBP8F-6-95NQ" name="Update the Work Items  List" guid="_Mgb9IC4DEduBP8F-6-95NQ">
    <sectionDescription>Capture references to the requirements in the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html&quot; guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;&gt;Artifact: Work Items List&lt;/a&gt;, so that you can prioritize the work.</sectionDescription>
  </sections>
  <purpose>The purpose of this task is to understand Stakeholder requirements and communicate these to the development team.</purpose>
</org.eclipse.epf.uma:TaskDescription>