Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You or Your Team.

Learn More →

Understanding aspects: extended abstract

Understanding aspects: extended abstract Invited Talk Understanding Aspects (Extended Abstract) Mitchell Wand∗ College of Computer and Information Science Northeastern University Boston, MA 02115, USA wand@ccs.neu.edu 1 Background Since the mid-90 ™s, Kiczales and others have identi ed new limitations of traditional layered architectures for complex systems. The most serious of these new limitations is the problem of scattering. A typical large system requires many services, such as logging, locking, authentication, etc. While the functionality to implement a particular service may be located in a single module, the code to invoke the service is typically scattered across many modules. Kiczales ™s solution was to use a special-purpose language to give a declarative speci cation of where or when each service should be invoked. A service typically takes the form of a class called an aspect, possibly containing several methods. The potential points at which a method of an aspect can be invoked are called join points, and each method of the aspect is associated with a point cut, which is the set of join points at which it should act. Kiczales called this aspect-oriented programming (AOP). This idea has attracted widespread attention in the software-engineering community. Different aspect-oriented programming languages use different join-point http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png ACM SIGPLAN Notices Association for Computing Machinery

Understanding aspects: extended abstract

ACM SIGPLAN Notices , Volume 38 (9) – Sep 25, 2003

Loading next page...
 
/lp/association-for-computing-machinery/understanding-aspects-extended-abstract-3DpMb46OUa

References

References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.

Publisher
Association for Computing Machinery
Copyright
Copyright © 2003 by ACM Inc.
ISSN
0362-1340
DOI
10.1145/944746.944732
Publisher site
See Article on Publisher Site

Abstract

Invited Talk Understanding Aspects (Extended Abstract) Mitchell Wand∗ College of Computer and Information Science Northeastern University Boston, MA 02115, USA wand@ccs.neu.edu 1 Background Since the mid-90 ™s, Kiczales and others have identi ed new limitations of traditional layered architectures for complex systems. The most serious of these new limitations is the problem of scattering. A typical large system requires many services, such as logging, locking, authentication, etc. While the functionality to implement a particular service may be located in a single module, the code to invoke the service is typically scattered across many modules. Kiczales ™s solution was to use a special-purpose language to give a declarative speci cation of where or when each service should be invoked. A service typically takes the form of a class called an aspect, possibly containing several methods. The potential points at which a method of an aspect can be invoked are called join points, and each method of the aspect is associated with a point cut, which is the set of join points at which it should act. Kiczales called this aspect-oriented programming (AOP). This idea has attracted widespread attention in the software-engineering community. Different aspect-oriented programming languages use different join-point

Journal

ACM SIGPLAN NoticesAssociation for Computing Machinery

Published: Sep 25, 2003

There are no references for this article.