Abstract

Once aspects have been identified during requirements engineering activities, 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 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 paper describes how, with the help of Use Case Maps, scenario-based aspects can be modeled at the requirements level unobtrusively and with the same techniques as for non-aspectual systems. Use Case Maps are a visual scenario notation under standardization by the International Telecommunication Union. With Use Case Maps, aspects as well as pointcut expressions are modeled in a visual way which is generally considered the preferred choice for models of a high level of abstraction.

-- DanielAmyot - 15 Mar 2007

Discussion

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

FormForVirtualLibrary edit

Title Visualizing Early Aspects with Use Case Maps
Authors G. Mussbacher, D. Amyot, and M. Weiss
Type Journal
Conference/Journal Title LNCS Journal on Transactions on Aspect-Oriented Software Development
Volume/Number 4620/2007
Editors J. Araújo, E. Baniassad
Publisher Springer
Month November
Year 2007
Pages 105-143
DOI 10.1007/978-3-540-75162-5_5
Keywords AoUCM, Aspect-Oriented Requirements Engineering, Use Case Maps, Scenario Notations, User Requirements Notation
Topic attachments
I Attachment Action Size Date Who Comment
TAOSD_2006_-_Visualizing_Aspects.pdfpdf TAOSD_2006_-_Visualizing_Aspects.pdf manage 376 K 10 Mar 2009 - 10:13 GunterMussbacher prepublication version
Topic revision: r3 - 12 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