| <?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="-TksCtMgc0b4QqzwzniGvIw" |
| name="traceability_1,_eYtQQO0KEdqHTdbLTmC5IQ" guid="-TksCtMgc0b4QqzwzniGvIw" authors="Chris Sibbald" |
| changeDate="2007-04-05T06:08:15.287-0700" changeDescription="Added concept in accordance with Feb 23, 2006 minutes of RM SIG meeting." |
| version="0.1"> |
| <mainDescription><p align="left">
 |
| Traceability is about understanding how high-level requirements (objectives, goals, aims, aspirations, expectations,
 |
| needs) are transformed into low-level requirements, how they are implemented, and how they are verified.
 |
| </p>
 |
| <p>
 |
| Using traceability can provide the following benefits <a class="elementlinkwithusertext" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#HUL05" guid="_9ToeIB83Edqsvps02rpOOg">[HUL05]</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <strong>Greater confidence in meeting objectives</strong>
 |
| </li>
 |
| </ul>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| Traceability increases confidence that objectives will be met by permitting coverage analysis to ensure that
 |
| everything agreed to has been done.
 |
| </p>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| <strong>Ability to assess the impact of change</strong>
 |
| </li>
 |
| </ul>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| Traceability allows the impact (cost, schedule, technical) of changes to be assessed before work begins.
 |
| </p>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| <strong>Improved accountability</strong>
 |
| </li>
 |
| </ul>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| Traceability provides clarity about how the work contributes to the project as a whole.
 |
| </p>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| <strong>Ability to track progress</strong>
 |
| </li>
 |
| </ul>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| Traceability supports project tracking by assuring that requirements are implemented. For example, by verifying
 |
| that a design artifact and test exists for each requirement.
 |
| </p>
 |
| </blockquote>
 |
| <ul>
 |
| <li>
 |
| <strong>Ability to balance cost against benefit</strong>
 |
| </li>
 |
| </ul>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| Relating product components to the requirements allows you to compare benefits to costs.
 |
| </p>
 |
| </blockquote><br dir="ltr" />
 |
| <br /></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |