| <?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.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="_zHZW8qYSEdmvhNXG0Oc2uA" |
| name="use_case,_0VGbUMlgEdmt3adZL5Dmdw" guid="_zHZW8qYSEdmvhNXG0Oc2uA" changeDate="2008-08-14T12:17:34.664-0400" |
| version="1.0.0"> |
| <purpose><p> |
| Use cases are used for the following purposes: |
| </p> |
| <ul> |
| <li> |
| to reach a common understanding of system behavior. |
| </li> |
| <li> |
| to design elements that support the required behavior. |
| </li> |
| <li> |
| to identify test cases. |
| </li> |
| <li> |
| to plan and assess work. |
| </li> |
| <li> |
| to write user documentation. |
| </li> |
| </ul></purpose> |
| <impactOfNotHaving>Without this artifact it may be unclear&nbsp;what functionality the solution needs to support.</impactOfNotHaving> |
| <reasonsForNotNeeding>A project may use alternative requirements practices (e.g. “The system shall…” statements) which could replace use
 |
| cases.<br /></reasonsForNotNeeding> |
| <briefOutline><p>
 |
| A use case typically includes the following information:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Name:</strong> The name of the use case.
 |
| </li>
 |
| <li>
 |
| <strong>Brief Description:</strong> A brief description of the role and purpose of the use case.
 |
| </li>
 |
| <li>
 |
| <strong>Flow of Events:</strong> A textual description of what the system does in regard to a use case scenario
 |
| (not how specific problems are solved by the system). The description is understandable by the customer.&nbsp; The
 |
| flows can include a basic flow, alternative flows, and subflows.
 |
| </li>
 |
| <li>
 |
| <strong>Key scenarios:</strong> A textual description of the most important or frequently discussed scenarios.
 |
| </li>
 |
| <li>
 |
| <strong>Special Requirements:</strong> A textual description that collects all requirements, such as non-functional
 |
| requirements, on the use case, that are not considered in the use-case model, but that need to be taken care of
 |
| during design or implementation.&nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| <strong>Preconditions:</strong>&nbsp;A textual description that defines a constraint on the system when the use
 |
| case may start.&nbsp;&nbsp;&nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| <strong>Post conditions:</strong> A textual description that defines a constraint on the system when the use cases
 |
| have terminated.&nbsp;&nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| <strong>Extension points:</strong> A list of locations within the flow of events of the use case at which
 |
| additional behavior can be inserted using the extend-relationship.&nbsp;&nbsp;&nbsp;
 |
| </li>
 |
| </ul></briefOutline> |
| <representationOptions><p>
 |
| The use case can be documented as just a use-case specification document, or can be incorporated in a use-case
 |
| model.&nbsp; Use cases, and parts of use cases, can also be captured in a requirements management tool.
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
