Practical refactoring-based framework upgrade Export

@inproceedings{citeulike:6056712, abstract = {Although the API of a software framework should stay stable, in practice it often changes during maintenance. When deploying a new framework version such changes may invalidate plugins - modules that used one of its previous versions. While manual plugin adaptation is expensive and error-prone, automatic adaptation demands cumbersome specifications, which the developers are reluctant to write and maintain. Basing on the history of structural framework changes (refactorings), in our previous work we formally defined how to automatically derive an adaptation layer that shields plugins from framework changes. In this paper we make our approach practical. Two case studies of unconstrained API evolution show that our approach scales in a large number of adaptation scenarios and comparing to other adaptation techniques. The evaluation of our logic-based tool ComeBack! demonstrates that it can adapt efficiently most of the problem-causing API refactorings.}, address = {New York, NY, USA}, author = {\c{S}avga, Ilie and Rudolf, Michael and G\"{o}tz, Sebastian and Assmann, Uwe}, booktitle = {GPCE '08: Proceedings of the 7th international conference on Generative programming and component engineering}, citeulike-article-id = {6056712}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=1449939}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/1449913.1449939}, doi = {10.1145/1449913.1449939}, isbn = {978-1-60558-267-2}, keywords = {apitrafo, refactoring}, location = {Nashville, TN, USA}, pages = {171--180}, posted-at = {2009-11-02 15:52:51}, priority = {2}, publisher = {ACM}, title = {Practical refactoring-based framework upgrade}, url = {http://dx.doi.org/10.1145/1449913.1449939}, year = {2008} }

TY - CONF ID - citeulike:6056712 L3 - citeulike-article-id:6056712 N2 - Although the API of a software framework should stay stable, in practice it often changes during maintenance. When deploying a new framework version such changes may invalidate plugins - modules that used one of its previous versions. While manual plugin adaptation is expensive and error-prone, automatic adaptation demands cumbersome specifications, which the developers are reluctant to write and maintain. Basing on the history of structural framework changes (refactorings), in our previous work we formally defined how to automatically derive an adaptation layer that shields plugins from framework changes. In this paper we make our approach practical. Two case studies of unconstrained API evolution show that our approach scales in a large number of adaptation scenarios and comparing to other adaptation techniques. The evaluation of our logic-based tool ComeBack! demonstrates that it can adapt efficiently most of the problem-causing API refactorings. CY - Nashville, TN, USA SN - 978-1-60558-267-2 AD - New York, NY, USA EP - 180 TI - Practical refactoring-based framework upgrade PB - ACM T2 - GPCE '08: Proceedings of the 7th international conference on Generative programming and component engineering SP - 171 KW - apitrafo KW - refactoring AU - Şavga, Ilie AU - Rudolf, Michael AU - Götz, Sebastian AU - Assmann, Uwe PY - 2008/// UR - http://dx.doi.org/10.1145/1449913.1449939 ER -