2015 IEEE International Conference on Software Maintenance and Evolution (ICSME) 2015
DOI: 10.1109/icsm.2015.7332494
|View full text |Cite
|
Sign up to set email alerts
|

Do automatic refactorings improve maintainability? An industrial case study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
5
4

Relationship

1
8

Authors

Journals

citations
Cited by 16 publications
(14 citation statements)
references
References 26 publications
0
14
0
Order By: Relevance
“…Interviews with the developers revealed that they found it to be easy to work with the tool in a lots of situations and they intend to keep using it in the future. An in-depth analysis of the results was discussed in a previous study [30] and a summary of our observations is available as an experience report [28].…”
Section: Discussionmentioning
confidence: 93%
See 1 more Smart Citation
“…Interviews with the developers revealed that they found it to be easy to work with the tool in a lots of situations and they intend to keep using it in the future. An in-depth analysis of the results was discussed in a previous study [30] and a summary of our observations is available as an experience report [28].…”
Section: Discussionmentioning
confidence: 93%
“…Generating only the required code parts created nearly the same code as the original, with most indentation and whitespaces in the right place. This was an important request from developers because interviews showed that they did not want to bother with fixing the indentation [30].…”
Section: Keeping Track Of Modificationsmentioning
confidence: 99%
“…On the other hand, if we just focus on maintainability, it has been positively linked to design patterns by Hegedűs et al [11], refactorings by Szőke et al [24], and version history metrics by Faragó et al [6].…”
Section: Related Workmentioning
confidence: 99%
“…We found that the effect of a single transformation usually has an unbalanced positive/negative effect on one or more quality attributes, but when developers applied them en masse, it always had a beneficial effect on the maintainability of the code. Later, in the automatic refactoring phase, we found that developers tend to have a different behavior when they use automatic tools (e.g., they accept a solution recommended by the tool even if manually they would probably do something else), so we examined the automatic transformations as well [14]. In a recent tool demo paper [15], we described the architecture of the tools developed in the project.…”
Section: Introductionmentioning
confidence: 99%