TRACEABILITY BETWEEN SOFTWARE SYSTEMS AND

SOFTWARE MODELS

Presented byVinay Gunnam

What is “Traceability” ?

The IEEE Standard Glossary of Software Engineering Terminology defines traceability as “the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another.”

Why is “Traceability” needed ?

Frequent changes in requirements Software design turning more complex

Reduction of cost of software development

Enhance the software development cycle

Directional Traceability

FORWARD Is the requirement implemented ?BACKWARD Is the implementation required ?

Features of a Traceability Technique

bidirectional requirement linking to system elements

capture of allocation rationale, accountability, and test/validation

identification of inconsistencies capabilities to view/trace links verification of requirements history of requirements changes

Traceability Techniques

Cross Referencing(tagging, numbering, indexing, track matrices)

Templates and Integration/Transformation documents

Restructuring

Automated/Semi-automated methods were also developed

Example: Track Matrices

Drawbacks of Traceability

Lack of a common definition

Conflicting underlying problems• Coarse granularity of traceable entities• Immature integration technology• Project longevity