Automatically inferring concern code from program investigation activities

Proceedings - 18th IEEE International Conference on Automated Software Engineering, ASE 2003

Volumn , Issue , 2003, Pages 225-234

  Robillard, Martin P ^a   Murphy, Gail C ^a  

^a UNIVERSITY OF BRITISH COLUMBIA   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING LANGUAGES; OBJECT ORIENTED PROGRAMMING; SOFTWARE ENGINEERING;

LATE STAGE; OBJECT-ORIENTED SYSTEM; PROGRAM EVOLUTION; PROGRAM INVESTIGATION; SOURCE CODES;

CODES (SYMBOLS);

EID: 18144393987     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASE.2003.1240310     Document Type: Conference Paper

References (16)

1. M. Fowler. Refactoring-Improving the Design of Existing Code. Object Technologies Series. Addison-Wesley, 2000.
2. K. B. Gallagher and J. R. Lyle. Using program slicing in software maintenance. IEEE Transactions on Software Engineering, 17(8):751-761, August 1991.
3. G. Kiczales, J. Lamping, A. Menhdhekar, C. Maeda, C. Lopes, J.-M. Loingtier, and J. Irwin. Aspect-oriented programming. In M. Akşit and S. Matsuoka, editors, Proceedings of the 11th European Conference on Object-oriented Programming, volume 1241 of Lecture Notes in Computer Science, pages 220-242. Springer-Verlag, June 1997.
4. S. Letovsky and E. Soloway. Delocalized plans and program comprehension. IEEE Software, 3(3):41-49, May 1986.
5. K. Lukoit, N. Wilde, S. Stowell, and T. Hennessey. TraceGraph: Immediate visual location of software features. In Proceedings of the International Conference on Software Maintenance, pages 33-39. IEEE Computer Society, October 2000.
6. Object Technology International, Inc. Eclipse platform technical overview. White Paper, July 2001.
7. M. P. Robillard and G. C. Murphy. Concern Graphs: Finding and describing concerns using structural program dependencies. In Proceedings of the 24th International Conference on Software Engineering, pages 406-416, May 2002.
8. M. P. Robillard and G. C. Murphy. A study of program evolution involving scattered concerns. Technical Report CS-2003-06, Department of Computer Science, University of British Columbia, March 2003.
9. M. Siff and T. Reps. Identifying modules via concept analysis. IEEE Transactions on Software Engineering, 25(6):749-768, November/December 1999.
10. E. Soloway, J. Pinto, S. Letovsky, D. Littman, and R. Lam-pert. Designing documentation to compensate for delocalized plans. Communications of the ACM, 31(11):1259-1267, November 1988.
11. F. Tip. A survey of program slicing techniques. Journal of Programming Languages, 3(3):121-189, September 1995.
12. A. van Deursen and T. Kuipers. Identifying objects using cluster and concept analysis. In Proceedings of the 21st International Conference on Software Engineering, pages 246-255. ACM, May 1999.
13. M. Weiser. Program slicing. IEEE Transactions on Software Engineering, 10(4):352-357, July 1984.
14. N. Wilde and C. Casey. Early field experiences with the software reconnaissance technique for software comprehension. In Proceedings of the International Conference on Software Maintenance, pages 312-318. IEEE, 1996.
15. N. Wilde, J. A. Gomez, T. Gust, and D. Strasburg. Locating user functionality in old code. In Proceedings of the Conference on Software Maintenance, pages 200-205. IEEE Computer Society, November 1992.
16. N. Wilde and M. Scully. Software reconnaissance: Mapping program features to code. Journal of Software Maintenance: Research and Practice, 7:49-62, January 1995.