| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-oFAa8Uu6tr_GkE_E0iycdQ" name="detail_use_case_scenarios,_SL7N0LPdEduocbW-TPTq7A" guid="-oFAa8Uu6tr_GkE_E0iycdQ" changeDate="2007-12-18T02:40:22.000-0800" changeDescription="Review comments:||1. Step 2 was a copy of step 1.|2. Step 1 - excessive linking - remove 2nd paragraph|" version="7.1.0"> |
| <keyConsiderations><p>
 |
| To avoid unnecessary rework, only those use-case scenarios that are scheduled for implementation in the near term (in
 |
| the next iteration or two)&nbsp;must be detailed.&nbsp;
 |
| </p>
 |
| <p>
 |
| Not all use-case scenarios require detailing.
 |
| </p></keyConsiderations> |
| <sections xmi:id="_fAWPkJLZEdyk6dG0ehkW5Q" name="Detail use cases and scenarios" guid="_fAWPkJLZEdyk6dG0ehkW5Q"> |
| <sectionDescription><p>
 |
| Some&nbsp;use cases and scenarios&nbsp;might need to be described in more detail to validate the understanding of the
 |
| requirements 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 on them. The level of detail captured will vary depending upon the
 |
| needs of the project and the complexity of the use case.&nbsp;Capture the use case and scenarios details in the use
 |
| case specification.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_iEvYMJLaEdyk6dG0ehkW5Q" name="Detail glossary terms" guid="_iEvYMJLaEdyk6dG0ehkW5Q"> |
| <sectionDescription><p>
 |
| 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&nbsp;glossary. If your understanding of the domain has improved, refine existing glossary terms.
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_kojt4JLcEdyk6dG0ehkW5Q" name="Achieve concurrence" guid="_kojt4JLcEdyk6dG0ehkW5Q"> |
| <sectionDescription><p>
 |
| Review the&nbsp;detailed use case and scenarios with relevant stakeholders and the development team to ensure
 |
| consistency with the agreed vision.&nbsp;Assess quality and identify any required changes.
 |
| </p></sectionDescription> |
| </sections> |
| <purpose>The purpose of this task is to describe&nbsp;use-case scenarios 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> |
