Designing and Developing Automated Refactoring Transformations: An Experience Report

Szőke, Gábor; Nagy, Csaba; Ferenć, Rudolf; Gyimóthy, Tibor

doi:10.1109/saner.2016.17

Cited by 15 publications

(11 citation statements)

References 16 publications

(12 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most of them were published in journals or conferences with high reputation, including IEEE Transactions on Software Engineering (TSE) and International Conference on Automated Software Engineering (ASE). 55Algebraic and cost-based optimization of refactoring sequences 37Search-based refactoring based on unfolding of graph transformation systems 57How we refactor, and how we know it (46) Identifying refactoring sequences for improving software maintainability (43) An empirical study of refactoring: Challenges and benefits at Microsoft 35FaultBuster: An automatic code smell refactoring toolset (64) Designing and developing automated refactoring transformations (65) Step 2: Define a final search string. Based on the pilot search, we decided to discard continuous refactoring from our search string, because many of the papers have used this term with purposes that extrapolates the scope of batch refactoring.…”

Section: Literature Review Protocolmentioning

confidence: 99%

“…Sequence of refactoring is commonly adopted by previous work such as (43,55,57,64) to refer to interrelated code transformations applied in conjunction. Additionally, batch refactoring has been more recently adopted by the literature (7,46,65).…”

Section: Literature Review Protocolmentioning

confidence: 99%

“…One particular study assumed that each code transformation into a batch should be applied in up to 60 seconds after the previous transformation (46), then the time spent for applying a batch can be minutes. Other studies (35,50,64,65) suggest do not constrain the time so that consecutive code transformations can be applied at any time.…”

Section: Batch Characteristicsmentioning

confidence: 99%

“…For instance, this work unlikely captures batches that last for more than an hour as a developer often has to intertwine refactoring edits with his other routine activities. Conversely, other studies do not constrain the time spent to apply these code transformations, thereby making possible to compute batch refactorings that last days, weeks, and even months to be completed (35,50,64,65,7). In these cases, the lack of a threshold may lead one to the consideration of non-cohesive batches.…”

Section: Conflict 3: How Long Does Applying a Batch Refactoring Last?mentioning

confidence: 99%

“…Table 4.1 describes the possible manifestations of each batch characteristic. Previous studies (35,43,46,64,65) have focused on some of these manifestations based on assumptions made by the authors. They have not empirically evaluated the frequency of these manifestations.…”

Section: Goal and Research Questionsmentioning

confidence: 99%

See 4 more Smart Citations

Understanding Characteristics and Structural Effects of Batch Refactorings in Practice

BIBIANO¹

View full text Add to dashboard Cite

First and foremost, I would like to thank God Almighty for the gift of living, growing up, and contributing the His plan the way I can. I also thank the Virgin Mary for being my role model and intercessor along the way. I am full of gratitude for my parents, Mrs. Lourinete Bibiano and Mr. Antonio Bibiano (in memoriam), my grandparents, brothers, and sister. Thanks for the kind support support. Especial thanks to Mr. José Pedro Luiz (in memoriam), my dear grandfather, for inspiring me to be a scientist. Thanks to all my friends for the support and patience along the years, especially Jedson Amaro, who helped me to reach my goals and was present in both happy and hard times, my dear friend Jakson Leao that brought me happiness and advice, and my brother Ladovanio Gomes that was my support all the time. Many people became special to my academic formation throughout this journey. I am grateful for their support along the last two years of study along my Master's course. I would like to thank Prof. Dr. Alessandro Garcia, my advisor, for believing in my potential as a scientist. Thanks for helping me reach my dreams. I also thank my dear friend MSc. Eduardo Fernandes who became my research colleague but also a friend for life. During the last two years, we grew together spiritually and academically. Thanks for believing and supporting me, even when I did not believe in myself. I am grateful for the reviews and improvements suggested to this Master's dissertation, including the literature review protocol. Thanks to Dr. Diego Cedrim e MSc. Isabella Ferreira for supporting me in the early phases of my research. You provided me with key support to build the code smells versus batch refactoring database. Thanks also to BS Daniel Oliveira for the support in collecting and validating data used in this work. I extend my thanks to all OPUS Research Group members and collaborators from other groups, especially Profs. Drs. Baldoino Fonseca (UFAL) and Marcos Kalinowski (PUC-Rio). I am thankful for your feedback aimed to shape the directions of my research. Especial thanks to the (anonymous) software development companies that provided me with data for analysis. Thanks to Profs. Drs. Leonardo Murta (UFF), Marcos Kalinowski (PUC-Rio), and Simone Barbosa (PUC-Rio) for kindly accepting to integrate this Master's dissertation defense committee. Doing science in Brazil is challenging and, in the context, I would like to thank all agencies that provided me with funding, especially the Brazilian National Council for Scientific and Technological Development (CNPq), plus the partner companies of the Software Engineering Laboratory (LES/PUC-Rio) for the student scholarship.

show abstract