Monitor-Based Instant Software Refactoring

Liu, Hui; Guo, Xinhua; Shao, Wei

doi:10.1109/tse.2013.4

Cited by 44 publications

(40 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Compared to our prior work [11], the key difference which is also the unique advantage of the approach in Fig. 3 is requirements-driven.…”

Section: Enabling Software Refactoring Through Requirements Tracmentioning

confidence: 93%

“…Our essential argument is that the role of refactoring is better justified by leading more requirements to their full implementation. To examine this premise, we significantly extend monitor-based refactoring [11] by exploiting the novel use of requirements traceability information.…”

Section: Enabling Software Refactoring Through Requirements Tracmentioning

confidence: 99%

“…The framework deploys a monitoring mechanism to analyze code changes constantly (e.g., between saves), and then prompts the developer for potential refactorings. The direct effect is that more refactorings are made without much delay [11]. We thus believe this framework sets up a firm and promising basis for handling those just-in-time requirements that are slowly progressing or hard to accommodate.…”

Section: Introductionmentioning

confidence: 97%

“…In our earlier work, we devised an instant refactoring framework for actively assisting developers with better tactics [11]. The framework deploys a monitoring mechanism to analyze code changes constantly (e.g., between saves), and then prompts the developer for potential refactorings.…”

Section: Introductionmentioning

confidence: 99%

“…We thus believe this framework sets up a firm and promising basis for handling those just-in-time requirements that are slowly progressing or hard to accommodate. While our work so far has focused on the "when" and "how frequently" tactics [11,12], identifying "where" to apply "what" refactoring(s) remains one of the most pressing and vital issues confronting the research community [8].…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Traceability-enabled refactoring for managing just-in-time requirements

Niu

Bhowmik

Liu

et al. 2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

Self Cite

View full text Add to dashboard Cite

Abstract-Just-in-time requirements management, characterized by lightweight representation and continuous refinement of requirements, fits many iterative and incremental development projects. Being lightweight and flexible, however, can cause wasteful and procrastinated implementation, leaving certain stakeholder goals not satisfied. This paper proposes traceabilityenabled refactoring aimed at fulfilling more requirements fully. We make a novel use of requirements traceability to accurately locate where the software should be refactored, and develop a new scheme to precisely determine what refactorings should be applied to the identified places. Our approach is evaluated through an industrial study. The results show that our approach recommends refactorings more appropriately than a contemporary recommender.

show abstract

“…Compared to our prior work [11], the key difference which is also the unique advantage of the approach in Fig. 3 is requirements-driven.…”

Section: Enabling Software Refactoring Through Requirements Tracmentioning

confidence: 93%

Section: Enabling Software Refactoring Through Requirements Tracmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 97%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Traceability-enabled refactoring for managing just-in-time requirements

Niu

Bhowmik

Liu

et al. 2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

Self Cite

View full text Add to dashboard Cite

show abstract

A review of code smell mining techniques

Rasool

Arshad

2015

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

Over the past 15 years, researchers presented numerous techniques and tools for mining code smells. It is imperative to classify, compare, and evaluate existing techniques and tools used for the detection of code smells because of their varying features and outcomes. This paper presents an up-to-date review on the state-of-the-art techniques and tools used for mining code smells from the source code of different software applications. We classify selected code smell detection techniques and tools based on their detection methods and analyze the results of the selected techniques. We present our observations and recommendations after our critical analysis of existing code smell techniques and tools. Our recommendations may be used by existing and new tool developers working in the field of code smell detection. The scope of this review is limited to research publications in the area of code smells that focus on detection of code smells as compared with previous reviews that cover all aspects of code smells.

show abstract

Context‐based approach to prioritize code smells for prefactoring

Sae-Lim

Hayashi

Saeki

2017

J Software Evolu Process

View full text Add to dashboard Cite

Existing techniques for detecting code smells (indicators of source code problems) do not consider the current context, which renders them unsuitable for developers who have a specific context, such as modules within their focus. Consequently, the developers must spend time identifying relevant smells. We propose a technique to prioritize code smells using the developers' context. Explicit data of the context are obtained using a list of issues extracted from an issue tracking system. We applied impact analysis to the list of issues and used the results to specify the context-relevant smells. Results show that our approach can provide developers with a list of prioritized code smells related to their current context. We conducted several empirical studies to investigate the characteristics of our technique and factors that might affect the ranking quality.Additionally, we conducted a controlled experiment with professional developers to evaluate our technique. The results demonstrate the effectiveness of our technique. KEYWORDScode smell, impact analysis, issue tracking system, prefactoring INTRODUCTIONCode smell, as defined by Fowler, 1-3 is an indicator of design flaws or problems in the source code. Code smells of many types are summarized as smell catalogs. [1][2][3] Code elements that are affected by code smells are recommended for improved quality because they are likely to cause difficulties in the future, as discussed in the literature, eg, making the source code more difficult to understand and maintain or increasing code components' fault-proneness. Moreover, Yamashita et al 4 found that code smells can affect important maintainability aspects. Hermans and Aivaloglou 5 conducted a controlled experiment, which revealed that code smells influence the block-based programming performance of novice programmers.Developers can improve the code by removing the code smells from the elements.Many researchers have examined factors that can introduce code smells into the system. Tufano et al 6 conducted a large-scale empirical study, which revealed that the main activities that tend to introduce code smells are implementing features and enhancing existing ones. Moreover, they found that developers with high workloads and pressure are more likely to introduce a smelly code to the system. Vale et al 7 investigated the factors that can influence code smells based on a software developer's perspective. That investigation revealed that factors such as time pressure, bad design decisions, lack of business knowledge, inexperienced developers, little time for refactoring, and low priority assigned to software quality influence the severity of smelly codes.For issue-driven software development projects, development teams tend to adopt an issue tracking system such as Jira or Bugzilla to manage their lists of issues, so-called backlogs. Such issues can be anything related to software change requests, eg, bug fixing or feature implementation.Developers apply refactoring techniques to source codes before implementing changes ...

show abstract

Monitor-Based Instant Software Refactoring

Cited by 44 publications

References 39 publications

Traceability-enabled refactoring for managing just-in-time requirements

Traceability-enabled refactoring for managing just-in-time requirements

A review of code smell mining techniques

Context‐based approach to prioritize code smells for prefactoring

Contact Info

Product

Resources

About