Effort and quality of recovering requirements-to-code traces: Two exploratory experiments

Proceedings of the 2010 18th IEEE International Requirements Engineering Conference, RE2010

Volumn , Issue , 2010, Pages 221-230

  Egyed, Alexander ^a   Graf, Florian ^a   Grünbacher, Paul ^a  

^a JOHANNES KEPLER UNIVERSITY LINZ   (Austria)

Author keywords

Exploratory experiments; Requirements traceability; Traceability effort and quality

Indexed keywords

COMPLEX CLASS; CONTROLLED ENVIRONMENT; EXPLORATORY EXPERIMENTS; FUNDAMENTAL RESEARCH; MAINTENANCE ACTIVITY; OPEN SOURCE SOFTWARE SYSTEMS; REQUIREMENTS TRACEABILITY; SOFTWARE DEVELOPMENT; SOFTWARE SYSTEMS; TRACEABILITY EFFORT AND QUALITY;

COMPUTER SOFTWARE MAINTENANCE; COMPUTER SOFTWARE SELECTION AND EVALUATION; OPEN SYSTEMS; RECOVERY; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN;

EXPERIMENTS;

EID: 78650314941     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2010.34     Document Type: Conference Paper

References (37)

1. O. C. Z. Gotel and A. C. W. Finkelstein. An analysis of the requirements traceability problem. In Proc. RE Conf., pp. 94-101. 1994.
2. M. Lindvall and K. Sandahl. Practical implications of traceability. Sw. Pract. Exper., 26(10):1161-1180, 1996.
3. B. Ramesh and M. Jarke. Toward reference models of requirements traceability. IEEE TSE, 27(1):58-93, 2001.
4. B. Ramesh, L. C. Stubbs, and M. Edwards. Lessons learned from implementing requirements traceability. Crosstalk-J of Defense Sw Eng, 8(4):11-15, 1995.
5. D. L. Parnas. Software aging. In Proc. ICSE, pp. 279- 287. 1994.
6. N. Aizenbud-Reshef, B. T. Nolan, J. Rubin, and Y. Shaham-Gafni. Model traceability. IBM Systems J, 45(3):515-526, 2006.
7. M. Deng, R. E. K. Stirewalt, and B. H. C. Cheng. Retrieval by construction: a traceability technique to support verification and validation of UML formalizations. IJSEKE, 15(5):837-872, 2005.
8. L. C. Briand, Y. Labiche, and T. Yue. Automated traceability analysis for UML model refinements. IST J, 51(2):512-527, 2009.
9. J. Cleland-Huang, G. Zemont, and W. Lukasik. A heterogeneous solution for improving the return on investment of requirements traceability. In 12th IEEE Int'l Conf. on RE, pp. 230-239. 2004.
10. A. de Lucia, R. Oliveto, F. Zurolo, and M. D. Penta. Improving comprehensibility of source code via traceability information: a controlled experiment. In 14th Int'l Conf. on Program Comprehension (ICPC 2006), pp. 317-326. 2006.
11. A. Egyed, S. Biffl,M. Heindl, and P. Grünbacher. Determining the cost-quality trade-off for automated software traceability. In Proc. ASE Conf., pp. 360-363. 2005.
12. J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi, and E. Romanova. Best practices for automated traceability. IEEE Computer, 40(6):27-35, 2007.
13. C. Duan and J. Cleland-Huang. Clustering support for automated tracing. In Proc. ASE Conf., pp. 244-253. 2007.
14. A. Egyed. A scenario-driven approach to traceability. In Proc. ICSE, pp. 123-132. 2001.
15. R. Koschke and J. Quante. On dynamic feature location. In Proc. ASE Conf., pp. 86-95. 2005.
16. G. Spanoudakis, A. Zisman, E. Pérez-Miñana, and P. Krause. Rule-based generation of requirements traceability relations. JSS, 72(2):105-127, 2004.
17. J. H. Hayes and A. Dekhtyar. Humans in the traceability loop: can't live with 'em, can't live without 'em. In Proc. 3rd Int'l WS on Traceability in emerging forms of sw. eng., pp. 20-23. 2005.
18. G. Antoniol, B. Caprile, A. Potrich, and P. Tonella. Design-code traceability recovery: selecting the basic linkage properties. Sci. Comput. Program., 40(2- 3):213-234, 2001.
19. A. Egyed and P. Grünbacher. Automating requirements traceability: Beyond the record & replay paradigm. In Proc. ASE Conf., pp. 163-171. 2002.
20. G. C. Murphy, D. Notkin, and K. J. Sullivan. Software reflexion models: Bridging the gap between design and implementation. IEEE TSE, 27(4):364-380, 2001.
21. A. Marcus and J. I.Maletic. Recovering documentationto- source-code traceability links using latent semantic indexing. In Proc. ICSE, pp. 125-137. 2003.
22. H. Muccini, A. Bertolino, and P. Inverardi. Using software architecture for code testing. IEEE TSE, 30(3):160-171, 2004.
23. L. G. P. Murta, A. van der Hoek, and C. M. L. Werner. Continuous and automated evolution of architecture-toimplementation traceability links. ASE J, 15(1):75-107, 2008.
24. B. Dagenais, S. Breu, F. W. Warr, and M. P. Robillard. Inferring structural patterns for concern traceability in evolving software. In Proc. ASE Conf., pp. 254-263. 2007.
25. J. Cleland-Huang, C. K. Chang, and M. J. Christensen. Event-based traceability for managing evolutionary change. IEEE TSE, 29(9):796-810, 2003.
26. K. Pohl. PRO-ART: Enabling requirements pretraceability. In Proc. ICRE, pp. 76-85. 1996.
27. H. U. Asuncion, F. François, and R. N. Taylor. An end-to-end industrial software traceability tool. In Proc. ESEC/FSE, pp. 115-124. 2007.
28. O. Gotel and A. Finkelstein. Extended requirements traceability: Results of an industrial case study. In Proc. RE Conf., p. 169ff. 1997.
29. C. Neumüller and P. Grünbacher. Automating software traceability in very small companies: A case study and lessons learned. In Proc. ASE Conf., pp. 145-156. 2006.
30. J. H. Hayes, A. Dekhtyar, S. K. Sundaram, and S. Howard. Helping analysts trace requirements: An objective look. In Proc. RE Conf., pp. 249-259. 2004.
31. A. Bianchi, G. Visaggio, and A. R. Fasolino. An exploratory case study of the maintenance effectiveness of traceability models. In 8th Int'l WS on Program Comprehension, p. 149ff. 2000.
32. A. Egyed, P. Grünbacher,M. Heindl, and S. Biffl. Valuebased requirements traceability: Lessons learned. In Proc. RE Conf., pp. 115-118. 2007.
33. A. Egyed, G. Binder, and P. Grünbacher. Strada: A tool for scenario-based feature-to-code trace detection and analysis. In Proc. ICSE Conf., pp. 41-42. 2007.
34. T. J. McCabe. A complexity measure. IEEE TSE, 2(4):308-320, 1976.
35. C.Wohlin, P. Runeson, M. Höst, M. C. Ohlsson, B. Regnell, and A.Wesslén. Experimentation in software engineering: an introduction. Kluwer Academic Publishers, 2000.
36. A. de Lucia, R. Oliveto, and G. Tortora. IR-based traceability recovery processes: An empirical comparison of "one-shot" and incremental processes. In Proc. ASE Conf., pp. 39-48. 2008.
37. M. Höst, B. Regnell, and C. Wohlin. Using students as subjects-a comparative study of students and professionals in lead-time impact assessment. Empirical Software Engineering, 5(3):201-214, 2000.