2012
DOI: 10.1002/smr.1549
|View full text |Cite
|
Sign up to set email alerts
|

A suite of metrics for quantifying historical changes to predict future change‐prone classes in object‐oriented software

Abstract: Software systems are subject to series of changes during their evolution as they move from one release to the next. The change histories of software systems hold useful information that describes how artifacts evolved. Evolution-based metrics, which are the means to quantify the change history, are potentially good indicators of the changes in a software system. The objective of this paper is to derive and validate (theoretically and empirically) a set of evolution-based metrics as potential indicators of the … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

6
85
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 43 publications
(91 citation statements)
references
References 36 publications
6
85
0
Order By: Relevance
“…and DIT ( 3.5 for Findbugs, 2.4 for PMD and 2.3 for Checkstyle.). The results are similar to studies in related fields [11][12][13]. …”
Section: Descriptive Statisticssupporting
confidence: 91%
See 2 more Smart Citations
“…and DIT ( 3.5 for Findbugs, 2.4 for PMD and 2.3 for Checkstyle.). The results are similar to studies in related fields [11][12][13]. …”
Section: Descriptive Statisticssupporting
confidence: 91%
“…Recent studies have emphasized on change proneness as a relevant software quality attribute [12][13][14][15][16]. Han et al [12] evaluated the change using UML 2.0 models.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…More recently, Elish et al [17] started investigating the role of process metrics as predictors of change-prone classes. To this aim, they theoretically and empirically evaluated a new set of metrics (called "evolution metrics") that characterized the history of a class in order to delineate its future changeproneness.…”
Section: Introductionmentioning
confidence: 99%
“…[6], code smells [7], design patterns and [8] evolution metrics [9,10]. In terms of the techniques, different machine learning approaches have been used, such as Bayesian networks [11], neural networks [12], multivariate regression [1] and ensemble methods [5].…”
Section: Introductionmentioning
confidence: 99%