<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" 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="2006-05-01T03:37:44.000-0700" changeDescription="Added concept in accordance with Feb 23, 2006 minutes of RM SIG meeting."
    version="0.1">
  <mainDescription>&lt;p align=&quot;left&quot;>&#xD;
    Traceability is about understanding how high-level requirements (objectives, goals, aims, aspirations, expectations,&#xD;
    needs) are transformed into low-level requirements, how they are implemented, and how they are verified.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Using traceability can provide the following benefits &lt;a class=&quot;elementlinkwithusertext&quot; href=&quot;./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html#HUL05&quot; guid=&quot;_9ToeIB83Edqsvps02rpOOg&quot;>[HUL05]&lt;/a>:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Greater confidence in meeting objectives&lt;/strong>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;>&#xD;
    &lt;p>&#xD;
        Establishing traceability engenders greater reflection on how objectives are satisfied.&amp;nbsp; Traceability permits&#xD;
        coverage analysis to ensure that everything you have done everything that you agreed to do and only what you agreed&#xD;
        to do.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Ability to assess the impact of change&lt;/strong>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;>&#xD;
    &lt;p>&#xD;
        Traceability permits various forms of impact analysis that can be used to assess the impact of a proposed change on&#xD;
        the cost, schedule, and technical aspects of the project.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Improved accountability&lt;/strong>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;>&#xD;
    &lt;p>&#xD;
        Traceability provides greater clarity about how work contributes to the whole.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Ability to track progress&lt;/strong>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;>&#xD;
    &lt;p>&#xD;
        It is notoriously difficult to measure progress when all that you are doing is creating and revising artifacts.&#xD;
        Traceability processes allow precise measures of progress, such as: Is there a design artifact for each&#xD;
        requirement? Is there a test case for each requirement?.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;strong>Ability to balance cost against benefit&lt;/strong>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;>&#xD;
    &lt;p>&#xD;
        Relating product components to the requirements allows you to compare benefits to costs.&#xD;
    &lt;/p>&#xD;
&lt;/blockquote>&lt;br dir=&quot;ltr&quot; />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:ContentDescription>