| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-JcGDIeBIMM099mbWX5fXbA" |
| name=",_qis78DRbEduFvfVCXiK3AA" guid="-JcGDIeBIMM099mbWX5fXbA" changeDate="2006-09-14T06:30:41.163-0700"> |
| <representationOptions><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/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html" guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: Detail Use Cases and Scenarios</a>&nbsp;for guidance related to documenting
 |
| Use Cases.
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |