| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_Nqwi8KeqEdmKDbQuyzCoqQ" |
| name="detail_requirements,_0e1mIMlgEdmt3adZL5Dmdw" guid="_Nqwi8KeqEdmKDbQuyzCoqQ" |
| changeDate="2007-03-21T05:07:52.130-0800" 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/workproducts/use_case_22BE66E2.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 will be detailed prior to commencing implementation. Collaborate with stakeholders to detail only
 |
| those that are prioritized for implementation in the next iteration or two (see <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>), or those that are deemed architecturally significant (see
 |
| <a class="elementLinkWithType" href="./../../openup/guidances/concepts/architecturally_significant_requirements_1EE5D757.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. For
 |
| a discussion of the different levels of detail that may be applicable see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/use_case_formats_FF4AE425.html" guid="_qq0GMAXkEduj_7BEUj1JfQ">Guideline: Use Case Formats</a>.
 |
| </p>
 |
| <p>
 |
| Capture the use-case details in <a class="elementLinkWithType" href="./../../openup/workproducts/use_case_22BE66E2.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a>. For additional information on detailing use cases and scenarios, see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html" guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: Detail Use Cases and Scenarios</a>. For assistance in assessing the quality
 |
| of the use cases see <a class="elementLinkWithType" href="./../../openup/guidances/checklists/use_case_C5362874.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 <a class="elementLink" href="./../../openup/workproducts/supporting_requirements_spec_7D9DD47C.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Supporting Requirements Specification</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/guidances/concepts/change_requests_AD4868FE.html" guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a>. Collaborate with stakeholders to capture, refine and validate those
 |
| requirements that will have an impact on near term work (see <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>) or are deemed architecturally significant (see <a class="elementLinkWithType" href="./../../openup/guidances/concepts/architecturally_significant_requirements_1EE5D757.html" guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>).
 |
| </p>
 |
| <p>
 |
| Capture these requirements in the <a class="elementLinkWithType" href="./../../openup/workproducts/supporting_requirements_spec_7D9DD47C.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements Specification</a>.&nbsp; For additional guidance on detailing
 |
| supporting requirements see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/supporting_requirements_8ED0BB6B.html" guid="_wr24gNcGEdqz_d2XWoVt6Q">Guideline: Supporting Requirements</a>. For assistance in assessing the quality of your
 |
| supporting requirements see <a class="elementLinkWithType" href="./../../openup/guidances/checklists/supporting_requirements_3158BF2F.html" guid="_Vael8CGMEdu3VKXZx45D3A">Checklist: Supporting Requirements</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_2389cOz2Edq2wJOsmRwmhg" name="Detail Glossary terms" guid="_2389cOz2Edq2wJOsmRwmhg"> |
| <sectionDescription>Review the flow of the use case or scenario. If information is exchanged, be specific about what is passed back and forth.
 |
| Collaborate with stakeholders to ensure that you define newly discovered domain terms, or ambiguous terms properly in the
 |
| <a class="elementLink" href="./../../openup/workproducts/glossary_5D300778.html" guid="_Wn7HcNcEEdqz_d2XWoVt6Q">Glossary</a>. If your understanding of the domain has improved, refine existing glossary
 |
| terms.</sectionDescription> |
| </sections> |
| <sections xmi:id="_BYbboN-bEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_BYbboN-bEdqiM_wFaqLjNg"> |
| <sectionDescription>Conduct a review of the requirements (<a class="elementLinkWithType" href="./../../openup/workproducts/use_case_22BE66E2.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a> and <a class="elementLinkWithType" href="./../../openup/workproducts/supporting_requirements_spec_7D9DD47C.html" guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: Supporting Requirements Specification</a>)&nbsp;with relevant&nbsp;<a class="elementLinkWithUserText" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and the development team to ensure consistency with the <a class="elementLink" href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>, assess quality, and identify required changes. See <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/effective_req_reviews_5913D369.html" guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: Effective Requirement Reviews</a> for more information.</sectionDescription> |
| </sections> |
| <keyConsiderations>To avoid unnecessary rework, only those requirements that are scheduled for implementation in the near term (in the next
 |
| iteration or two) should be detailed.</keyConsiderations> |
| <purpose><p>
 |
| The purpose of this task is to describe one or more requirements in sufficient detail to validate understanding of the
 |
| requirement, to ensure concurrence with stakeholder expectations, and to permit software development to begin.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
