OpenUP/OpenUP_SP/library/openup_basic/workproducts/use_case.xmi

<?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>&lt;p&gt; 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: &lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt; &lt;strong&gt;Customers&lt;/strong&gt; use them to describe, or at least to approve, 
    the description of the system's behavior. &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt; Potential users&lt;/strong&gt; use them to understand the system's behavior. 
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt; Architects &lt;/strong&gt;use them to identify architecturally significant 
    functionality. &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt; Developers &lt;/strong&gt;use them&lt;strong&gt; &lt;/strong&gt; to understand the 
    required system behavior so they can identify classes from the Use Cases' 
    flow of events. &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt; Testers&lt;/strong&gt; use them as a basis for identifying a subset of 
    the required Test Cases. &lt;/li&gt;
  &lt;li&gt; &lt;strong&gt;M&lt;/strong&gt;&lt;b&gt;anagers&lt;/b&gt; use them&lt;b&gt; &lt;/b&gt; to plan and assess the 
    work for each iteration. &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt; Technical writers &lt;/strong&gt;use them 
    to understand the sequence of system behavior 
    that they need to describe in the documentation. &lt;/li&gt;
&lt;/ul&gt;</purpose>
  <representationOptions>&lt;p&gt; Decide the extent to which you will elaborate on Use 
  Cases: &lt;/p&gt;
&lt;ul&gt;
    
  &lt;li&gt; Describe only major flows? &lt;/li&gt;
    
  &lt;li&gt; Describe only the most important Use Cases? &lt;/li&gt;
    
  &lt;li&gt;Fully describe preconditions and post-conditions? &lt;/li&gt;
    
  &lt;li&gt; Describe scenarios first, and then raise the level of abstraction by describing 
    Use Case flows? &lt;/li&gt;
&lt;/ul&gt;</representationOptions>
</org.eclipse.epf.uma:ArtifactDescription>