REFERENCES

1. Arnold, R. and Bohner, S. 1996. Software Change Impact Analysis. IEEE Computer Society Press, Los Alamitos, California.

2. AspectJ Project. http://www.eclipse.org/aspectj/.

3. Bacon, D. F. 1997. Fast and effective optimization of statically typed object-oriented languages. Ph.D. thesis, University of California, Berkeley.

4. Baldwin, C. Y. and Clark, K. B. 2000. Design Rules: The Power of Modularity Volume 1. MIT Press, Cambridge, Massachusetts.

5. Baniassad, E., Murphy, G., Schwanninger, C., and Kircher, M. 2002. Managing crosscutting concerns during software evolution tasks: An inquisitive study. In 1st Int'l Conf. Aspect-Oriented Software Development (AOSD), (Enschede, The Netherlands), G. Kiczales, Ed. ACM, 120126.

6. Chen, K. and Rajlich, V. 2000. Case study of feature location using dependence graph. In 8th Int'l Workshop on Program Comprehension. IEEE, 241247.

7. Dean, J., Grove, D., and Chambers, C. 1995. Optimization of object-oriented programs using static class hierarchy analysis. In ECOOP'95 Object-Oriented Programming, 9th European Conference, W. Olthoff, Ed. LNCS, vol. 952. Springer-Verlag, Berlin. 77101.

8. Eick, S. G., Steffen, J. L., and Sumner, Jr.,E. E. 1992. Seesofta tool for visualizing line-oriented software statistics. IEEE Transactions on Software Engineering 18, 11, 957968.

9. Eisenbarth, T., Koschke, R., and Simon, D. 2003. Locating features in source code. IEEE Transactions on Software Engineering 29, 3, 210224.

10. Griswold, W. G., Yuan, J. J., and Kato, Y. 2001. Exploiting the map metaphor in a tool for software evolution. In 23rd Int'l Conf. Software Engineering (ICSE), (Toronto). IEEE, 265274.

11. Hannemann, J. The aspect mining tool web site. http://www.cs.ubc.ca/labs/spl/projects/amt.html.

12. Hannemann, J. and Kiczales, G. 2001. Overcoming the prevalent decomposition in legacy code. In Workshop on Advanced Separation of Concerns in Software Engineering (ICSE), (Toronto). http://www.research.ibm.com/hyperspace/workshops/icse2001/Papers/hannemann.pdf.

13. Kiczales, G., Hilsdale, E., Hugunin, J., Kersten, M., Palm, J., and Griswold, W. G. 2001. An overview of AspectJ. In ECOOP 2001Object-Oriented Programming, 15th European Conference, (Budapest), J. L. Knudsen, Ed. LNCS, vol. 2072. Springer-Verlag, Berlin, 327353.

14. Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J. M., and Irwin, J. 1997. Aspect-oriented programming. In ECOOP'97 Object-Oriented Programming, 11th European Conference, M. Akit and S. Matsuoka, Eds. 15. Leong, W. The Aspect Browser web site. http://www.cs.ucsd.edu/users/wgg/Software/AB.

16. Leong, W. Y. 2002. Using the atlas metaphor to assist cross-cutting software changes. M.S. thesis, University of California, San Diego.

17. Letovsky, S. and Solloway, E. 1986. Delocalized plans and program comprehension. IEEE Software 3, 3, 4149.

18. Parnas, D. L. 1972. On the criteria to be used in decomposing systems into modules. Comm. ACM 15, 12 (Dec.), 10531058.

19. Parnas, D. L. 1976. On the design and development of program families. IEEE Transactions on Software Engineering SE-2, 1 (Mar.), 19.

20. Pfleeger, S. and Bohner, S. 1990. A framework for software maintenance metrics. In Int'l Conf. Software Maintenance (ICSM), (San Diego). IESEE, 320327.

21. Robillard, M. P. The Jex home page. http://www.cs.ubc.ca/~mrobilla/jex/.

22. Robillard, M. P. The FEAT home page. http://www.cs.ubc.ca/labs/spl/projects/feat/.

23. Robillard, M. P. and Murphy, G. C. 2002. Concern Graphs: Finding and describing concerns using structural program dependencies. In Int'l Conf. Software Engineering (ICSE), (Orlando, Florida). IEEE, 406416.

24.Sim, S., Clarke, C., and Holt, R. 1998. Archetypal source code searching: A survey of software developers and maintainers. In Int'l Workshop on Program Comprehension, (Ischia, Italy). 180187. http://www.cs.toronto.edu/~simsuz/papers/iwpc98.pdf.

25. Singer, J., Lethbridge, T., Vinson, N., and Anquetil, N. 1997. An examination of software engineering work practices. In CASCON, (Toronto, Canada). 209223. http://wwwsel.iit.nrc.ca/seldocs/eassedocs/Cascon97Singer.pdf.

26. Soloway, E. and Erlich, K. 1984. Empirical studies of programmers knowledge. IEEE Transactions on Software EngineeringSE-10, 5, 595609.

27. Sullivan, K., Cai, Y., Hallen, B., and Griswold, W. 2001. The structure and value of modularity in design. In European Software Engineering Conference/ACM Symp. Foundations of Software Engineering, (Vienna, Austria). 99108. http://www.cs.virginia.edu/~sullivan/publications/UVa-CS-2001-13.pdf.

28. von Mayrhauser, A. and Vans, A. M. 1995. Program comprehension during software maintenance and evolution. IEEE Computer 28, 8, 4455.

29. Wilde, N., Gomez, J., Gust, T., and Strasburg, D. 1992. Locating user functionality in old code. In Int'l Conf. Software Maintenance (ICSM), (Orlando, Florida). IEEE, 200205.

30. Wong, W., Gokhale, S., Horgan, J., and Trivedi, K. 1999. Locating program features using execution slices. In Symp. Application-Specific Systems and Software Engineering and Technology, (Richardson, Texas) 192203. http://srel.ee.duke.edu/PAPERS/locating.pdf.