| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\guidances\concepts\traceability.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: traceability.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_eYtQQO0KEdqHTdbLTmC5IQ CRC: 2307195292 -->Traceability<!-- END:presentationName,_eYtQQO0KEdqHTdbLTmC5IQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_eYtQQO0KEdqHTdbLTmC5IQ CRC: 2269060618 -->Traceability is a term used to describe the establishment and maintenance of relationships between artifacts, such as a requirement and a design class or a requirement and a test case, so that you can track the completeness of work &lt;strong&gt; &lt;/strong&gt;and assess the impact of changes.<!-- END:briefDescription,_eYtQQO0KEdqHTdbLTmC5IQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-TksCtMgc0b4QqzwzniGvIw CRC: 3393829164 --><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. 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 /><!-- END:mainDescription,-TksCtMgc0b4QqzwzniGvIw --> |
| </body> |
| </html> |
