libraries/EPF_Practices_Library/obsoleted_from_openup/workproducts/supporting_requirements_intent_req.xmi

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