Enhancing base-code protection in aspect-oriented programs

ABSTRACT

Aspect-oriented programming (AOP) promises to localize concerns that inherently crosscut the primary structural decomposition of a software system. Localization of concerns is critical to parallel development, maintainability, modular reasoning, and program understanding. However, AOP as it stands today causes problems in exactly these areas, defeating its purpose and impeding its adoption. First, the need to open up systems' modules for aspects' interaction competes with the need to protect those modules against possible fault injection by aspects. Second, since aspects are written in terms of base code interfaces, base system components must be stable before aspect components can be developed. This dependency hinders parallel development. This work proposes a language-based solution that allows base code classes to regulate aspect invasiveness, and provides loose coupling of aspects and base code.

REFERENCES

• 1: J. Aldrich. Open modules: Modular reasoning about advice. In ECOOP '05, pages 144--168, 2005.
• 2: Pavel Avgustinov , Aske Simon Christensen , Laurie Hendren , Sascha Kuzins , Jennifer Lhoták , Ondřej Lhoták , Oege de Moor , Damien Sereni , Ganesh Sittampalam , Julian Tibble, abc: an extensible AspectJ compiler, Proceedings of the 4th international conference on Aspect-oriented software development, p.87-98, March 14-18, 2005, Chicago, Illinois [doi>10.1145/1052898.1052906]
• 3: C. Clifton, G. T. Leavens, and J. Noble. Mao: Ownership and effects for more effective reasoning about aspects. In ECOOP '07, pages 451--475, 2007.
• 4: Torbjörn Ekman , Görel Hedin, The JastAdd system — modular extensible compiler construction, Science of Computer Programming, v.69 n.1-3, p.14-26, December, 2007 [doi>10.1016/j.scico.2007.02.003]
• 5: William G. Griswold , Kevin Sullivan , Yuanyuan Song , Macneil Shonle , Nishit Tewari , Yuanfang Cai , Hridesh Rajan, Modular Software Design with Crosscutting Interfaces, IEEE Software, v.23 n.1, p.51-60, January 2006 [doi>10.1109/MS.2006.24]
• 6: A. P. Guide. The AspectJ programming guide. http://www.eclipse.org/aspectj/doc/released/progguide/.
• 7: K. Hoffman and P. Eugster. Bridging java and AspectJ through explicit join points. Technical Report ejp-200705-1, Purdue University, 2007.
• 8: I. Jacobson. A case for aspects. Software development Magazine, October 2003.
• 9: Ramnivas Laddad, AspectJ in Action: Practical Aspect-Oriented Programming, Manning Publications Co., Greenwich, CT, 2003
• 10: G. T. Leavens and C. Clifton. Multiple concerns in aspect-oriented language design: A language engineering approach to balancing benefits, with examples. Technical Report TR 07-01a, Iowa State University, 2007.
• 11: Hridesh Rajan , Gary T. Leavens, Ptolemy: A Language with Quantified, Typed Events, Proceedings of the 22nd European conference on Object-Oriented Programming, July 07-11, 2008, Paphos, Cypress [doi>10.1007/978-3-540-70592-5_8]

INDEX TERMS

Primary Classification:
  D. Software
  D.3 PROGRAMMING LANGUAGES

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

General Terms:
Algorithms, Design

Keywords:
aspect-oriented programming, aspectj