| <?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><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_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.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> Establishing traceability engenders greater reflection on how objectives |
| are satisfied.&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.</p> |
| </blockquote> |
| <ul> |
| |
| <li> <strong>Ability to assess the impact of change </strong></li> |
| </ul> |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px"> |
| <p> 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.</p> |
| </blockquote> |
| <ul> |
| |
| <li><strong> Improved accountability </strong></li> |
| </ul> |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px"> |
| |
| <p> Traceability provides great clarity about how work contributes to the |
| whole. </p> |
| </blockquote> |
| <ul> |
| <li><strong> Ability to track progress </strong></li> |
| </ul> |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px"> |
| |
| <p> 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?. </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> |