blob: 8dd9f6a4c257d44554e785e5fcfe4a114ef9371d [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>\openup_basic\workproducts\supporting_requirements_intent_req.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: supporting_requirements_intent_req.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: representationOptions<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:representationOptions,-SUqkkwrs1D_5YXZls-3YBg CRC: 3187753078 --><h4>
Recommendation: Use the Supporting Requirements Specification Template
</h4>
<p>
<a class="elementLinkWithType" href="./../../openup_basic/guidances/templates/supporting_requirements_spec,_ItYXcNa9Edqrw4BYKyYKiA.html" guid="_ItYXcNa9Edqrw4BYKyYKiA">Template: Supporting Requirements Specification</a>&nbsp;provides a tool to capture,
structure, and organize the supporting requirements.
</p>
<p>
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.
</p><!-- END:representationOptions,-SUqkkwrs1D_5YXZls-3YBg -->
</body>
</html>