Recovery of traceability links between software documentation and source code

International Journal of Software Engineering and Knowledge Engineering

Volumn 15, Issue 5, 2005, Pages 811-836

  Marcus, Andrian ^a   Maletic, Jonathan I ^b   Sergeyev, Andrey ^a  

^a Wayne State University   (United States)

^b KENT STATE UNIVERSITY   (United States)

Author keywords

Information retrieval; Latent semantic indexing; Traceability

Indexed keywords

AUTOMATION; CODES (SYMBOLS); COMPUTER SOFTWARE; INDEXING (OF INFORMATION); INFORMATION RETRIEVAL; SEMANTICS;

LATENT SEMANTIC INDEXING; SEMI-AUTOMATED RECOVERY; SOFTWARE DOCUMENTATION; TRACEABILITY;

SOFTWARE ENGINEERING;

EID: 27744487177     PISSN: 02181940     EISSN: None     Source Type: Journal    
DOI: 10.1142/S0218194005002543     Document Type: Article

References (47)

1. K. M. Anderson, R. N. Taylor, and E. J. J. Whitehead, Chimera: Hypermedia for heterogeneous software development enviroments, ACM Trans, on Information Systems 18(3) (2000) 211-245.
2. N. Anquetil and T. Lethbridge, Extracting concepts from file names; a new file clustering criterion, in Proc. 20th Int. Conf. on Software Engineering (ICSE'98), Kyoto, Japan, 1998, pp. 84-93.
3. G. Antoniol, G. Canfora, G. Casazza, and A. De Lucia, Information retrieval models for recovering traceability links between code and documentation, in Proc. IEEE Int. Conf. on Software Maintenance, San Jose, CA, Oct 11-14, 2000, pp. 40-51.
4. G. Antoniol, G. Canfora, G. Casazza, and A. De Lucia, Maintaining traceability links during object-oriented software evolution, Software -Practice and Experience 31(4) (2001) 331-355.
5. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, Tracing object-oriented code into functional requirements, in Proc. 8th Int. Workshop on Program Comprehension (IWPC'00), Limerick, Ireland, June 10-11, 2000, pp. 79-87.
6. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, Recovering traceability links between code and documentation, IEEE Trans. on Software Engineering 28(10) (2002) 970-983.
7. G. Antoniol, G. Canfora, A. De Lucia, and E. Merlo, Recovering code to documentation links in OO systems, in Proc. 6th IEEE Working Conf. on Reverse Engineering (WCRE'99), Atlanta, GA, October 6-8, 1999, pp. 136-144.
8. G. Antoniol, B. Caprile, A. Potrich, and P. Tonella, Design-code traceability for object oriented systems, Annals of Software Engineering 9(1/4) (2000) 35-58.
9. M. W. Berry, S. T. Dumais, and G. W. O'Brien, Using linear algebra for intelligent information retrieval, SIAM Review 37(4) (1995) 573-595.
10. W. Chan, R. Anderson, P. Beame, S. Burns, F. Modugno, D. Notkin, and J. Reese, Model checking large software specifications, IEEE Trans. on Software Engineering 24(7) (1998) 498-520.
11. J. Y. J. Chen and S.-C. Chou, Consistency management in a process environment, The Journal of Systems and Software 47 (1999) 105-110.
12. J. Cleland-Huang, C. K. Chang, and M. Christensen, Event-based tracebility for managing evolutionary change, IEEE Trans. on Software Engineering 29(9) (2003) 796-810.
13. G. Cugola, E. D. Nitto, A. Fugetta, and C. Ghezzi, A framework for formalizing inconsistencies and deviations in human-centered systems, ACM Trans. on Software Engineering and Methodology 5(3) (1996) 191-230.
14. J. Dag, B. Regnell, P. Carlshamre, M. Andersson, and J. Karls-son, A feasibility study of automated natural language requirements analysis in market-driven development, Requirements Engineering Journal 7(1) (2002) 20-33.
15. A. De Lucia, F. Fasano, R. Oliveto, and G. Tortora, Enhancing an artefact management system with traceability recovery features, in Proc. EEE Int. Conf. on Software Maintenance (ICSM'04), Chicago, IL, 2004, pp. 306-315.
16. S. Deerwester, S. T. Dumais, G. W. Furnas, T. K. Landauer, and R. Harshman, Indexing by latent semantic analysis, Journal of the American Society of Information Science 41 (1990) 391-407.
17. J. Dick, Rich traceability, in Proc. Automated Software Engineering, Edinburgh, Scotland, 2002.
18. S. T. Dumais, Improving the retrieval of information from external sources, Behavior Research Methods, Instruments, and Computers 23(2) (1991) 229-236.
19. L. H. Etzkorn and C. G. Davis, Automatically identifying reusable OO legacy code, IEEE Computer 30(10) (1997) 66-72.
20. C. Faloutsos and D. W. Oard, A survey of information retrieval and filtering methods, University of Maryland, Technical Report CS-TR-3514, August 1995.
21. O. Gotel and A. Ginkelstein, An analysis of the requirement traceability problem, in Proc. Int. Conf. on Requirements Engineering, Colorado Springs, Colorado, 1994, pp. 94-102.
22. J. Grundy, J. Hosking, and W. Mugridge, Inconsistency management for multiple-view software development environments, IEEE Trans. on Software Engineering 24(11) (1998) 960-981.
23. J. H. Hayes, A. Dekhtyar, and J. Osborne, Improving requirements tracebility via information retrieval, in Proc. 11th IEEE Int. Requirements Engineering Conference (RE'03), Monterey, CA, 2003, pp. 138-147.
24. C. L. Heitmeyer, R. D. Jeffords, and B. G. Labaw, Automated consistency checking of requirements specifications, ACM Trans, on Software Engineering and Methodology 5(3) (1996) 231-261.
25. A. Hunter and B. Nuseibeh, Managing inconsistent specifications: Reasoning, analysis, and action, A CM Trans. on Software Engineering and Methodology 7(4) (1998) 335-367.
26. A. Knethen, Automatic change support based on a trace model, in Proc. Automated Software Engineering, Edinburgh, Scotland, 2002.
27. T. K. Landauer, P. W. Foltz, and D. Laham, An introduction to latent semantic analysis, Discourse Processes 25(2&3) (1998) 259-284.
28. J. I. Maletic and A. Marcus, Supporting program comprehension using semantic and structural information, in Proc. 23rd Int. Conf. on Software Engineering (ICSE'01), Toronto, Ontario, Canada, May 12-19, 2001, pp. 103-112.
29. J. I. Maletic and N. Valluri, Automatic software clustering via latent semantic analysis, in Proc. 14th IEEE Int. Conf. on Automated Software Engineering (ASE'99), Cocoa Beach Florida, October 1999, pp. 251-254.
30. A. Marcus and J. I. Maletic, Identification of high-level concept clones in source code, in Proc. Automated Software Engineering, San Diego, CA, November 26-29, 2001, pp. 107-114.
31. A. Marcus and J. I. Maletic, Recovering documentation-to-source-code traceability links using latent semantic indexing, in Proc. 25th IEEE/ACM Int. Conf. on Software Engineering (ICSE'03), Portland, OR, May 3-10, 2003, pp. 125-137.
32. B. Nuseibeh, S. Easterbrook, and A. Russo, Leveraging inconsistency in software development, IEEE Computer 33(4) (2000) 24-29.
33. B. Nuseibeh, J. Kramer, and A. Finkelstein, A framework for expressing the relationships between multiple views in requirements specification, IEEE Trans. on Software Engineering 20(10) (1994) 760-773.
34. F. Pinheiro and J. Goguen, An object-oriented tool for tracing requirements, IEEE Software 13(2) (1996) 52-64.
35. K. Pohl, PRO-ART: Enabling requirements pre-traceability, in Proc. Int. Conf. on Requirements Engineering, Colorado Springs, Colorado, 1996, pp. 76-85.
36. B. Ramesh and M. Jarke, Toward reference model for requirements traceability, IEEE Trans. on Software Engineering, 27(1) (2001) 58-93.
37. S. Reiss, The desert environment, ACM Trans. on Software Engineering and Methodology 8(4) (1999) 297-342.
38. W. Robinson and S. Pawlowski, Managing requirements inconsistency with development goal monitors, IEEE Trans. on Software Engineering 25(6) (1999) 816-835.
39. G. Salton, Automatic Text Processing: The Transformation, Analysis and Retrieval of Information by Computer, Addison-Wesley, 1989.
40. G. Salton and M. McGill, Introduction to Modern Information Retrieval, McGraw-Hill, 1983.
41. I. Sommerville, P. Sawyer, and S. Viller, Managing process inconsistency using viewpoints, IEEE Trans. on Software Engineering, 25(6) (1999) 784-799.
42. G. Spanoudakis and A. Zisman, Inconsistency management in software engineering: Survey and open research issues, in Handbook of Software Engineering and Knowledge Engineering, ed. S. K. Chang, 2001, pp. 24-29.
43. D. Strasunskas, Traceability in collaborative systems development from lifecycle perspective - position paper, in Proc. Automated Software Engineering, Edinburgh, 2002.
44. M. Toranzo and J. Castro, A comprehensive traceability model to support the design of interactive systems, in Proc. ECOOP Workshops, 1999, pp. 283-284.
45. A. van Lamsweerde and E. Letier, Handling obstacles in goal-oriented requirements engineering, IEEE Trans. on Software Engineering 26(10) (2000) 978-1005.
46. R. Watkins and M. Neal, Why and how of requirements tracing, IEEE Software 11(4) (1994) 104-106.
47. A. Zisman and A. Kozlenkov, Knowledge-based approach to consistency management of UML specifications, in Proc. Automated Software Engineering (ASE'01), San Diego, CA, November 26-29, 2001, pp. 359-363.