| <?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="-SUqkkwrs1D_5YXZls-3YBg" |
| name=",_oclg0DRXEdudA-StyUUwnw" guid="-SUqkkwrs1D_5YXZls-3YBg" changeDate="2007-05-31T06:05:37.479-0700"> |
| <representationOptions><h4>
 |
| Option: Use the Work Items List
 |
| </h4>
 |
| <p>
 |
| Consider capturing Supporting Requirements in the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, which
 |
| you can use for prioritizing and managing requirements. If Stakeholders are comfortable with accessing requirements
 |
| directly from&nbsp;the work items list, or with accessing a report automatically generated from it, then you do not
 |
| need a separate document.
 |
| </p>
 |
| <h4>
 |
| Option: Include as Part of the Vision Document
 |
| </h4>
 |
| <p>
 |
| Consider including some types of Supporting Requirements in the <a class="elementLink" href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>&nbsp;document. To keep
 |
| the Vision stable, follow this option for the requirements types that need less refinement, such as Product Qualities,
 |
| Documentation, or Compliance.<br />
 |
| </p></representationOptions> |
| </org.eclipse.epf.uma:ArtifactDescription> |