blob: e761171fc4e87195013d7d129ccb3f2dbac5c0fe [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\guidances\checklists\good_requirements.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: good_requirements.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_jxn9EO0HEdqHTdbLTmC5IQ CRC: 3010651615 -->Qualities of Good Requirements<!-- END:presentationName,_jxn9EO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_jxn9EO0HEdqHTdbLTmC5IQ CRC: 489495434 -->This checklist provides guidance on assessing the quality of requirements.<!-- END:briefDescription,_jxn9EO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDsu0HEdqHTdbLTmC5IQ CRC: 2680628265 -->Is the requirement correct?<!-- END:name,_jxuDsu0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDsu0HEdqHTdbLTmC5IQ CRC: 1326692982 --><p>
Does the requirement specify a true need, desire, or obligation?
</p>
<p>
Have you identified the "root cause" for the requirement?
</p><!-- END:sectionDescription,_jxuDsu0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDs-0HEdqHTdbLTmC5IQ CRC: 2453166247 -->Is the requirement complete?<!-- END:name,_jxuDs-0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDs-0HEdqHTdbLTmC5IQ CRC: 923625204 --><p>
Is the requirement stated as a complete sentence?
</p>
<p>
Is the requirement stated entirely in one place, in a manner that does not force the reader to look at additional
information to understand the requirement?
</p><!-- END:sectionDescription,_jxuDs-0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDse0HEdqHTdbLTmC5IQ CRC: 1375086789 -->Is the requirement clear?<!-- END:name,_jxuDse0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDse0HEdqHTdbLTmC5IQ CRC: 4116032612 --><p>
Is the requirement unambiguous and not confusing?
</p>
<p>
Does everyone agree on the meaning of the requirement?
</p><!-- END:sectionDescription,_jxuDse0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDt-0HEdqHTdbLTmC5IQ CRC: 1860228673 -->Is the requirement consistent<!-- END:name,_jxuDt-0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDt-0HEdqHTdbLTmC5IQ CRC: 787788266 --><p>
Is the requirement in conflict with other requirements?
</p>
<p>
Is the terminology used consistent with other requirements and glossary terms?
</p><!-- END:sectionDescription,_jxuDt-0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDte0HEdqHTdbLTmC5IQ CRC: 995275143 -->Is the requirement verifiable?<!-- END:name,_jxuDte0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDte0HEdqHTdbLTmC5IQ CRC: 3260001816 --><p>
Can we determine whether the system satisfies the requirement?
</p>
<p>
Is it possible to define a clear, unambiguous&nbsp;pass/fail criterion?
</p>
<p>
Is it possible to determine if the requirement has been met via inspection, analysis, demonstration or test?
</p><!-- END:sectionDescription,_jxuDte0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDtu0HEdqHTdbLTmC5IQ CRC: 1566052626 -->Is the requirement traceable?<!-- END:name,_jxuDtu0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDtu0HEdqHTdbLTmC5IQ CRC: 2457844759 --><p>
Is the requirement uniquely identified so it can be unambiguously referenced?
</p><!-- END:sectionDescription,_jxuDtu0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDtO0HEdqHTdbLTmC5IQ CRC: 1331256571 -->Is the requirement feasible?<!-- END:name,_jxuDtO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDtO0HEdqHTdbLTmC5IQ CRC: 26269228 --><p>
Can the requirement be satisfied within cost and on schedule?
</p>
<p>
Is the requirement technically feasible with current technology?
</p>
<p>
Is the requirement physically achievable?
</p><!-- END:sectionDescription,_jxuDtO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_jxuDsO0HEdqHTdbLTmC5IQ CRC: 3359799507 -->Is the requirement design independent?<!-- END:name,_jxuDsO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_jxuDsO0HEdqHTdbLTmC5IQ CRC: 2721187127 --><p>
Are all requirements that impose constraints on the design, limiting design options,&nbsp;justified?
</p>
<p>
Is the requirement stated in such that there is more than one way that it can be satisfied?
</p><!-- END:sectionDescription,_jxuDsO0HEdqHTdbLTmC5IQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_gRb_IJEvEdui_vx06Mo1eg CRC: 4047137448 -->Is the requirement atomic?<!-- END:name,_gRb_IJEvEdui_vx06Mo1eg -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_gRb_IJEvEdui_vx06Mo1eg CRC: 2752865898 --><p>
Does the requirement statement define exactly one requirement?
</p>
<p>
Is the requirement statement free of conjunctions (and, or, but) that may indicate multiple requirements?
</p><!-- END:sectionDescription,_gRb_IJEvEdui_vx06Mo1eg -->
</body>
</html>