Automatic code locations identification for replacing temporary variable with query method

Rongviriyapanish, Songsakdi; Karunlanchakorn, Nopphawit; Meananeatra, Panita

doi:10.1109/ecticon.2015.7207086

Cited by 1 publication

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We compare the impacted statements by replace temp with query refactoring technique identified by our LMR plugin and IntelliJ IDEA. As a result, our tool can identify codes to form a query method for replacing a temporary variable in a long method covering more cases and more correctly than IntelliJ IDEA [23]. Our tool can identify temp variable inside loop statement and selection statement while IntelliJ IDEA cannot.…”

Section: Toolsmentioning

confidence: 99%

See 1 more Smart Citation

Refactoring Opportunity Identification Methodology for Removing Long Method Smells and Improving Code Analyzability

Meananeatra

Rongviriyapanish

Apiwattanapong

2018

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

SUMMARYAn important step for improving software analyzability is applying refactorings during the maintenance phase to remove bad smells, especially the long method bad smell. Long method bad smell occurs most frequently and is a root cause of other bad smells. However, no research has proposed an approach to repeating refactoring identification, suggestion, and application until all long method bad smells have been removed completely without reducing software analyzability. This paper proposes an effective approach to identifying refactoring opportunities and suggesting an effective refactoring set for complete removal of long method bad smell without reducing code analyzability. This approach, called the long method remover or LMR, uses refactoring enabling conditions based on program analysis and code metrics to identify four refactoring techniques and uses a technique embedded in JDeodorant to identify extract method. For effective refactoring set suggestion, LMR uses two criteria: code analyzability level and the number of statements impacted by the refactorings. LMR also uses side effect analysis to ensure behavior preservation. To evaluate LMR, we apply it to the core package of a real world java application. Our evaluation criteria are 1) the preservation of code functionality, 2) the removal rate of long method characteristics, and 3) the improvement on analyzability. The result showed that the methods that apply suggested refactoring sets can completely remove long method bad smell, still have behavior preservation, and have not decreased analyzability. It is concluded that LMR meets the objectives in almost all classes. We also discussed the issues we found during evaluation as lesson learned. key words: code analyzability, long method bad smell, refactoring, software engineering, software maintenance

show abstract

Section: Toolsmentioning

confidence: 99%

“…Our plugin also identifies statements impacted by the replace temp with query refactoring by using the approach described in Ref. [20].…”

Section: Toolsmentioning

confidence: 99%

Refactoring Opportunity Identification Methodology for Removing Long Method Smells and Improving Code Analyzability

Meananeatra

Rongviriyapanish

Apiwattanapong

2018

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

show abstract

Automatic code locations identification for replacing temporary variable with query method

Cited by 1 publication

References 11 publications

Refactoring Opportunity Identification Methodology for Removing Long Method Smells and Improving Code Analyzability

Refactoring Opportunity Identification Methodology for Removing Long Method Smells and Improving Code Analyzability

Contact Info

Product

Resources

About