<?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" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="-TksCtMgc0b4QqzwzniGvIw" name="traceability_1,_eYtQQO0KEdqHTdbLTmC5IQ" guid="-TksCtMgc0b4QqzwzniGvIw" authors="Chris Sibbald" changeDate="2006-05-01T15:37:44.378-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;&gt; 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. 
&lt;/p&gt;
&lt;p&gt;
    Using traceability can provide the following benefits &lt;a class=&quot;elementlinkwithusertext&quot;
    href=&quot;./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html#HUL05&quot;
    guid=&quot;_9ToeIB83Edqsvps02rpOOg&quot;&gt;[HUL05]&lt;/a&gt;:
&lt;/p&gt;
&lt;ul&gt;
    
  &lt;li&gt; &lt;strong&gt;Greater confidence in meeting objectives &lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    
  &lt;p&gt; Establishing traceability engenders greater reflection on how objectives 
    are satisfied.&amp;nbsp; Traceability permits coverage analysis to ensure that 
    everything you have done everything that you agreed to do and only what you 
    agreed to do.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
    
  &lt;li&gt; &lt;strong&gt;Ability to assess the impact of change &lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt; 
  &lt;p&gt; Traceability permits various forms of impact analysis that can be used to 
    assess the impact of a proposed change on the cost, schedule, and technical 
    aspects of the project.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
    
  &lt;li&gt;&lt;strong&gt; Improved accountability &lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    
  &lt;p&gt; Traceability provides great clarity about how work contributes to the 
    whole. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt; Ability to track progress &lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    
  &lt;p&gt; It is notoriously difficult to measure progress when all that you are doing 
    is creating and revising artifacts. Traceability processes allow precise measures 
    of progress, such as: Is there a design artifact for each requirement? Is 
    there a test case for each requirement?. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;ul&gt;
    
  &lt;li&gt;&lt;strong&gt; Ability to balance cost against benefit &lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;blockquote dir=&quot;ltr&quot; style=&quot;MARGIN-RIGHT: 0px&quot;&gt;
    
  &lt;p&gt; Relating product components to the requirements allows you to compare benefits 
    to costs. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;br dir=&quot;ltr&quot; /&gt;
&lt;br /&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>