Cross-artifact traceability using lightweight links

Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE 2009

Volumn , Issue , 2009, Pages 57-64

  Ratanotayanon, Sukanya ^a   Sim, Susan Elliott ^a   Raycraft, Derek J ^a  

^a 5226 Donald Bren Hall   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

FEATURE MAP; PRECISION AND RECALL; SOFTWARE LIFE CYCLES; SOURCE CODES; TRACEABILITY LINKS;

COMPUTER SOFTWARE;

EID: 70349902775     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/TEFSE.2009.5069584     Document Type: Conference Paper

References (26)

1. O.C.Z. Gotel and C.W. Finkelstein, "An Analysis of the Requirements Traceability Problem," in RE'94: Proceedings of the First International Conference on Requirements Engineering, pp. 94-101, 1994.
2. L. Naslavsky, T.A. Alspaugh, D.J. Richardson and H. Ziv, "Using Scenarios to Support Traceability," in TEFSE '05: Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 25-30, 2005.
3. P. Haumer, K. Pohl, K. Weidenhaupt and M. Jarke, "Improving Reviews by Extended Traceability," in HICSS '99: Proceedings of the 32th Annual Hawaii International Conference on System Sciences-Volume 3, pp. 3052, 1999.
4. C. Lee, L. Guadagno and X. Jia, "An Agile Approach to Capturing Requirements and Traceability," in TEFSE'03: Proceeding of the 1st International Workshop on Traceability in Emerging Forms of Software Engineering, 2003.
5. T. Hughes and C. Martin, "Design Traceability of Complex Systems," in HICS '98: Proceedings of the 4th Symposium on Human Interaction with Complex Systems, pp. 37, 1998.
6. L.G.P. Murta, A. Van De Hoek and C.M.L. Werner, "ArchTrace: Policy-Based Support for Managing Evolving Architecture-to-Implementation Traceability Links," in ASE '06: Proceedings of the 21st IEEE International Conference on Automated Software Engineering, pp. 135-144, 2006.
7. J. Cleland-Huang and C.K. Chang, "Event-Based Traceability for Managing Evolutionary Change," IEEE Transactions on Software Engineering, vol. 29, pp. 796, 2003.
8. S.G. Eick, J.L. Steffen and E.E. Sumner, "Seesoft-A Tool for Visualizing Line Oriented Software Statistics," IEEE Transactions on Software Engineering, vol. 18, pp. 957, 1992.
9. B. Azelborn, "Building a Better Traceability Matrix with DOORS," in Telelogic INDOORS Europe, 2000.
10. I. Spence and L. Probasco, "Traceability Strategies for Managing Requirements with use Cases," in Rational Software White Paper, 1999.
11. F.A.C. Pinheiro and J.A. Goguen, "An Object-Oriented Tool for Tracing Requirements," IEEE Software, vol. 13, pp. 52, 1996.
12. M.P. Robillard and G.C. Murphy, "Representing Concerns in Source Code," ACM Transaction on Software Engineering Methodology, vol. 16, pp. 3, 2007.
13. M. Kersten and G.C. Murphy, "Mylar: A Degree-of-Interest Model for IDEs," in AOSD '05: Proceedings of the 4th International Conference on Aspect-Oriented Software Development, pp. 159-168, 2005.
14. A. Egyed, "A Scenario-Driven Approach to Traceability," in ICSE '01, pp. 123-132, 2001.
15. J. Sayyad-Shirabad, T.C. Lethbridge and S. Lyon, "A Little Knowledge can Go a Long Way Towards Program Understanding," in IWPC '97: Proceedings of the 5th International Workshop on Program Comprehension, pp. 111, 1997.
16. S. Yadla, J. H. Hayes and A. Dekhtyar, "Tracing Requirements to Defect Reports: An Application of Information Retrieval Techniques," Innovations in Systems and Software Engineering a NASA Journal, vol. 1, pp. 116, 2005.
17. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia and E. Merlo, "Recovering Traceability Links between Code and Documentation," IEEE Transactions on Software Engineering, vol. 28, pp. 970-983, 2002.
18. A. De Lucia, F. Fasano, R. Oliveto and G. Tortora, "Enhancing an Artefact Management System with Traceability Recovery Features," in ICSM '04: Proceedings of the 20th IEEE International Conference on Software Maintenance, pp. 306-315, 2004.
19. A. Marcus and J.I. Maletic, "Recovering Documentation-to-Source-Code Traceability Links using Latent Semantic Indexing," in ICSE '03, pp. 125-135, 2003.
20. A. De Lucia, R. Oliveto, F. Zurolo and M. Di Penta, "Improving Comprehensibility of Source Code Via Traceability Information: A Controlled Experiment," in ICPC '06: Proceedings of the 14th IEEE International Conference on Program Comprehension, pp. 317-326, 2006.
21. D. Cubranic and G.C. Murphy, "Hipikat: Recommending Pertinent Software Development Artifacts," in ICSE '03, pp. 408-418, 2003.
22. XPlanner. http://www.xplanner.org/2007.
23. jEdit. http://www.jedit.org/2008.
24. WinMerge. http://winmerge.org/2008.
25. S.P. Reiss, "Tracking Source Locations," in ICSE '08, pp. 11-20, 2008.
26. G. Canfora, L. Cerulo and M. Di Penta, "Identifying Changed Source Code Lines from Version Repositories," in MSR '07: Proceedings of the Fourth International Workshop on Mining Software Repositories, pp. 14, 2007.