Abstract

Aspect-oriented programming (AOP) aims at managing crosscutting concerns at the programming language level. AOP is basically an evolution technique that may be used to augment a system with a new concern considered orthogonal to the others. The augmentation is applied automatically to a code base and is described with respect to a model of it. With AspectJ-like approaches this model has to be described as a set of join points, a solution that is in most cases too low level. Programmers should instead have the power of abstracting from the code base the model they prefer. Then, the augmentations described with respect to this specific model can be woven into the original system. Since the model introduced is specific to the concern the designer is trying to tackle, it may explicitly express design decisions,

Citations

34	Open Modules: “A Proposal for Modular Reasoning in Aspect-Oriented Programming”, Carnegie Mellon - Aldrich
15	Modular Reasoning, and the Behavioral Subtyping Analogy - Clifton, Leavens, et al.
14	Aspect weaving by graph rewriting - ASSMANN, LUDWIG - 1999
6	L.: Translating java code to graph transformation systems - Corradini, Dotti, et al.
5	Using program slicing to analyze aspectoriented composition - Balzarotti, Monga - 2004