A Framework for Traceability Tool Comparison

The need for automated traceability support has been advocated by various researchers and practitioners alike, as manual traceability is cumbersome and error-prone. Thus, many tools and approaches have been developed to overcome the limitations of manual traceability detection and usage. However, the large amount of available traceability tools is lacking suitable means for reasonable comparison based on welldefined criteria, which in turn complicates the process of choosing the appropriate tool. We propose and discuss a framework for classifying traceability tools, demonstrate its feasibility by organizing three tools according to its criteria, and illustrate how its criteria can be used when searching for a suitable tool.

[1]  Ethan V. Munson,et al.  Using a Hypertext Model for Traceability Link Conformance Analysis , 2003 .

[2]  Giuliano Antoniol,et al.  Benchmarks for Traceability , 2007 .

[3]  Mikael Lindvall,et al.  Traceability aspects of impact analysis in object-oriented systems , 1998, J. Softw. Maintenance Res. Pract..

[4]  Mikael Lindvall,et al.  Practical Implications of Traceability , 1996, Softw. Pract. Exp..

[5]  Aurora Vizcaíno,et al.  Requirements Engineering Tools , 2011, IEEE Software.

[6]  Eya Ben Charrada,et al.  Towards a benchmark for traceability , 2011, IWPSE-EVOL '11.

[7]  Patrick Mäder,et al.  Acquiring Tool Support for Traceability , 2012, Software and Systems Traceability.

[8]  Ilka Philippow,et al.  Rule-Based Maintenance of Post-Requirements Traceability Relations , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[9]  Patricio Letelier.  A Framework for Requirements Traceability in UML-based Projects , 2002 .

[10]  Jens von Pilgrim,et al.  A survey of traceability in requirements engineering and model-driven development , 2010, Software & Systems Modeling.

[11]  Giuliano Antoniol,et al.  Grand challenges, benchmarks, and TraceLab: developing infrastructure for the software traceability research community , 2011, TEFSE '11.

[12]  Muhammad Ali Babar,et al.  A comparative study of architecture knowledge management tools , 2010, J. Syst. Softw..

[13]  Alessandro Bianchi,et al.  An exploratory case study of the maintenance effectiveness of traceability models , 2000, Proceedings IWPC 2000. 8th International Workshop on Program Comprehension.

[14]  Thomas Olsson,et al.  Supporting traceability and inconsistency management between software artifacts , 2002, ICSE 2002.

[15]  Stefan Biffl,et al.  A value-based approach for understanding cost-benefit trade-offs during automated software traceability , 2005, TEFSE '05.