blob: e6c1c6060dd864c3fc426f14d7b63547cb7128e8 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>\openup_basic\workproducts\use_case.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: use_case.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0VGbUMlgEdmt3adZL5Dmdw CRC: 3319967926 -->Use Case<!-- END:presentationName,_0VGbUMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0VGbUMlgEdmt3adZL5Dmdw CRC: 2735006813 -->This artifact captures the sequence of actions a system performs that yields an observable result of value to those interacting with the system.<!-- END:briefDescription,_0VGbUMlgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,_zHZW8qYSEdmvhNXG0Oc2uA CRC: 4252402079 --><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><!-- END:purpose,_zHZW8qYSEdmvhNXG0Oc2uA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: representationOptions<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:representationOptions,_zHZW8qYSEdmvhNXG0Oc2uA CRC: 734904562 --><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><!-- END:representationOptions,_zHZW8qYSEdmvhNXG0Oc2uA -->
</body>
</html>