| <?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="_P9iS8PV_EdmdHa9MmVPgqQ" |
| name="find_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ" guid="_P9iS8PV_EdmdHa9MmVPgqQ" |
| changeDate="2007-03-23T09:54:39.420-0800" version="1.0.0"> |
| <sections xmi:id="_ckG-cCY-EdqNHcQ-rAojXw" name="Gather information" guid="_ckG-cCY-EdqNHcQ-rAojXw"> |
| <sectionDescription><p>
 |
| 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 must prepare in order
 |
| for these meetings to run efficiently.
 |
| </p>
 |
| <p>
 |
| Be prepared by gathering and reviewing information related to the problem domain, problem statement, business
 |
| environment and key stakeholders. Most of this information should be available in the <a class="elementLinkWithType" href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Artifact: Vision</a>.&nbsp; Review the <a class="elementLinkWithType" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a> for stakeholder requests.
 |
| </p>
 |
| <p>
 |
| See <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/req_gathering_techniques_8CB8E44C.html" guid="_OnoNQNSAEdmLhZ9H5Plxyw">Guideline: Requirements Gathering Techniques</a> for more information.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_GAr3IOz3Edq2wJOsmRwmhg" name="Identify and capture domain terms" |
| guid="_GAr3IOz3Edq2wJOsmRwmhg"> |
| <sectionDescription>Collaborate with stakeholder to make sure that ambiguous or domain-specific terms are clearly defined in the <a class="elementLink" href="./../../openup/workproducts/glossary_5D300778.html" guid="_Wn7HcNcEEdqz_d2XWoVt6Q">Glossary</a> and that you use these terms consistently.</sectionDescription> |
| </sections> |
| <sections xmi:id="_fDbgkCY-EdqNHcQ-rAojXw" name="Identify the types of requirements relevant to your system" |
| guid="_fDbgkCY-EdqNHcQ-rAojXw"> |
| <sectionDescription><p>
 |
| Requirements can be broadly classified as either functional or non-functional requirements. The former specify what the
 |
| system must do. The latter specify constraints on the solution such as usability, reliability, performance,
 |
| supportability, interfaces with legacy systems, etc. Depending upon the domain there may be regulatory requirements
 |
| that apply.
 |
| </p>
 |
| <p>
 |
| Collaborate with stakeholders to identify the types of requirements relevant to your system. This will help you assess
 |
| the completeness of your requirement set. For more information on types of requirements see <a class="elementlinkwithtype" href="./../../openup/guidances/concepts/requirements_8006414F.html" guid="_0Wh-sMlgEdmt3adZL5Dmdw">Concept: Requirements</a> and <a class="elementLinkWithType" href="./../../openup/guidances/concepts/supporting_requirements_B2C4D610.html" guid="_VXZ5wO0IEdqHTdbLTmC5IQ">Concept: Supporting Requirements</a>.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_5is40NccEdu5tJAZnuAhYQ" name="Identify and capture Supporting Requirements" |
| guid="_5is40NccEdu5tJAZnuAhYQ"> |
| <sectionDescription><p>
 |
| Collaborate with stakeholders to identify and capture&nbsp;the other types of requirements relevant to your system. See
 |
| <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/supporting_requirements_8ED0BB6B.html" guid="_wr24gNcGEdqz_d2XWoVt6Q">Guideline: Supporting Requirements</a> for more information.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_0WhHsN-eEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_0WhHsN-eEdqiM_wFaqLjNg"> |
| <sectionDescription>Conduct a review of the requirements with relevant <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 any 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> |
| <sections xmi:id="_Mgb9IC4DEduBP8F-6-95NQ" name="Update the Work Items List" guid="_Mgb9IC4DEduBP8F-6-95NQ"> |
| <sectionDescription>Capture references to the requirements in the <a class="elementLinkWithType" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>, so they can be prioritized.</sectionDescription> |
| </sections> |
| <keyConsiderations>Collaboration with stakeholders on this task is critical for the success of project. See principle <a class="elementLink" href="./../../openup/guidances/concepts/core_principle_collaborate_EC5EB51F.html" guid="_KkTIsMp7EdqC_NfSivunjA">Collaborate to align interests and share understanding</a> for more information.</keyConsiderations> |
| <purpose><p>
 |
| The purpose of this task is to identify and capture functional and non-functional requirements for the system. These
 |
| requirements form the basis of communication and agreement between the stakeholders and the development team on what
 |
| the system must do to satisfy stakeholder needs. The goal is to understand the requirements at a high-level so that the
 |
| initial scope of work can be determined.&nbsp; Further analysis will be performed to detail these requirements prior to
 |
| implementation.
 |
| </p></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
