| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription 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" xmi:id="_zHZW8qYSEdmvhNXG0Oc2uA" name="use_case,_0VGbUMlgEdmt3adZL5Dmdw" guid="_zHZW8qYSEdmvhNXG0Oc2uA" changeDate="2006-09-13T14:58:40.026-0700"> |
| <purpose><p> The primary purpose of the Use Case is to capture the required system behavior |
| from the perspective of the end user, to achieve one or more goals. Different |
| users benefit in different ways, of course: </p> |
| <ul> |
| <li> <strong>Customers</strong> use them to describe, or at least to approve, |
| the description of the system's behavior. </li> |
| <li><strong> Potential users</strong> use them to understand the system's behavior. |
| </li> |
| <li><strong> Architects </strong>use them to identify architecturally significant |
| functionality. </li> |
| <li><strong> Developers </strong>use them<strong> </strong> to understand the |
| required system behavior so they can identify classes from the Use Cases' |
| flow of events. </li> |
| <li><strong> Testers</strong> use them as a basis for identifying a subset of |
| the required Test Cases. </li> |
| <li> <strong>M</strong><b>anagers</b> use them<b> </b> to plan and assess the |
| work for each iteration. </li> |
| <li><strong> Technical writers </strong>use them |
| to understand the sequence of system behavior |
| that they need to describe in the documentation. </li> |
| </ul></purpose> |
| <representationOptions><p> Decide the extent to which you will elaborate on Use |
| Cases: </p> |
| <ul> |
| |
| <li> Describe only major flows? </li> |
| |
| <li> Describe only the most important Use Cases? </li> |
| |
| <li>Fully describe preconditions and post-conditions? </li> |
| |
| <li> Describe scenarios first, and then raise the level of abstraction by describing |
| Use Case flows? </li> |
| </ul></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |