<?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="-SUqkkwrs1D_5YXZls-3YBg" name=",_oclg0DRXEdudA-StyUUwnw" guid="-SUqkkwrs1D_5YXZls-3YBg" changeDate="2006-09-14T09:34:35.021-0400">
  <representationOptions>&lt;h4&gt;
    Recommendation: Use the Supporting Requirements Specification Template
&lt;/h4&gt;
&lt;p&gt;
    &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/guidances/templates/supporting_requirements_spec,_ItYXcNa9Edqrw4BYKyYKiA.html&quot; guid=&quot;_ItYXcNa9Edqrw4BYKyYKiA&quot;&gt;Template: Supporting Requirements Specification&lt;/a&gt;&amp;nbsp;provides a tool to capture,
    structure, and organize the supporting requirements.
&lt;/p&gt;
&lt;p&gt;
    Even in a small project, a requirements management tool, a database, or a spreadsheet, are recommended for prioritizing
    and managing requirements. If Stakeholders are comfortable with accessing requirements directly from that tool or with
    accessing a report automatically generated from the tool, you will not need a separate document.
&lt;/p&gt;</representationOptions>
</org.eclipse.epf.uma:ArtifactDescription>