Towards detecting and solving aspect conflicts and interferences using unit tests

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Towards detecting and solving aspect conflicts and interferences using unit tests

Full text

Pdf (192 KB)

Source

Aspect-oriented software development; Vol. 217 archive
Proceedings of the 5th workshop on Software engineering properties of languages and aspect technologies table of contents

Vancouver, British Columbia, Canada

Article No. 7

Year of Publication: 2007

ISBN:1-59593-656-1

Authors

André Restivo	Faculdade de Engenharia da Universidade do Porto
Ademar Aguiar	Faculdade de Engenharia da Universidade do Porto, INESC Port

Sponsor

AOSD-Europe : European Network of Excellent on Aspect-oriented Software Development

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 11, Downloads (12 Months): 97, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

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/1233843.1233850 What is a DOI?

ABSTRACT

Aspect Oriented Programming (AOP) is a programming paradigm that aims at solving the problem of crosscutting concerns being normally scattered throughout several units of an application.

Although an important step forward in the search for modularity, by breaking the notion of encapsulation introduced by Object Oriented Programming (OOP), AOP has proven to be prone to numerous problems caused by conflicts and interferences between aspects.

This paper presents work that explores the proven unit testing techniques as a mean to help developers describe the behavior of their aspects and to advise them about possible conflicts and interferences.

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	Ossher, H., Tarr, P.: Multi-dimensional separation of concerns and the Hyperspace approach. In: Software Architectures and Component Technology: The State of the Art in Research and Practice. (2000)
	2	Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J. M., Irwin, J.: Aspect-oriented programming. In Aksşit, M., Matsuoka, S., eds.: 11th Europeen Conf. Object-Oriented Programming. Volume 1241 of LNCS., Springer Verlag (1997) 220--242
	3	Filman, R., Friedman, D.: Aspect-oriented programming is quantification and obliviousness (2000)
	4	Bertrand Meyer, Applying "Design by Contract", Computer, v.25 n.10, p.40-51, October 1992 [doi>10.1109/2.161279 ]
	5	Tessier, F., Badri, M., Badri, L.: A model-based detection of conflicts between crosscutting concerns: Towards a formal approach. In: International Workshop on Aspect-Oriented Software Development. (2004)
	6	Katz, S.: Diagnosis of harmful aspects using regression verification (2004)
	7	Kienzle, J., Yu, Y., Xiong, J.: On composition and reuse of aspects. In: Software engineering Properties of Languages for Aspect Technologies. (2003)
	8	Balzarotti, D., Monga, M.: Using program slicing to analyze aspect oriented composition (2004)
	9	Störzer, M., Krinke, J.: Interference analysis for AspectJ. In: Foundations of Aspect-Oriented Languages (FOAL). (2003)
	10	Kessler, B., Tanter, É.: Analyzing interactions of structural aspects. ECOOP Workshop on Aspects, Dependencies and Interactions (ADI) (2006)
	11	Lagaisse, B., Joosen, W., De Win, B.: Managing semantic interference with aspect integration contracts. In: Software Engineering Properties of Languages and Aspect Technologies. (2004)