Obvious or Not? Regulating Architectural Decisions Using Aspect-Oriented Programming

Mati Shomrat, Amiram Yehudai

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

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.

Original languageEnglish
Title of host publication1st International Conference on Aspect-Oriented Software Development
EditorsG. Kinzales, G. Kiczales
Pages3-9
Number of pages7
StatePublished - 2002
Event1st International Conference on Aspect-Oriented Software Development (AOSD 2002) - Enschede, Netherlands
Duration: 22 Apr 200226 Apr 2002

Publication series

Name1st International Conference on Aspect-Oriented Software Development

Conference

Conference1st International Conference on Aspect-Oriented Software Development (AOSD 2002)
Country/TerritoryNetherlands
CityEnschede
Period22/04/0226/04/02

Fingerprint

Dive into the research topics of 'Obvious or Not? Regulating Architectural Decisions Using Aspect-Oriented Programming'. Together they form a unique fingerprint.

Cite this