<?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-2o1pXjHpSEPN_rohLce5jA" name="good_requirements_1,_jxn9EO0HEdqHTdbLTmC5IQ" guid="-2o1pXjHpSEPN_rohLce5jA" authors="Chris Sibbald" changeDate="2006-04-10T11:07:04.339-0400" 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;p&gt;
    Does the requirement specify a true need, desire, or obligation?
&lt;/p&gt;
&lt;p&gt;
    Have you identified the &quot;root cause&quot; for the requirement?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDs-0HEdqHTdbLTmC5IQ" name="Is the requirement complete?" guid="_jxuDs-0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Is the requirement stated as a complete sentence?
&lt;/p&gt;
&lt;p&gt;
    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?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDse0HEdqHTdbLTmC5IQ" name="Is the requirement clear?" guid="_jxuDse0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Is the requirement unambiguous and not confusing?
&lt;/p&gt;
&lt;p&gt;
    Does everyone agree on the meaning of the requirement?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDt-0HEdqHTdbLTmC5IQ" name="Is the requirement consistent" guid="_jxuDt-0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Is the requirement in conflict with other requirements?
&lt;/p&gt;
&lt;p&gt;
    Is the terminology used consistent with other requirements and glossary terms?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDte0HEdqHTdbLTmC5IQ" name="Is the requirement verifiable?" guid="_jxuDte0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Can we determine whether the system satisfies the requirement?
&lt;/p&gt;
&lt;p&gt;
    Is it possible to define a clear, unambiguous&amp;nbsp;pass/fail criterion?
&lt;/p&gt;
&lt;p&gt;
    Is it possible to determine if the requirement has been met via inspection, analysis, demonstration or test?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDtu0HEdqHTdbLTmC5IQ" name="Is the requirement traceable?" guid="_jxuDtu0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Is the requirement uniquely identified so it can be unambiguously referenced?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDtO0HEdqHTdbLTmC5IQ" name="Is the requirement feasible?" guid="_jxuDtO0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Can the requirement be satisfied within cost and on schedule?
&lt;/p&gt;
&lt;p&gt;
    Is the requirement technically feasible with current technology?
&lt;/p&gt;
&lt;p&gt;
    Is the requirement physically achievable?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jxuDsO0HEdqHTdbLTmC5IQ" name="Is the requirement design independent?" guid="_jxuDsO0HEdqHTdbLTmC5IQ">
    <sectionDescription>&lt;p&gt;
    Are all requirements that impose constraints on the design, limiting design options,&amp;nbsp;justified?
&lt;/p&gt;
&lt;p&gt;
    Is the requirement stated in such that there is more than one way that it can be satisfied?
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_gRb_IJEvEdui_vx06Mo1eg" name="Is the requirement atomic?" guid="_gRb_IJEvEdui_vx06Mo1eg">
    <sectionDescription>&lt;p&gt;
    Does the requirement statement define exactly one requirement?
&lt;/p&gt;
&lt;p&gt;
    Is the requirement statement free of conjunctions (and, or, but) that may indicate multiple requirements?
&lt;/p&gt;</sectionDescription>
  </sections>
</org.eclipse.epf.uma:ContentDescription>