Modeling aspects with UML's class, sequence and state diagrams in an industrial setting

  • Authors:
  • Alex Bustos;Yadran Eterovic

  • Affiliations:
  • Pontificia Universidad Católica de Chile, Cursor Ltd., Santiago;Pontificia Universidad Católica de Chile, Santiago, Chile

  • Venue:
  • SEA '07 Proceedings of the 11th IASTED International Conference on Software Engineering and Applications
  • Year:
  • 2007

Quantified Score

Hi-index 0.00

Visualization

Abstract

Aspect oriented programming allows software developers to modularize crosscutting concerns. While the emphasis has been on program implementation, it has been argued that applying aspect orientation at the design level can also be beneficial. However, we lack a convenient---i.e., both simple and expressive---notation to represent such designs, in particular, for fast, agile developments. In this paper, we describe a UML-based design notation to model the main concepts of aspects, their behavior, and their relationships with the base system. The notation uses UML's class, sequence, and state diagrams, to which it adds few new elements to model pointcut specification, pointcut activation, and the aspects' internal behavior; pointcut specifications can be modeled at three levels of detail. The notation is being used by a company that works on short projects, with limited time for design activities.