| <?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-09-03T17:31:44.256-0700" |
| 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 might be unclear which functionality the solution needs
 |
| to support.</impactOfNotHaving> |
| <reasonsForNotNeeding>You
 |
| might not need to use a use case if your project uses alternative requirements
 |
| practices (for example, &#x201c;The system shall&#x2026;&#x201d; statements).<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). Write the description so that the customer
 |
| can understand it. 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 of the requirements of the use case that are not considered
 |
| in the use-case model, but that must be taken care of during design or implementation
 |
| (for example, non-functional requirements)</li>
 |
| <li> <strong>Preconditions:</strong> A textual description that defines
 |
| a constraint on the system when the use case starts </li>
 |
| <li> <strong>Post-conditions:</strong> A textual description that
 |
| defines a constraint on the system when the use case ends </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 by using the extend-relationship </li>
 |
| </ul></briefOutline> |
| <representationOptions><p
 |
| > You can document the use case as a use-case specification document or you
 |
| can incorporate the use case in a use-case model. You can also use a requirements
 |
| management tool to capture use cases and parts of use cases<?Pub Caret?>. </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |
