Modularisation and composition of aspectual requirements
Proceedings of the 2nd international conference on Aspect-oriented software development
Aspect-Oriented Analysis and Design
Aspect-Oriented Analysis and Design
Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series)
Aspect-Oriented Software Development with Use Cases (Addison-Wesley Object Technology Series)
Semantic-based weaving of scenarios
Proceedings of the 5th international conference on Aspect-oriented software development
Semantics-based composition for aspect-oriented requirements engineering
Proceedings of the 6th international conference on Aspect-oriented software development
Assessing the Applicability of Use Case Maps for Business Process and Workflow Description
MCETECH '08 Proceedings of the 2008 International MCETECH Conference on e-Technologies
Aspect-Oriented User Requirements Notation: Aspects in Goal and Scenario Models
Models in Software Engineering
MATA: A Unified Approach for Composing UML Aspect Models Based on Graph Transformation
Transactions on Aspect-Oriented Software Development VI
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
Extending the user requirements notation with aspect-oriented concepts
SDL'09 Proceedings of the 14th international SDL conference on Design for motes and mobiles
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Towards a taxonomy of syntactic and semantic matching mechanisms for aspect-oriented modeling
SAM'10 Proceedings of the 6th international conference on System analysis and modeling: about models
Hi-index | 0.00 |
Aspects use pointcut expressions to specify patterns that are matched against a base model, hence defining the base locations to which aspects are applied. The fragile pointcut problem is well-known in aspect-oriented modeling, as small changes in the base may lead to non-matching patterns. Consequently, aspects are not applied as desired. This is especially problematic for refactoring. Even though the meaning of the model has not changed, pointcut expressions may no longer match. We present an aspect-oriented modeling technique for scenarios that is refactoring-safe. The scenarios are modeled with Aspect-oriented Use Case Maps (AoUCM), an extension of the recent ITU standard User Requirements Notation. AoUCM takes the semantics of the modeling notation into account, thus ensuring pointcut expressions still match even after, for example, refactoring a single use case map into several hierarchical maps. Furthermore, AoUCM allows the composed model to be viewed without having to resolve complex layout issues. The general principles of our approach are also applicable to other aspect-oriented modeling notations.