ACM Home Page
Please provide us with feedback. Feedback
A study on exception detection and handling using aspect-oriented programming
Full text PdfPdf (128 KB)
Source International Conference on Software Engineering archive
Proceedings of the 22nd international conference on Software engineering table of contents
Limerick, Ireland
Pages: 418 - 427  
Year of Publication: 2000
ISBN:1-58113-206-9
Authors
Martin Lippert  Computer Science Department, SE Group University of Hamburg Vogt-Kölln-Str. 30 22527 Hamburg, Germany
Cristina Videira Lopes  Computer Science Laboratory, Xerox Palo Alto Research Center, 3333 Coyote Hill Rd., Palo Alto, CA
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Irish Comp Soc : Irish Computer Society
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 11,   Downloads (12 Months): 76,   Citation Count: 33
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/337180.337229
What is a DOI?

ABSTRACT

Aspect-Oriented Programming (AOP) is intended to ease situations that involve many kinds of code tangling. This paper reports on a study to investigate AOP's ability to ease tangling related to exception detection and handling. We took an existing framework written in Java™, the JWAM framework, and partially reengineered its exception detection and handling aspects using AspectJ™, an aspect-oriented programming extension to Java.We found that AspectJ supported implementations that drastically reduced the portion of the code related to exception detection and handling. In one scenario, we were able to reduce that code by a factor of 4. We also found that, with respect to the original implementation in plain Java, AspectJ provided better support for different configurations of exceptional behaviors, more tolerance for changes in the specifications of exceptional behaviors, better support for incremental development, better reuse, automatic enforcement of contracts in applications that use the framework, and cleaner program texts. We also found some weaknesses of AspectJ that should be addressed in the future.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
ANSI: American National Standard Programming Language PL/I, ANSI X3.53-1976. American Natioal Standards Institute, New York, 1976.
 
2
AspectJ Web Site, <http://www.aspectj.org/>.
3
 
4
A. P. Black: Exception Handling: The Case Against, Technical Report 82-01-02, Department of Computer Science, University of Washington, 1982. Reprinted in May 1983.
5
6
 
7
J. Bruno, U. H~lzle, M. Karaorman: jContractor: A Reflective Java Library to Support Design By Contract, Technical Report TRCS98-31, Department of Computer Science, University of California, Santa Barbara, December 1998.
 
8
F. Cristian: Exception Handling and Software Fault Tolerance, in IEEE Transactions on Computers, Vol. c-31, No. 6, pp. 531540, June 1982.
9
 
10
M. F. Dunn, J. C. Knight: Software Resuse In An Industrial Setting: A Case Study, IEEE, 1991.
 
11
12
13
 
14
JWAM framework Web Site, <http://www.jwam.de/>.
 
15
G. Kiczales, J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J.-M. Loingtier, J. Irwin: Aspect-Oriented Programming, in Proceedings of the 11 th European Conference on Object-Oriented Programming (ECOOP '97), Finland, Springer-Verlag, 1997, pp. 220-242.
 
16
17
 
18
R. E. Johnson, B. Foote: Designing Reusable Classes, in The Journal of Object-Oriented Programming, Vol. 1, No. 2, 1988, pp. 22-35.
 
19
20
 
21
 
22
 
23
 
24
 
25
26

CITED BY  33
 
 
 
 
 

Collaborative Colleagues:
Martin Lippert: colleagues
Cristina Videira Lopes: colleagues

Peer to Peer - Readers of this Article have also read: