2015
DOI: 10.18293/seke2015-099
|View full text |Cite
|
Sign up to set email alerts
|

A Software Defect-Proneness Prediction Framework: A new approach using genetic algorithms to generate learning schemes

Abstract: Recently, defect prediction software is an important research topic in the software engineering field. The demand for development of good quality software has seen a rapid growth in the last few years. The software measurement data collected during the software development process include valuable information about software projects status, progress, quality, performance, and evolution. The software fault prediction in the early phases of software development can help and guide software practitioners to focus … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 10 publications
(2 citation statements)
references
References 15 publications
0
2
0
Order By: Relevance
“…This set is composed of ten factors measuring the size and complexity of production and/or test code. Some of these metrics belong to the Object-Oriented metric suite proposed by Chidamber and Kemerer (Chidamber and Kemerer 1994), e.g., coupling between object classes (CBO), while other metrics come from other catalogs, e.g., the McCabe cyclomatic complexity (McCabe 1976) or the Halstead's metrics (Murillo-Morera and Jenkins 2015). The rationale behind the selection of these metrics was driven by our willingness to verify whether large and/or complex code might have an impact on the likelihood of observing a flaky behavior of the test case.…”
Section: Production and Test Code Metricsmentioning
confidence: 99%
“…This set is composed of ten factors measuring the size and complexity of production and/or test code. Some of these metrics belong to the Object-Oriented metric suite proposed by Chidamber and Kemerer (Chidamber and Kemerer 1994), e.g., coupling between object classes (CBO), while other metrics come from other catalogs, e.g., the McCabe cyclomatic complexity (McCabe 1976) or the Halstead's metrics (Murillo-Morera and Jenkins 2015). The rationale behind the selection of these metrics was driven by our willingness to verify whether large and/or complex code might have an impact on the likelihood of observing a flaky behavior of the test case.…”
Section: Production and Test Code Metricsmentioning
confidence: 99%
“…The main goal in generating these predictions is to enable software engineers to focus development and testing activities on the most fault-prone parts of their code, thereby improving software quality and making a better use of limited time and resources [16] and [1]. The study and construction of these techniques have been the emphasis of the fault prediction modeling research area and also the subject of many previous research projects [12], [22], [23], [33] and [37].…”
Section: Introductionmentioning
confidence: 99%