activity
20192025
most citedHow Do I Refactor This? An Empirical Study on Refactoring Trends and Topics in Stack Overflow

69 citations · 132 across the 16 of their papers we have counts for

collaborators
Showing 2021Show all

7 papers · 1 filter

cs.SE202169 cited

How Do I Refactor This? An Empirical Study on Refactoring Trends and Topics in Stack Overflow

Anthony Peruma, Steven Simmons, Eman Abdullah AlOmar +3

An essential part of software maintenance and evolution, refactoring is performed by developers, regardless of technology or domain, to improve the internal quality of the system,…

cs.SE2021

Behind the Scenes: On the Relationship Between Developer Experience and Refactoring

Eman Abdullah AlOmar, Anthony Peruma, Mohamed Wiem Mkaouer +2

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 copi…

cs.SE2021

On Preserving the Behavior in Software Refactoring: A Systematic Mapping Study

Eman Abdullah AlOmar, Mohamed Wiem Mkaouer, Christian Newman +1

Context: Refactoring is the art of modifying the design of a system without altering its behavior. The idea is to reorganize variables, classes and methods to facilitate their futu…

cs.SE2021

One Thousand and One Stories: A Large-Scale Survey of Software Refactoring

Yaroslav Golubev, Zarina Kurbatova, Eman Abdullah AlOmar +2

Despite the availability of refactoring as a feature in popular IDEs, recent studies revealed that developers are reluctant to use them, and still prefer the manual refactoring of…

cs.SE2021

SATDBailiff- Mining and Tracking Self-Admitted Technical Debt

Eman Abdullah AlOmar, Ben Christians, Mihal Busho +4

Self-Admitted Technical Debt (SATD) is a metaphorical concept to describe the self-documented addition of technical debt to a software project in the form of source code comments.…

cs.SE2021

Using Grammar Patterns to Interpret Test Method Name Evolution

Anthony Peruma, Emily Hu, Jiajun Chen +3

It is good practice to name test methods such that they are comprehensible to developers; they must be written in such a way that their purpose and functionality are clear to those…