<?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" epf:version="1.0.0" xmi:id="-JcGDIeBIMM099mbWX5fXbA" name=",_qis78DRbEduFvfVCXiK3AA" guid="-JcGDIeBIMM099mbWX5fXbA" changeDate="2006-09-14T09:30:41.163-0400">
  <representationOptions>&lt;p&gt;
    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 &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/guidelines/detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q.html&quot; guid=&quot;_4BJ_YCxSEdqjsdw1QLH_6Q&quot;&gt;Guideline: Detail Use Cases and Scenarios&lt;/a&gt;&amp;nbsp;for guidance related to documenting
    Use Cases.
&lt;/p&gt;</representationOptions>
</org.eclipse.epf.uma:ArtifactDescription>