.png){kind=icon}
.png){kind=icon}
Return
Cross-version defect prediction: use historical data, cross-project data, or both?
.png){kind=icon}
PRE
AI
DOI：10.1007/s10664-019-09777-8.png)
.png){kind=icon}
Original request for help.png){kind=icon}
Share.png){kind=icon}
Save
Abstract
En 中文
Context Although a long-running project has experienced many releases, removing defects from a product is still a challenge. Cross-version defect prediction (CVDP) regards project data of prior releases as a useful source for predicting fault-prone modules based on defect prediction techniques. Recent studies have explored cross-project defect prediction (CPDP) that uses the project data from outside a project for defect prediction. While CPDP techniques and CPDP data can be diverted to CVDP, its effectiveness has not been investigated. Objective To investigate whether CPDP approaches and CPDP data are useful for CVDP. The investigation also compared the usage of prior release data. Method We chose a style of replication of a previous comparative study on CPDP approaches. Results Some CPDP approaches could improve the performance of CVDP. The use of the latest prior release was the best choice. If one has no CVDP data, the use of CPDP data for CVDP was found to be effective. Conclusions 1) Some CPDP approaches could improve CVDP, 2), if one can access project data from the latest release, project data from older releases would not bring clear benefit, and 3) even if one has no CVDP data, appropriate CPDP approaches would be able to deliver quality prediction with CPDP data.
Keywords:
Cross-version defect prediction
Cross-project defect prediction
Comparative study
AI Summary
Key information extracted from the uploaded paper, including a brief overview, abstract, background, key highlights, visual analysis, and future outlook.
Journal
IF:
3.6
Papers:
2.0K
Citations:
5.3K
