Rights statement: This is the author’s version of the work. It is posted here for your personal use. Not for redistribution. The definitive version was published in the following publication: SPLASH Companion’15, October 25–30, 2015, Pittsburgh, PA, USA c 2015 ACM. 978-1-4503-3722-9/15/10... http://dx.doi.org/10.1145/2814189.2814195
Accepted author manuscript, 158 KB, PDF document
Available under license: CC BY: Creative Commons Attribution 4.0 International License
Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review
Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review
}
TY - GEN
T1 - Fraglight
T2 - shedding light on broken pointcuts in evolving aspect-oriented software
AU - Khatchadourian, Raffi
AU - Rashid, Awais
AU - Masuhara, Hidehiko
AU - Watanabe, Takuya
N1 - This is the author’s version of the work. It is posted here for your personal use. Not for redistribution. The definitive version was published in the following publication: SPLASH Companion’15, October 25–30, 2015, Pittsburgh, PA, USA c 2015 ACM. 978-1-4503-3722-9/15/10... http://dx.doi.org/10.1145/2814189.2814195
PY - 2015
Y1 - 2015
N2 - Pointcut fragility is a well-documented problem in Aspect-Oriented Programming; changes to the base-code can lead to join points incorrectly falling in or out of the scope of pointcuts. Deciding which pointcuts have broken due to base-code changes is a daunting venture, especially in large and complex systems. We demonstrate an automated tool called FRAGLIGHT that recommends a set of pointcuts that are likely to require modification due to a particular base-code change. The underlying approach is rooted in harnessing unique and arbitrarily deep structural commonality between program elements corresponding to join points selected by a pointcut in a particular software version. Patterns describing such commonality are used to recommend pointcuts that have potentially broken with a degree of confidence as the developer is typing. Our tool is implemented as an extension to the Mylyn Eclipse IDE plug-in, which maintains focused contexts of entities relevant to a task.
AB - Pointcut fragility is a well-documented problem in Aspect-Oriented Programming; changes to the base-code can lead to join points incorrectly falling in or out of the scope of pointcuts. Deciding which pointcuts have broken due to base-code changes is a daunting venture, especially in large and complex systems. We demonstrate an automated tool called FRAGLIGHT that recommends a set of pointcuts that are likely to require modification due to a particular base-code change. The underlying approach is rooted in harnessing unique and arbitrarily deep structural commonality between program elements corresponding to join points selected by a pointcut in a particular software version. Patterns describing such commonality are used to recommend pointcuts that have potentially broken with a degree of confidence as the developer is typing. Our tool is implemented as an extension to the Mylyn Eclipse IDE plug-in, which maintains focused contexts of entities relevant to a task.
M3 - Conference contribution/Paper
SN - 9781450337229
SP - 17
EP - 18
BT - SPLASH Companion 2015 Companion Proceedings of the 2015 ACM SIGPLAN International Conference on Systems, Programming, Languages and Applications: Software for Humanity
PB - ACM
CY - New York
ER -