Over the last decade, many aspect-oriented (AO) programming and modeling languages have been developed. Pointcut expressions are a key concept of each of these languages as they define the patterns that must be matched for aspects to be applied to the base. To date, most pointcut expressions are constrained to one particular notation – the one for which they were designed – even though a goal of aspect-oriented software development should be to encapsulate a concern through all phases of software development. Motivated by examples of aspects that require characteristics expressed in different notations to be matched by their pointcut expressions, we argue that there should be more focus on heterogeneous pointcut expressions that can span several notations from potentially different development phases. We demonstrate such pointcuts in an example modeled with the Aspect-oriented User Requirements Notation (AoURN) which combines notations for goal-oriented, scenario-based, and aspect-oriented modeling in one framework for requirements engineering.


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Heterogeneous Pointcut Expressions
Authors G. Mussbacher, D. Amyot
Type Conference
Conference/Journal Title Early Aspects Workshop @ ICSE09, Vancouver, Canada
Publisher IEEE CS
Month May
Year 2009
Pages 8-13
DOI 10.1109/EA.2009.5071577
Keywords Aspect-oriented User Requirements Notation, Aspects, Pointcut Expressions, Traceability
Topic attachments
I Attachment Action Size Date Who Comment
EA-ICSE09-HeterogeneousPointcuts.pdfpdf EA-ICSE09-HeterogeneousPointcuts.pdf manage 332 K 05 Nov 2009 - 14:57 DanielAmyot Prepublication version
Topic revision: r4 - 05 Nov 2009, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback