<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription 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="-2o1pXjHpSEPN_rohLce5jA"
    name="good_requirements_1,_jxn9EO0HEdqHTdbLTmC5IQ" guid="-2o1pXjHpSEPN_rohLce5jA"
    authors="Chris Sibbald" changeDate="2006-04-10T08:07:04.339-0700" changeDescription="Added checklist for good requirements in accordance with Feb. 23, 2006 minutes of RM SIG."
    version="0.1">
  <sections xmi:id="_jxuDsu0HEdqHTdbLTmC5IQ" name="Is the requirement correct?" guid="_jxuDsu0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Does the requirement specify a true need, desire, or obligation? &lt;/li>&#xD;
  &lt;li> Have you identified the root cause that necessitates the requirement? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDs-0HEdqHTdbLTmC5IQ" name="Is the requirement complete?" guid="_jxuDs-0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Is the requirement stated as a complete sentence? &lt;/li>&#xD;
  &lt;li> Is the requirement stated entirely in one place and in a manner that does &#xD;
    not force the reader to look at additional information to understand the requirement? &#xD;
  &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDse0HEdqHTdbLTmC5IQ" name="Is the requirement clear?" guid="_jxuDse0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Is the requirement unambiguous and not confusing? &lt;/li>&#xD;
  &lt;li> Does everyone agree on the meaning of the requirement? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDt-0HEdqHTdbLTmC5IQ" name="Is the requirement consistent?"
      guid="_jxuDt-0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Is the requirement in conflict with other requirements? &lt;/li>&#xD;
  &lt;li> Is the terminology used consistent with other requirement and glossary &#xD;
    terms? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDte0HEdqHTdbLTmC5IQ" name="Is the requirement verifiable?"
      guid="_jxuDte0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Can you determine whether the system satisfies the requirement? &lt;/li>&#xD;
  &lt;li> Is it possible to define a clear, unambiguous&amp;nbsp;pass or fail criterion? &#xD;
  &lt;/li>&#xD;
  &lt;li> Is it possible to determine whether the requirement has been met through &#xD;
    inspection, analysis, demonstration, or test? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDtu0HEdqHTdbLTmC5IQ" name="Is the requirement traceable?"
      guid="_jxuDtu0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p> Is the requirement uniquely identified so that it can be referenced unambiguously? &#xD;
&lt;/p></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDtO0HEdqHTdbLTmC5IQ" name="Is the requirement feasible?" guid="_jxuDtO0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Can the requirement be satisfied within budget and on schedule? &lt;/li>&#xD;
  &lt;li> Is the requirement technically feasible with current technology? &lt;/li>&#xD;
  &lt;li> Is the requirement physically achievable? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_jxuDsO0HEdqHTdbLTmC5IQ" name="Is the requirement design independent?"
      guid="_jxuDsO0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Are all requirements that impose constraints on the design, thereby limiting &#xD;
    design options,&amp;nbsp;justified? &lt;/li>&#xD;
  &lt;li> Is the requirement stated in such a way that there is more than one way &#xD;
    that it can be satisfied? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
  <sections xmi:id="_gRb_IJEvEdui_vx06Mo1eg" name="Is the requirement atomic?" guid="_gRb_IJEvEdui_vx06Mo1eg">
    <sectionDescription>&lt;ul>&#xD;
  &lt;li> Does the requirement statement define exactly one requirement? &lt;/li>&#xD;
  &lt;li> Is the requirement statement free of conjunctions (and, or, but) that could &#xD;
    indicate multiple requirements? &lt;/li>&#xD;
&lt;/ul></sectionDescription>
  </sections>
</org.eclipse.epf.uma:ContentDescription>