Implementing product line variabilities
SSR '01 Proceedings of the 2001 symposium on Software reusability: putting software reuse in context
Adding trace matching with free variables to AspectJ
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Eclipse: Building Commercial-Quality Plug-ins (2nd Edition) (Eclipse)
Eclipse: Building Commercial-Quality Plug-ins (2nd Edition) (Eclipse)
When to use features and aspects?: a case study
Proceedings of the 5th international conference on Generative programming and component engineering
Automated Inference of Pointcuts in Aspect-Oriented Refactoring
ICSE '07 Proceedings of the 29th international conference on Software Engineering
A decision model for implementing product lines variabilities
Proceedings of the 2008 ACM symposium on Applied computing
Extracting and evolving mobile games product lines
SPLC'05 Proceedings of the 9th international conference on Software Product Lines
A taxonomy of software product line reengineering
Proceedings of the Eighth International Workshop on Variability Modelling of Software-Intensive Systems
| Hi-index | 0.01 |
When restructuring variabilities in Software Product Lines (SPL), due to the great variety of existing mechanisms - such as Inheritance, Configuration Files, Aspect-Oriented Programming etc, developers may spend time and effort to decide which mechanism to use and which refactorings should be applied. To help on this task, we propose in this paper a tool capable of recommending refactorings based on some mechanisms. By applying the recommendations of our tool, bad smells such as cloned code may be removed and the modularity of the features is improved.