OpenUP/OpenUP_RU/library/openup_basic/tasks/detail_requirements.xmi - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?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="_Nqwi8KeqEdmKDbQuyzCoqQ" name="detail_requirements,_0e1mIMlgEdmt3adZL5Dmdw" guid="_Nqwi8KeqEdmKDbQuyzCoqQ" changeDate="2006-09-29T15:31:25.226-0700" version="1.0.0">
   <sections xmi:id="_vWeHMCxSEdqjsdw1QLH_6Q" name="Detail Use Cases and Scenarios" guid="_vWeHMCxSEdqjsdw1QLH_6Q">
     <sectionDescription>&lt;p&gt;
     Some &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0VGbUMlgEdmt3adZL5Dmdw&quot;&gt;Use Case&lt;/a&gt;s and Scenarios may need to be described in more detail to validate our
     understanding of the requirement and to permit software development to begin. This does not imply that all&amp;nbsp;use
     cases and scenarios&amp;nbsp;will be detailed prior to commencing implementation.&amp;nbsp;&amp;nbsp;Work with stakeholders to
     detail only those that are prioritized for implementation in the next iteration or two (see &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;), or those that are deemed architecturally significant
     (see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html&quot; guid=&quot;_HrZGIA4MEduibvKwrGxWxA&quot;&gt;Concept: Architecturally Significant Requirements&lt;/a&gt;.)
 &lt;/p&gt;
 &lt;p&gt;
     The level of detail captured will vary depending upon the needs of the project and the complexity of the use
     case.&amp;nbsp; For a discussion of the different levels of detail that may be applicable see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/use_case_formats,_qq0GMAXkEduj_7BEUj1JfQ.html&quot; guid=&quot;_qq0GMAXkEduj_7BEUj1JfQ&quot;&gt;Guideline: Use Case Formats&lt;/a&gt;.
 &lt;/p&gt;
 &lt;p&gt;
     Capture the use case&amp;nbsp;details in &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0VGbUMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Use Case&lt;/a&gt;.&amp;nbsp; For additional information on detailing use cases and scenarios, see&amp;nbsp;&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q.html&quot; guid=&quot;_4BJ_YCxSEdqjsdw1QLH_6Q&quot;&gt;Guideline: Detail Use Cases and Scenarios&lt;/a&gt;.&amp;nbsp; For assistance in assessing the
     quality of your use cases see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/checklists/use_case,_0kNwINk1Edq2Q8qZoWbvGA.html&quot; guid=&quot;_0kNwINk1Edq2Q8qZoWbvGA&quot;&gt;Checklist: Use Case&lt;/a&gt;.
 &lt;/p&gt;</sectionDescription>
   </sections>
   <sections xmi:id="_B47VwCxTEdqjsdw1QLH_6Q" name="Detail supporting requirements" guid="_B47VwCxTEdqjsdw1QLH_6Q">
     <sectionDescription>&lt;p&gt;
     Some&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html&quot; guid=&quot;_BVh9cL-CEdqb7N6KIeDL8Q&quot;&gt;Supporting Requirements&lt;/a&gt; may need to be clarified or described in more detail, new
     requirements&amp;nbsp;may have been discovered as we detailed the use cases and scenarios, and new requirements may have
     been submitted as &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/guidances/concepts/change_requests,_6jdvECb3Edqh1LYUOGRh2A.html&quot; guid=&quot;_6jdvECb3Edqh1LYUOGRh2A&quot;&gt;Change Requests&lt;/a&gt;.&amp;nbsp;Work with stakeholders to capture, refine and validate those
     requirements that will have an impact on near term work (see &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;) or are deemed architecturally significant (see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html&quot; guid=&quot;_HrZGIA4MEduibvKwrGxWxA&quot;&gt;Concept: Architecturally Significant Requirements&lt;/a&gt;).
 &lt;/p&gt;
 &lt;p&gt;
     Capture these requirements in&amp;nbsp;the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html&quot; guid=&quot;_BVh9cL-CEdqb7N6KIeDL8Q&quot;&gt;Artifact: Supporting Requirements&lt;/a&gt;.&amp;nbsp; For additional guidance on detailing
     supporting requirements 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 assistance in assessing the quality of
     your supporting requirements see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/checklists/supporting_requirements,_Vael8CGMEdu3VKXZx45D3A.html&quot; guid=&quot;_Vael8CGMEdu3VKXZx45D3A&quot;&gt;Checklist: Supporting Requirements&lt;/a&gt;.
 &lt;/p&gt;</sectionDescription>
   </sections>
   <sections xmi:id="_2389cOz2Edq2wJOsmRwmhg" name="Detail glossary terms" guid="_2389cOz2Edq2wJOsmRwmhg">
     <sectionDescription>Review the use case&amp;nbsp;flow of events. If information is exchanged, be specific about what is passed back and
 forth.&amp;nbsp; Work with stakeholders to ensure that you define newly discovered domain terms, or ambiguous
 terms&amp;nbsp;properly in the &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;.
 If your understanding of the domain has improved,&amp;nbsp;refine existing glossary terms.</sectionDescription>
   </sections>
   <sections xmi:id="_BYbboN-bEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_BYbboN-bEdqiM_wFaqLjNg">
     <sectionDescription>Conduct a review&amp;nbsp;of the&amp;nbsp;requirements (&lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0VGbUMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Use Case&lt;/a&gt; and &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html&quot; guid=&quot;_BVh9cL-CEdqb7N6KIeDL8Q&quot;&gt;Artifact: Supporting Requirements&lt;/a&gt;)&amp;nbsp;with relevant&amp;nbsp;&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 required changes. See&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>
   <purpose>&lt;p&gt;
     The purpose of this task is to describe one or more requirements&amp;nbsp;in sufficient detail to validate understanding of
     the requirement, to ensure concurrence with stakeholders expectations, and to permit software development&amp;nbsp;to
     begin.
 &lt;/p&gt;</purpose>
 </org.eclipse.epf.uma:TaskDescription>
	<?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="_Nqwi8KeqEdmKDbQuyzCoqQ" name="detail_requirements,_0e1mIMlgEdmt3adZL5Dmdw" guid="_Nqwi8KeqEdmKDbQuyzCoqQ" changeDate="2006-09-29T15:31:25.226-0700" version="1.0.0">
	<sections xmi:id="_vWeHMCxSEdqjsdw1QLH_6Q" name="Detail Use Cases and Scenarios" guid="_vWeHMCxSEdqjsdw1QLH_6Q">
	<sectionDescription><p>
	Some <a class="elementLink" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>s and Scenarios may need to be described in more detail to validate our
	understanding of the requirement and to permit software development to begin. This does not imply that all&nbsp;use
	cases and scenarios&nbsp;will be detailed prior to commencing implementation.&nbsp;&nbsp;Work with stakeholders to
	detail only those that are prioritized for implementation in the next iteration or two (see <a class="elementLinkWithType" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>), or those that are deemed architecturally significant
	(see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html" guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>.)
	</p>
	<p>
	The level of detail captured will vary depending upon the needs of the project and the complexity of the use
	case.&nbsp; For a discussion of the different levels of detail that may be applicable see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/use_case_formats,_qq0GMAXkEduj_7BEUj1JfQ.html" guid="_qq0GMAXkEduj_7BEUj1JfQ">Guideline: Use Case Formats</a>.
	</p>
	<p>
	Capture the use case&nbsp;details in <a class="elementLinkWithType" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a>.&nbsp; For additional information on detailing use cases and scenarios, see&nbsp;<a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q.html" guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: Detail Use Cases and Scenarios</a>.&nbsp; For assistance in assessing the
	quality of your use cases see <a class="elementLinkWithType" href="./../../openup_basic/guidances/checklists/use_case,_0kNwINk1Edq2Q8qZoWbvGA.html" guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: Use Case</a>.
	</p></sectionDescription>
	</sections>
	<sections xmi:id="_B47VwCxTEdqjsdw1QLH_6Q" name="Detail supporting requirements" guid="_B47VwCxTEdqjsdw1QLH_6Q">
	<sectionDescription><p>
	Some&nbsp;<a class="elementLink" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Supporting Requirements</a> may need to be clarified or described in more detail, new
	requirements&nbsp;may have been discovered as we detailed the use cases and scenarios, and new requirements may have
	been submitted as <a class="elementLink" href="./../../openup_basic/guidances/concepts/change_requests,_6jdvECb3Edqh1LYUOGRh2A.html" guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a>.&nbsp;Work with stakeholders to capture, refine and validate those
	requirements that will have an impact on near term work (see <a class="elementLinkWithType" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>) or are deemed architecturally significant (see <a class="elementLinkWithType" href="./../../openup_basic/guidances/concepts/architecturally_significant_requirements,_HrZGIA4MEduibvKwrGxWxA.html" guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>).
	</p>
	<p>
	Capture these requirements in&nbsp;the <a class="elementLinkWithType" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements</a>.&nbsp; For additional guidance on detailing
	supporting requirements see <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/supporting_requirements,_wr24gNcGEdqz_d2XWoVt6Q.html" guid="_wr24gNcGEdqz_d2XWoVt6Q">Guideline: Supporting Requirements</a>.&nbsp; For assistance in assessing the quality of
	your supporting requirements see <a class="elementLinkWithType" href="./../../openup_basic/guidances/checklists/supporting_requirements,_Vael8CGMEdu3VKXZx45D3A.html" guid="_Vael8CGMEdu3VKXZx45D3A">Checklist: Supporting Requirements</a>.
	</p></sectionDescription>
	</sections>
	<sections xmi:id="_2389cOz2Edq2wJOsmRwmhg" name="Detail glossary terms" guid="_2389cOz2Edq2wJOsmRwmhg">
	<sectionDescription>Review the use case&nbsp;flow of events. If information is exchanged, be specific about what is passed back and
	forth.&nbsp; Work with stakeholders to ensure that you define newly discovered domain terms, or ambiguous
	terms&nbsp;properly in the <a class="elementLink" href="./../../openup_basic/workproducts/glossary,_Wn7HcNcEEdqz_d2XWoVt6Q.html" guid="_Wn7HcNcEEdqz_d2XWoVt6Q">Glossary</a>.
	If your understanding of the domain has improved,&nbsp;refine existing glossary terms.</sectionDescription>
	</sections>
	<sections xmi:id="_BYbboN-bEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_BYbboN-bEdqiM_wFaqLjNg">
	<sectionDescription>Conduct a review&nbsp;of the&nbsp;requirements (<a class="elementLinkWithType" href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a> and <a class="elementLinkWithType" href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements</a>)&nbsp;with relevant&nbsp;<a class="elementLinkWithUserText" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and the development team to ensure consistency with the <a class="elementLink" href="./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>, assess quality, and identify required changes. See&nbsp;<a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/effective_req_reviews,_E-dPIL-GEdqb7N6KIeDL8Q.html" guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: Effective Requirement Reviews</a>&nbsp;for more information.</sectionDescription>
	</sections>
	<purpose><p>
	The purpose of this task is to describe one or more requirements&nbsp;in sufficient detail to validate understanding of
	the requirement, to ensure concurrence with stakeholders expectations, and to permit software development&nbsp;to
	begin.
	</p></purpose>
	</org.eclipse.epf.uma:TaskDescription>