Location of Repository

Aspect-Oriented Modelling: Issues and Misconceptions

By Saqib Iqbal and Gary Allen


Aspect-oriented programming is an extension to object-oriented programming. It introduces new constructs called “aspects” for representing crosscutting concerns in a system development. These constructs are somewhat similar to object oriented “classes” but they also have some clear differences in terms of characteristics. This complicated nature of aspects makes their modeling a difficult task. While working on the modeling of new design techniques for aspect oriented technology, we have come across some unresolved modeling issues and some misconceptions about the nature of aspects and their representation in software design. This paper highlights these misconceptions and outlines some important aspect-oriented modeling issues, such as the modular nature of aspects, their resemblance with classes, and their high coupling with the base program

Topics: QA75
Publisher: IEEE
Year: 2010
OAI identifier: oai:eprints.hud.ac.uk:9007

Suggested articles



  1. (2002). A UML-based AspectOriented Design Notation For Aspect” doi
  2. (2003). Analytical problems and AspectJ”
  3. (2005). Classpects, “Unifying aspectand object-oriented language design” doi
  4. (2009). Composite Application Guidance for WPF and Silverlight -
  5. (2002). Designing Aspect-Oriented Crosscutting in UML” doi
  6. (2007). Patterns of Aspect-Oriented Design”
  7. (1999). Subject-Oriented Design: Towards Improved Alignment of Requirements, Design and Code” doi
  8. (2004). Theme: An Approach for AspectOriented Analysis and Design” doi
  9. (2003). UML profile for aspect-oriented software development”
  10. (2002). Using a concept-based approach to aspect-oriented software design”

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.