Constructing models for predicting extract subclass refactoring opportunities using object-oriented quality metrics

Dallal, Jehad Al

doi:10.1016/j.infsof.2012.04.004

Cited by 45 publications

(26 citation statements)

References 58 publications

(103 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Moreover, there are several approaches or techniques that have been proposed and utilized in the identification of refactoring opportunities [17][18] [25]. These approaches are either completely automated or semi-auto mated [12][17] [18]. Nonetheless, the goals are centered on reducing the high cost of maintenance due to increased complexity in order to increase source code comprehensibility, maintainability and extensibility [8] [14].…”

Section: Object -Oriented Refactoring Oportunities Identificationmentioning

confidence: 99%

“…Nonetheless, the goals are centered on reducing the high cost of maintenance due to increased complexity in order to increase source code comprehensibility, maintainability and extensibility [8] [14]. Furthermore, identifying the refactorings opportunities in OO code manually has been deemed challenging, costly and timewasting task [17] [18]. The existing approaches can be applied to OO code written in diverse languages and are grouped into six categories such as quality metricoriented, precondition-oriented, cluster-oriented, graphoriented, code slicing-oriented and dynamic analysisoriented approaches [17].…”

Section: Object -Oriented Refactoring Oportunities Identificationmentioning

confidence: 99%

“…Based on the 16 studies considered in this paper, the approaches that utilized software metrics employed the use of either structural, semantic or structural and semantic information to identify the bad smells in OO code in order to apply the appropriate refactorings to fix them [10][12] [18]. Each approach has its unique operations in identify ing the opportunities for either a single or mult iple refactorings.…”

Section: A Rq1: How Are the Opportunities For Refactorings Identifiementioning

confidence: 99%

“…"Constructing models for predicting extrac t subclass refactoring opportunities using objectoriented quality metrics": Al Dalal [18] built a model to predict opportunities for refactorings using empirically validated quality metrics and logistic regression (LR) as statistical technique. The study first exp lored emp irically, the capabilit ies of some existing met rics: 25 size, cohesion, and coupling to predict refactoring opportunities individually in a g iven class using the univariate LR.…”

Section: A Rq1: How Are the Opportunities For Refactorings Identifiementioning

confidence: 99%

“…To perform refactoring in software code, the first task is to pinpoint the refactoring candidates that manifest in the form of bad smells before applying the appropriate refactoring to remove them. Today, there exist several approaches to identify refactoring opportunities in OO software systems and the application of appropriate refactorings have been proposed, developed and utilized during software development [10] [12][17] [18][19] [20]. However, these approaches are designed to identify opportunity for a particular refactoring candidate or couple of them which is ach ieved by either full automation or semi automat ion.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Analysis of Metric-Based Object-Oriented Code Refactoring Opportunities Identification Approaches

Isong¹,

Dladlu²,

Duke³

et al. 2017

IJITCS

View full text Add to dashboard Cite

Abstract-Refactoring is used to improve deteriorated software design, code and their maintainability. In objectoriented (OO) code, before refactoring is performed, its opportunities must be identified and s everal approaches exist this regard. Among the approaches is the software metric-based approach where quality software met rics are used. Therefore, this paper provide analysis of existing emp irical studies that utilized software metrics to identify refactoring opportunities in OO software systems. We performed a co mprehensive analysis on 16 studies to identify the state-of-the-practice. The focal point was on the workings, refactoring activ ities, the programming language and the impact on software quality. The results obtained shows approaches were not unique, each was designed either for a single refactoring activ ity or couple of them, move method and extract class dominated th e refactorings activities, and most approaches were fu lly automated while few were semi-auto mated. Moreover, OO met rics p layed acritical role in both opportunities detection and factoring decisions. Based on the results, it would be beneficial if generic refactoring approach is developed that is capable of identifying needs for all refactoring activities.

show abstract

Section: Object -Oriented Refactoring Oportunities Identificationmentioning

confidence: 99%

Section: Object -Oriented Refactoring Oportunities Identificationmentioning

confidence: 99%

Section: A Rq1: How Are the Opportunities For Refactorings Identifiementioning

confidence: 99%

Section: A Rq1: How Are the Opportunities For Refactorings Identifiementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Analysis of Metric-Based Object-Oriented Code Refactoring Opportunities Identification Approaches

Isong¹,

Dladlu²,

Duke³

et al. 2017

IJITCS

View full text Add to dashboard Cite

show abstract

Accounting for data encapsulation in the measurement of object-oriented class cohesion

Dallal

2015

J. Softw. Evol. and Proc.

Self Cite

View full text Add to dashboard Cite

Intuitively, in a certain class, a pair of methods that share an attribute of an object type is potentially more cohesive than those that share an attribute of a primitive type because the attribute of a reference type could implicitly refer to multiple data. Existing class cohesion measures ignore the implicit access to or sharing of attributes due to the encapsulation feature. As a result, the obtained cohesion values can be inaccurate and could lead to incorrect quality indications. This paper aims at demonstrating how to account for data encapsulation (DE) in cohesion measurement and reports empirical studies that investigate the impact of considering DE in cohesion measurement on cohesion values and the abilities of cohesion measures to predict class fault proneness. To differentiate between attributes and parameters of different types, we propose a weight assignment algorithm. The weight that is assigned to an attribute or a parameter of a type depends on the number of encapsulated attributes of the type. Seven cohesion measures are extended to consider the assigned weights in cohesion measurement. The results of the empirical study show that the cohesion values and the corresponding fault‐proneness prediction results can significantly change when accounting for DE in cohesion measurement. Copyright © 2015 John Wiley & Sons, Ltd.

show abstract

Generation of refactoring algorithms by grammatical evolution

2022

View full text Add to dashboard Cite

Constructing models for predicting extract subclass refactoring opportunities using object-oriented quality metrics

Cited by 45 publications

References 58 publications

Analysis of Metric-Based Object-Oriented Code Refactoring Opportunities Identification Approaches

Analysis of Metric-Based Object-Oriented Code Refactoring Opportunities Identification Approaches

Accounting for data encapsulation in the measurement of object-oriented class cohesion

Generation of refactoring algorithms by grammatical evolution

Contact Info

Product

Resources

About