OpenUP/OpenUP_baseline_EN/exported_HTML_1_0/openup/guidances/concepts/requirement_attributes.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?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&amp;#92;guidances&amp;#92;concepts&amp;#92;&amp;#92;requirement_attributes.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: requirement_attributes.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_VQ268O0KEdqHTdbLTmC5IQ CRC: 1974774863 -->Requirement Attributes<!-- END:presentationName,_VQ268O0KEdqHTdbLTmC5IQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_VQ268O0KEdqHTdbLTmC5IQ CRC: 3719514671 -->Requirements attributes capture additional information about each requirement. This additional information is used to help manage the project.<!-- END:briefDescription,_VQ268O0KEdqHTdbLTmC5IQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: mainDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:mainDescription,-fCBrf_5JlrmuKgyrCaKGOA CRC: 1013226381 --><p>
     Requirement Attributes are properties of a requirement. Attributes capture important additional information about a
     requirement. This information can subsequently be used to answer queries about the status of the development project.
 </p>
 <h4>
     Examples of attributes
 </h4>
 <p>
     Below is a list of attributes typically used by small projects, along with a brief description of their meaning. Some
     attributes are best described as a number, whilst other are best described as a date, a Boolean value (true or false),
     or a freeform text field. Other attributes can be expressed as enumerated lists. For instance, Priority may have values
     of High, Medium, or Low.
 </p>
 <p>
     <strong>Priority</strong> - Statement of relative importance of the requirement to stakeholders (high, medium, low).
 </p>
 <p>
     <strong>Assigned to</strong> - Who in the organization is responsible for making sure the requirement is met (person's
     name or organizational name).
 </p>
 <p>
     <strong>Target Iteration</strong> – The iteration in which the requirement is planned to be implemented (number or
     text).
 </p>
 <p>
     <strong>Estimation of Size</strong> - gives you a high-level estimate for the effort required to implement and verify
     the requirement, typically measured using a neutral unit such as points. (See <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>&nbsp;for more information).
 </p>
 <p>
     <strong>Effort Remaining</strong> – An estimate of the remaining effort to implement and verify the requirement
     (hours).
 </p>
 <p>
     <strong>Completion Status</strong> – The progress of implementing a requirement. This may be captured as an enumerated
     list (Complete, Partially Completed, Not Started) or can be inferred from the Effort Remaining attribute.
 </p>
 <p>
     When these attributes are assigned values for each requirement, it becomes easy to answer typical queries about the
     project such as:
 </p>
 <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
     <p>
         <em>How many requirements are to be implemented in the current iteration?<br />
         </em> (Query the <strong>Target Iteration</strong> attribute)
     </p>
     <p>
         <em>What percentage of the high priority requirements&nbsp;is currently implemented?<br />
         </em> (Query the <strong>Completion Status</strong> and <strong>Priority</strong> attributes)
     </p>
     <p>
         <em>How many requirements assigned to the current iteration remain unimplemented?<br />
         </em> (Query the <strong>Target Iteration</strong> and <strong>Completion Status</strong> attributes)
     </p>
     <p>
         <em>Which requirements are assigned to me?<br />
         </em> (Query the <strong>Assigned To</strong> attribute)<br />
     </p>
 </blockquote>
 <p>
     Examples of other useful requirements attributes include:
 </p>
 <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
     <p>
         <strong>Source</strong> - Person, document or other origin of a given requirement. This is useful for determining
         whom to call for questions or for grouping requirements according to the person making the demands.
     </p>
     <p>
         <strong>Comments</strong> - Reviewer's or writer's comments on a requirement.
     </p>
     <p>
         <strong>Difficulty</strong> - An indication of the level of effort needed or how hard it will be to implement the
         requirement (high, medium, low).
     </p>
     <p>
         <strong>Risk</strong> - Confidence measure on the likelihood of meeting (or not meeting) a requirement. Could be
         high, medium, low or the integers one through ten.
     </p>
     <p>
         <strong>Test ID</strong> - Identification of a specific test or other method of verification.
     </p>
 </blockquote><!-- END:mainDescription,-fCBrf_5JlrmuKgyrCaKGOA -->
 </body>
 </html>
	<?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&#92;guidances&#92;concepts&#92;&#92;requirement_attributes.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: requirement_attributes.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_VQ268O0KEdqHTdbLTmC5IQ CRC: 1974774863 -->Requirement Attributes<!-- END:presentationName,_VQ268O0KEdqHTdbLTmC5IQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_VQ268O0KEdqHTdbLTmC5IQ CRC: 3719514671 -->Requirements attributes capture additional information about each requirement. This additional information is used to help manage the project.<!-- END:briefDescription,_VQ268O0KEdqHTdbLTmC5IQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: mainDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:mainDescription,-fCBrf_5JlrmuKgyrCaKGOA CRC: 1013226381 --><p>
	Requirement Attributes are properties of a requirement. Attributes capture important additional information about a
	requirement. This information can subsequently be used to answer queries about the status of the development project.
	</p>
	<h4>
	Examples of attributes
	</h4>
	<p>
	Below is a list of attributes typically used by small projects, along with a brief description of their meaning. Some
	attributes are best described as a number, whilst other are best described as a date, a Boolean value (true or false),
	or a freeform text field. Other attributes can be expressed as enumerated lists. For instance, Priority may have values
	of High, Medium, or Low.
	</p>
	<p>
	<strong>Priority</strong> - Statement of relative importance of the requirement to stakeholders (high, medium, low).
	</p>
	<p>
	<strong>Assigned to</strong> - Who in the organization is responsible for making sure the requirement is met (person's
	name or organizational name).
	</p>
	<p>
	<strong>Target Iteration</strong> – The iteration in which the requirement is planned to be implemented (number or
	text).
	</p>
	<p>
	<strong>Estimation of Size</strong> - gives you a high-level estimate for the effort required to implement and verify
	the requirement, typically measured using a neutral unit such as points. (See <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a> for more information).
	</p>
	<p>
	<strong>Effort Remaining</strong> – An estimate of the remaining effort to implement and verify the requirement
	(hours).
	</p>
	<p>
	<strong>Completion Status</strong> – The progress of implementing a requirement. This may be captured as an enumerated
	list (Complete, Partially Completed, Not Started) or can be inferred from the Effort Remaining attribute.
	</p>
	<p>
	When these attributes are assigned values for each requirement, it becomes easy to answer typical queries about the
	project such as:
	</p>
	<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
	<p>
	<em>How many requirements are to be implemented in the current iteration?<br />
	</em> (Query the <strong>Target Iteration</strong> attribute)
	</p>
	<p>
	<em>What percentage of the high priority requirements is currently implemented?<br />
	</em> (Query the <strong>Completion Status</strong> and <strong>Priority</strong> attributes)
	</p>
	<p>
	<em>How many requirements assigned to the current iteration remain unimplemented?<br />
	</em> (Query the <strong>Target Iteration</strong> and <strong>Completion Status</strong> attributes)
	</p>
	<p>
	<em>Which requirements are assigned to me?<br />
	</em> (Query the <strong>Assigned To</strong> attribute)<br />
	</p>
	</blockquote>
	<p>
	Examples of other useful requirements attributes include:
	</p>
	<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
	<p>
	<strong>Source</strong> - Person, document or other origin of a given requirement. This is useful for determining
	whom to call for questions or for grouping requirements according to the person making the demands.
	</p>
	<p>
	<strong>Comments</strong> - Reviewer's or writer's comments on a requirement.
	</p>
	<p>
	<strong>Difficulty</strong> - An indication of the level of effort needed or how hard it will be to implement the
	requirement (high, medium, low).
	</p>
	<p>
	<strong>Risk</strong> - Confidence measure on the likelihood of meeting (or not meeting) a requirement. Could be
	high, medium, low or the integers one through ten.
	</p>
	<p>
	<strong>Test ID</strong> - Identification of a specific test or other method of verification.
	</p>
	</blockquote><!-- END:mainDescription,-fCBrf_5JlrmuKgyrCaKGOA -->
	</body>
	</html>