REFERENCES | Aspect-Oriented Software Development with Use Cases

1. AspectJ project. http://www.eclipse.org/aspectj/.

2. Basili, V. R. 1996. The role of experimentation in software engineering: Past, current, and future. In 18th Int'l Conf. Software Engineering (ICSE), (Berlin). IEEE, 442449.

3. Black, A., Hutchinson, N., Jul, E., and Levy, H. 1986. Object structure in the Emerald system. In 1st Conf. Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), (Portland, Oregon). ACM, 7886.

4. Boehm-Davis, D. A., Holt, R. W., and Schultz, A. C. 1992. The role of program structure in software maintenance. Int'l Journal of Man-Machine Studies 36, 1, 2163.

5. Curtis, B., Soloway, E., Brooks, R., Black, J., Ehrlich, K., and Ramsey, H. 1986. Software psychology: The need for an interdisciplinary program. Proc. IEEE 74, 8 (August), 10921106.

6. Dijkstra, E. W. 1976. A Discipline of Programming. Prentice-Hall, Englewood Cliffs, New Jersey.

7. Gosling, J., Joy, B., and Steele, G. L. 1996. The Java Language Specification. Addison-Wesley, Reading, Massachusetts.

8. Harrison, W. and Ossher, H. 1993. Subject-oriented programminga critique of pure objects. In 8th Conf. Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), (Washington, D. C.). ACM, 411428.

9. Irwin, J., Loingtier, J. M., Gilbert, J. R., Kiczales, G., Lamping, J., Mendhekar, A., and Shpeisman, T. 1997. Aspect-oriented programming of sparse matrix code. In Int'l Scientific Computing in Object-Oriented Parallel Environments (ISCOPE). LNCS, vol. 1343. Springer-Verlag, Berlin, 249256.

10. Jensen, K. and Wirth, N. 1974. Pascal: User Manual and Report, LNCS, vol. 18. Springer-Verlag, Berlin.

11. 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., vol. 1241. Springer-Verlag, Berlin. 220242.

12. Korson, T. and Vaishnavi, V. 1986. An empirical study of the effects of modularity on program modifiability. In 1st Workshop on Empirical Studies of Programmers, (Washington, D. C.). Ablex, Norwood, New Jersey, 168186.

13. Law, R. 1993. Evaluating the program slicing technique. SIAST TODAY 4, 6 (June), 6.

14. Law, R. 1997. An overview of debugging tools. ACM SIGSOFT Software Engineering Notes 22, 2 (March), 4347.

15. McGrath, J. 1995. Methodology matters: Doing research in the behavioral and social sciences. In Readings in Human-Computer Interaction: Toward the Year 2000. Morgan Kaufman, San Mateo, California, 152169.

16. Mendhekar, A., Kiczales, G., and Lamping, J. 1997. RG: A case-study for aspect-oriented programming. Tech. Rep. SPL-97-009, Palo Alto Research Center.

17. Murphy, G. C., Walker, R. J., and Baniassad, E. L.A. 1999. Evaluating emerging software development technologies: Lessons learned from assessing aspect-oriented programming. IEEE Transactions on Software Engineering 25, 4 (July/August), 438455.

18. Rational Corporation. UML summary. http:www.rational.com/uml/resources/documentation/summary/index.jtmpl.

19. Rombach, H. 1985. Impact of software structure on maintenance. In Conf. Software Maintenance (CSM), (Washington, D.C.). IEEE, 152160.

20. Scholtz, J. and Wiedenbeck, S. 1992. The use of unfamiliar programming languages by experienced programmers. In People and Computers VII: HCI'92. 4556.

21. Weiser, M. 1984. Program slicing. IEEE Transactions on Software Engineering 10, 4 (July), 352357.