Transparency versus security: early analysis of antagonistic requirements
Proceedings of the 2010 ACM Symposium on Applied Computing
Extending the user requirements notation with aspect-oriented concepts
SDL'09 Proceedings of the 14th international SDL conference on Design for motes and mobiles
Workflow design using fragment composition: crisis management system design through ADORE
Transactions on aspect-oriented software development VII
Workflow design using fragment composition: crisis management system design through ADORE
Transactions on aspect-oriented software development VII
Using multiple feature models to design applications for mobile phones
Proceedings of the 15th International Software Product Line Conference, Volume 2
Using domain features to handle feature interactions
Proceedings of the Sixth International Workshop on Variability Modeling of Software-Intensive Systems
A commutative model composition operator to support software adaptation
ECMFA'12 Proceedings of the 8th European conference on Modelling Foundations and Applications
Towards correct product derivation in model-driven product lines
SAM'12 Proceedings of the 7th international conference on System Analysis and Modeling: theory and practice
Aspect interaction chart - a UML approach for modularizing aspect interaction conflicts
Proceedings of the 28th Annual ACM Symposium on Applied Computing
| Hi-index | 0.00 |
Interactions between dependent or conflicting aspects are a well-known problem with aspect-oriented development (and related paradigms). These interactions are potentially dangerous and can lead to unexpected or incorrect results when aspects are composed. To date, most aspect interaction detection methods have been based either on purely syntactic comparisons or have relied on heavyweight formal methods. We present a new approach that is based instead on lightweight semantic annotations of aspects. Each aspect is annotated with domain-specific markers and a separate influence model describes how semantic markers from different domains influence each other. Automated analysis can then be used both to highlight semantic aspect conflicts and to trade-off aspects. We apply this technique to early aspects, namely, aspect scenarios, because it is desirable to detect aspect interactions as early in the software lifecycle as possible. We evaluate the technique using an industrial case study and show that the technique detects interactions that cannot be discovered using syntactic techniques.