| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-AJQLv2ldVv5KN9eUbdQe_g" name="new_guideline,_6jXzYNcKEdqz_d2XWoVt6Q" guid="-AJQLv2ldVv5KN9eUbdQe_g" changeDate="2006-05-01T03:33:21.000-0700" version="7.1.0"> |
| <mainDescription><p>
 |
| To write a good requirement, you must write it as a complete sentence, with a subject and a predicate (usually a verb).
 |
| The subject&nbsp;is an Actor, a stakeholder, the system under development, or a design entity that is related to the
 |
| requirement. The predicate specifies a condition, action, or intended result that is done for, by, with, or to the
 |
| subject.
 |
| </p>
 |
| <p>
 |
| Consistent use of the verb <strong>to be</strong> solidifies the link between the subject and the predicate. Thus, you
 |
| can analyze a requirement from a grammatical point of view.
 |
| </p>
 |
| <p>
 |
| Beware of lists, bullets, and words such as <strong>all</strong>, <strong>every</strong>, and <strong>some</strong>.
 |
| For example:
 |
| </p>
 |
| <blockquote>
 |
| <p>
 |
| The order entry clerk must be able to complete 10 customer orders in less than two hours.
 |
| </p>
 |
| </blockquote>
 |
| <p>
 |
| This requirement has a subject (the order entry clerk, who is an Actor), a specific and measurable end state (10
 |
| customer orders completed), and a performance criterion (in less than two hours).
 |
| </p>
 |
| <p>
 |
| Follow these simple guidelines in writing any requirement. For consistency, these examples are all in the context of an
 |
| aircraft. [[WAS: is used throughout.]] <a class="elementlinkwithusertext"
 |
| href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html"
 |
| guid="_9ToeIB83Edqsvps02rpOOg">[TEL06]</a>
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Define one requirement at a time. 
 |
| <blockquote>
 |
| <p>
 |
| The pilot shall be able to control the aircraft's angle of climb with one hand.
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| </ul>
 |
| <blockquote>
 |
| <blockquote>
 |
| <p>
 |
| The pilot shall be able to feel the angle of climb from the climb control.
 |
| </p>
 |
| </blockquote>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| Avoid conjunctions (and, or) that make multiple requirements.
 |
| </li>
 |
| </ul>
 |
| <blockquote>
 |
| <blockquote>
 |
| <p>
 |
| The navigator shall be able to view the aircraft's position relative to the route's radio beacons.
 |
| </p>
 |
| <p>
 |
| The navigator shall be able to view the aircraft's position as estimated by inertial guidance.
 |
| </p>
 |
| </blockquote>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| Avoid let-out clauses or words that imply options or exceptions (unless, except, if necessary, but).
 |
| </li>
 |
| <li style="list-style: none">
 |
| <blockquote>
 |
| <p>
 |
| The design shall provide a rear-facing seat for each cabin crew member.
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li>
 |
| Use simple, direct sentences.
 |
| </li>
 |
| </ul>
 |
| <ul>
 |
| <li style="list-style: none">
 |
| <blockquote>
 |
| <p>
 |
| The pilot shall be able to see the airspeed indicator.
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li>
 |
| Use a limited (500-word) vocabulary, especially if your audience is international. 
 |
| <blockquote>
 |
| <p>
 |
| The airline shall be able to convert the aircraft from business to holiday charter use in less than 12
 |
| hours
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li style="list-style: none">
 |
| <blockquote>
 |
| <p>
 |
| <strong>Note:</strong> There is no need to use words such as <strong>reconfigured.</strong>
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li>
 |
| Identify the type of user who needs each requirement.
 |
| </li>
 |
| </ul>
 |
| <ul>
 |
| <li style="list-style: none">
 |
| <blockquote>
 |
| <p>
 |
| The navigator shall be able to...
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li>
 |
| Focus on stating what result you will provide for that type of user.
 |
| </li>
 |
| </ul>
 |
| <ul>
 |
| <li style="list-style: none">
 |
| <blockquote>
 |
| <p>
 |
| ...view storm clouds by radar...
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| <li>
 |
| Define verifiable criteria 
 |
| <blockquote>
 |
| <p>
 |
| ...at least 100 miles ahead.
 |
| </p>
 |
| </blockquote>
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
