ACM Home Page
Please provide us with feedback. Feedback
Obvious or not?: regulating architectural decisions using aspect-oriented programming
Full text PdfPdf (516 KB)
Source Aspect-oriented software development archive
Proceedings of the 1st international conference on Aspect-oriented software development table of contents
Enschede, The Netherlands
COLUMN: Full papers table of contents
Pages: 3 - 9  
Year of Publication: 2002
ISBN:1-58113-469-X
Authors
Mati Shomrat  Tel-Aviv University, Tel-Aviv 69978, Israel
Amiram Yehudai  Tel-Aviv University, Tel-Aviv 69978, Israel and The Academic College of Tel-Aviv-Yaffo
Sponsors
CTIT : Centre for Telematics and Information Technology
IPA : Institute for Software and Arithmetic
KNAW : Koninklijke Nederlandse Akademie van Wetenschappen
PATO : Post Academisch Tecbnisch Onderwijs
University of Twente : University of Twente
NWO : Dutch Orgartisation for Scientific Research
IBMR : IBM Research
AITO : Association Internationale pour les Technologies Objets
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 14,   Downloads (12 Months): 41,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/508386.508388
What is a DOI?

ABSTRACT

The construction of complex, evolving software systems requires a high-level design model. However, this model tends not to be enforced on the system, leaving room for the implementors to diverge from it, thus differentiating the designed system from the actual implemented one. The essence of the problem of enforcing such models lies in their globality. The principles and guidelines conveyed by these models cannot be localized in a single module, they must be observed everywhere in the system. A mechanism for enforcement needs to have a global view of the system and to report breaches in the model at the time they occur.Aspect-Oriented Programming has been proposed as a new software engineering approach. Unlike contemporary software engineering methods, which are module centered, Aspect Oriented Programming provides mechanisms for the definition of cross-module interactions. We explore the possibility of using Aspect-Oriented Programming in general and the AspectJ programming language in particular for the enforcement of design models.


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
 
2
 
3
Carolyn K. Duby, Scott Meyers, and Steven P. Reiss. CCEL: A metalanguage for C++. In USENIX C++ Technical Conference Proceedings, pages 99-115, Portland, OR, 10-13 1992. USENIX Assoc. Berkeley, CA, USA.
 
4
 
5
 
6
Gregor Kiczales, John Lamping, Anurag Menhdhekar, Chris Maeda, Cristina Lopes, Jean-Marc Loingtier, and John Irwin. Aspect-oriented programming. In Mehmet Akşit and Satoshi Matsuoka, editors, ECOOP '97 --- Object-Oriented Programming 11th European Conference, Jyväskylä, Finland, volume 1241, pages 220-242. Springer-Verlag, New York, NY, 1997.
7
 
8
 
9
 
10
 
11
 
12
 
13
14
15
 
16
Carolyn K. Duby, Scott Meyers, and Steven P. Reiss, CCEL: A metalanguage for C++, USENIX C++ Technical Conference Proceedings (Portland, OR), USENIX Assoc. Berkeley, CA, USA, 10-13 1992, pp. 99-115.
17

CITED BY  8

Collaborative Colleagues:
Mati Shomrat: colleagues
Amiram Yehudai: colleagues