| <?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><p> |
| Does the requirement specify a true need, desire, or obligation? |
| </p> |
| <p> |
| Have you identified the "root cause" for the requirement? |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDs-0HEdqHTdbLTmC5IQ" name="Is the requirement complete?" guid="_jxuDs-0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDse0HEdqHTdbLTmC5IQ" name="Is the requirement clear?" guid="_jxuDse0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><p> |
| Is the requirement unambiguous and not confusing? |
| </p> |
| <p> |
| Does everyone agree on the meaning of the requirement? |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDt-0HEdqHTdbLTmC5IQ" name="Is the requirement consistent" guid="_jxuDt-0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><p> |
| Is the requirement in conflict with other requirements? |
| </p> |
| <p> |
| Is the terminology used consistent with other requirements and glossary terms? |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDte0HEdqHTdbLTmC5IQ" name="Is the requirement verifiable?" guid="_jxuDte0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDtu0HEdqHTdbLTmC5IQ" name="Is the requirement traceable?" guid="_jxuDtu0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><p> |
| Is the requirement uniquely identified so it can be unambiguously referenced? |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDtO0HEdqHTdbLTmC5IQ" name="Is the requirement feasible?" guid="_jxuDtO0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| <sections xmi:id="_jxuDsO0HEdqHTdbLTmC5IQ" name="Is the requirement design independent?" guid="_jxuDsO0HEdqHTdbLTmC5IQ"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| <sections xmi:id="_gRb_IJEvEdui_vx06Mo1eg" name="Is the requirement atomic?" guid="_gRb_IJEvEdui_vx06Mo1eg"> |
| <sectionDescription><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></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:ContentDescription> |