blob: 0a364afbe97bbdfa5e4d41d8d22669ef8f482178 [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_intent_req.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_intent_req.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: representationOptions<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:representationOptions,-JcGDIeBIMM099mbWX5fXbA CRC: 205132673 --><p>
Some projects apply Use Cases informally to help discover requirements, documenting and maintaining these requirements
in another form such as user stories. How you tailor Use Cases may depend on project size, team experience, your tool
set, the customer relationship, and so forth. See <a class="elementLinkWithType" href="./../../openup_basic/guidances/guidelines/detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q.html" guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: Detail Use Cases and Scenarios</a>&nbsp;for guidance related to documenting
Use Cases.
</p><!-- END:representationOptions,-JcGDIeBIMM099mbWX5fXbA -->
</body>
</html>