| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.2.0" xmi:id="-9sNgONA1WJCxf12B40uDgw" |
| name="detail_system_wide_requirements,_4z8Z0EbEEdyx8quJU3Grxg" guid="-9sNgONA1WJCxf12B40uDgw" |
| changeDate="2007-11-14T10:42:54.904-0800" version="1.0.0"> |
| <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> |
| <sections xmi:id="_4z8Z1EbEEdyx8quJU3Grxg" name="Detail system-wide requirements " |
| guid="_4z8Z1EbEEdyx8quJU3Grxg"> |
| <sectionDescription><p>
 |
| Some&nbsp;system-wide requirements&nbsp;may need to be clarified or described in more detail.&nbsp;New
 |
| requirements&nbsp;may&nbsp;be discovered&nbsp;while the use cases and scenarios are detailed, and new requirements may
 |
| have been submitted as change requests.&nbsp;Collaborate with stakeholders to capture, refine and validate those
 |
| requirements that will have an impact on near term, planned&nbsp;work or are deemed architecturally significant.&nbsp;
 |
| </p><br /></sectionDescription> |
| </sections> |
| <sections xmi:id="_4z8Z0UbEEdyx8quJU3Grxg" name="Detail glossary terms" guid="_4z8Z0UbEEdyx8quJU3Grxg"> |
| <sectionDescription>Review the system-wide requirements and collaborate with stakeholders to ensure that you define newly discovered domain
 |
| terms, or ambiguous terms properly in the glossary. If your understanding of the domain has improved, refine existing
 |
| glossary terms.</sectionDescription> |
| </sections> |
| <sections xmi:id="_4z8Z0kbEEdyx8quJU3Grxg" name="Achieve concurrence" guid="_4z8Z0kbEEdyx8quJU3Grxg"> |
| <sectionDescription><p>
 |
| Review the&nbsp;detailed system-wide requirements with relevant stakeholders and the development team to ensure
 |
| consistency with the&nbsp;agreed vision.&nbsp;Assess quality and identify any required changes.
 |
| </p></sectionDescription> |
| </sections> |
| <purpose>The purpose of this task is to describe one or more system-wide requirements in sufficient detail to validate understanding
 |
| of the requirements, to ensure concurrence with stakeholder expectations, and to permit software development to begin.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
