The benefits of aspects and aspect-oriented modelling are beginning to be recognized for requirements engineering activities. However, once aspects have been identified, the behaviour, structure, and pointcut expressions of aspects need to be modeled unobtrusively at the requirements level, allowing the engineer to seamlessly focus either on the behaviour and structure of the system without aspects or on the combined behaviour and structure. Furthermore, the modeling techniques for aspects should be the same as for the base system, ensuring that the engineer continues to work with familiar models. This position paper describes how, with the help of Use Case Maps, scenario-based aspects can be modeled visually and unobtrusively at the requirements level and with the same techniques as for non-aspectual systems. With Use Case Maps, aspects including pointcut expressions are modeled in a visual way which is generally considered the preferred choice for models of a high level of abstraction.

-- DanielAmyot - 03 Aug 2006


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

FormForVirtualLibrary edit

Title Visualizing Aspect-Oriented Requirements Scenarios with Use Case Maps
Authors G. Mussbacher, D, Amyot, and M. Weiss
Type Conference
Conference/Journal Title International Workshop on Requirements Engineering Visualization (REV 2006)
Publisher IEEE
Month September
Year 2006
DOI 10.1109/REV.2006.9
Keywords Aspect-oriented Requirements Engineering, Use Case Maps, Scenario Notations, User Requirements Notation
Topic attachments
I Attachment Action Size Date Who Comment
REV06.pdfpdf REV06.pdf manage 283 K 03 Aug 2006 - 14:04 DanielAmyot Pre-publication paper
Topic revision: r2 - 05 Nov 2009, AlirezaPourshahid
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