Behind the Intents

Paixao, Matheus; Uchôa, Anderson; Bibiano, Ana Carla; Oliveira, Daniel; Garcia, Alessandro; Krinke, Jens; Arvonio, Emilio

doi:10.1145/3379597.3387475

Cited by 39 publications

(11 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Paixão et al [9] buscaram compreender o contexto e as motivações nos quais os desenvolvedores realizam rafatorações na revisão de código moderna. Para isso, um estudo experimental foi desenvolvido, onde mensagens de commit e discussões entre desenvolvedores foram inspecionadas.…”

Section: Palavras-chaveunclassified

Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar

Henrique¹,

Dósea²,

Sant’Anna³

2021

Anais Do IX Workshop De Visualização, Evolução E Manutenção De Software (VEM 2021)

View full text Add to dashboard Cite

As refatorações são operações realizadas no código fonte visando melhorar a capacidade de manutenção de um sistema de software. Apesar da literatura conter diversos estudos sobre as refatorações, são poucos os trabalhos que investigaram as motivações para tais refatorações ocorrerem. Esta pesquisa buscou investigar as motivações por trás das operações de extract method em um sistema real. Para isso, um estudo experimental foi conduzido, buscando minerar as refatorações do tipo extract method e analisar as mensagens de commit visando capturar as motivações por trás das refatorações. Também foi verificado a relação entre as refatorações e a métrica de número de linhas de código (LOC). Os resultados apontaram 11 motivações diferentes para a utilização do extract method. Além disso, foi visto que apenas 35% das refatorações que ocorreram foram com intenção de melhorar a qualidade do código. Também foi identificado que as refatorações com intenção de melhorar a qualidade do código ocorreram com maior frequência em métodos com valores de LOC na faixa de 21 a 40 e foram menos frequentes em métodos com valores entre 61 a 80.

show abstract

Section: Palavras-chaveunclassified

Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar

Henrique¹,

Dósea²,

Sant’Anna³

2021

Anais Do IX Workshop De Visualização, Evolução E Manutenção De Software (VEM 2021)

View full text Add to dashboard Cite

show abstract

“…The refactoring categories have been defined by reviewing the literature on refactoring motivation. 20,23,35,37,[42][43][44][45][46][47] To cover all of the existing motivations, the authors clustered the existing refactoring taxonomy reported in the literature into five categories. We then followed a multistaged approach to build our model for commit messages classification.…”

Section: Commit Classification Model Constructionmentioning

confidence: 99%

“…Recent studies have shown that the process of reviewing refactoring changes heavily relies on understanding the context of the performed refactoring. 45,47 Furthermore, the lack of refactoring documentation was one of the main challenges that impacted the efficiency of the review process. 47 This observation motivates us to explore documentation practice written by open-source developers and investigate the correlation between developer contributions and refactoring documentation.…”

Section: Rq4 Does Developer's Experience Influence the Quality Of Ref...mentioning

confidence: 99%

Behind the scenes: On the relationship between developer experience and refactoring

AlOmar

Peruma

Mkaouer

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

Refactoring is widely recognized as one of the efficient techniques to manage technical debt and maintain a healthy software project through enforcing best design practices, or coping with design defects. Previous refactoring surveys have shown that code refactoring activities are mainly executed by developers who have sufficient knowledge of the system's design, and disposing of leadership roles in their development teams. However, these surveys were mainly limited to specific projects and companies. In this paper, we explore the generalizability of the previous results by analyzing 800 open‐source projects. We mine their refactoring activities, and we identify their corresponding contributors. Then, we associate an experience score to each contributor in order to test various hypotheses related to whether developers with higher scores tend to (1) perform a higher number of refactoring operations, (2) exhibit different motivations behind their refactoring, and (3) better document their refactoring activity. We found that (1) although refactoring is not restricted to a subset of developers, those with higher contribution scores tend to perform more refactorings than others; (2) although there is no correlation between experience and motivation behind refactoring, top contributed developers are found to perform a wider variety of refactoring operations, regardless of their complexity; and (3) top contributed developer tend to document less their refactoring activity. Our qualitative analysis of three randomly sampled projects shows that the developers who are responsible for the majority of refactoring activities are typically in advanced positions in their development teams, demonstrating their extensive knowledge of the design of the systems they contribute to.

show abstract

“…If the developer recognizes that this renaming operation is a refactoring automated by their development environment, they can invoke the automated support to update the method name and all references (e.g., call sites) to the new name. Common refactorings like rename, extract, and move 8 occur both during software changes that are purely quality‐improving and—more commonly—during changes to software functionality 5,9,10 …”

Section: Introductionmentioning

confidence: 99%

“…33 Paixão et al also investigated why developers apply refactorings and mined code changes from open-source communities, finding that refactorings are mainly driven by the intent to introduce or enhance features. 9 Two other studies that summarize perspectives on refactoring from the industry are conducted by Sharma et al 14 and Leppänen et al 34 These studies investigated both kinds of refactoring and suggest factors that deter from tool use, such as lack of exposure to tool and differential code bases 14 and lack of trust in tools. 34 Despite trust being a recurring theme in these studies, it is not well understood what developers refer to when they complain of lack of trust, nor how to address it in tools.…”

mentioning

confidence: 99%

A study of refactorings during software change tasks

Eilertsen

Murphy

2021

J Software Evolu Process

View full text Add to dashboard Cite

Developers frequently undertake software change tasks that could be partially or fully automated by refactoring tools. As has been reported by others, all too often, these refactoring steps are instead performed manually by developers. These missed opportunities are referred to as occasions of disuse of refactoring tools. We perform an observational study in which 17 developers with professional experience attempt to solve three change tasks with steps amenable to the use of refactoring tools. We found that the strategies developers use to approach these tasks shape their workflow, which, in turn, shape the opportunities for refactoring tool use. We report on a number of findings about developer strategies, demonstrating the difficulty of aligning the kind of refactoring steps that emerge during a change task based on the strategy with the tools available. We also report on findings about refactoring tools, such as the difficulties developers face in controlling the scope of application of the tools. Our findings can help inform the designers of refactoring tools.

show abstract

Behind the Intents

Cited by 39 publications

References 24 publications

Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar

Minerando Motivações para Aplicação de Extract Method: Um Estudo Preliminar

Behind the scenes: On the relationship between developer experience and refactoring

A study of refactorings during software change tasks

Contact Info

Product

Resources

About