Peixin Yang
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Peixin Yang has a total of 11 co-authors. Here are the top co-authors by number of shared publications:
Chuanxiang Ma
School of Computer Science and Information Engineering Hubei University Wuhan China
1 shared publication- Jacky Keung
City University of Hong Kong, Hong Kong, Hong Kong
1 shared publication - Jianwen Xiang
Wuhan University of Technology, Wuhan, China
1 shared publication Lin Zhu
School of Computer Wuhan Qingchuan University Wuhan China
1 shared publication- Lin Zhu
Wuhan Qingchuan University, China
1 shared publication - Liping Lu
School of Computer Science and Artificial Intelligence, Wuhan University of Technology, Wuhan, China
1 shared publication
Latest Publications
- 10 July 2024
- Published by Wiley in Software: Practice and Experience
- Vol. 55 (1) , 49-78
Bug numbers matter: An empirical study of effort‐aware defect prediction using class labels versus bug numbers
Previous research have utilized public software defect datasets such as NASA, RELINK, and SOFTLAB, which only contain class label information. Most effort‐aware defect prediction (EADP) studies are carried out around these datasets. However, EADP studies typically relying on predicted bug number (i.e., considering modules as effort) or density (i.e., considering lines of code as effort) for ranking software modules. To explore the impact of bug number information in constructing EADP models, we access the performance degradation of the best‐performing learning‐to‐rank methods when using class labels instead of bug numbers for training. The experimental results show that using class labels instead of bug numbers in building EADP models results in an decrease in the detected bugs when module is considering as effort. When effort is LOC, using class labels to construct EADP models can lead to a significant increase in the initial false alarms and a significant increase in the modules that need to be inspected. Therefore, we recommend not only the class labels but also the bug number information should be disclosed when publishing software defect datasets, in order to construct more accurate EADP models.
- 10 July 2024
- Published by Wiley in Software: Practice and Experience
- Vol. 55 (1) , 49-78
Bug numbers matter: An empirical study of effort‐aware defect prediction using class labels versus bug numbers
Previous research have utilized public software defect datasets such as NASA, RELINK, and SOFTLAB, which only contain class label information. Most effort‐aware defect prediction (EADP) studies are carried out around these datasets. However, EADP studies typically relying on predicted bug number (i.e., considering modules as effort) or density (i.e., considering lines of code as effort) for ranking software modules. To explore the impact of bug number information in constructing EADP models, we access the performance degradation of the best‐performing learning‐to‐rank methods when using class labels instead of bug numbers for training. The experimental results show that using class labels instead of bug numbers in building EADP models results in an decrease in the detected bugs when module is considering as effort. When effort is LOC, using class labels to construct EADP models can lead to a significant increase in the initial false alarms and a significant increase in the modules that need to be inspected. Therefore, we recommend not only the class labels but also the bug number information should be disclosed when publishing software defect datasets, in order to construct more accurate EADP models.
- Open Access
- 4 August 2023
- Published by Association for Computing Machinery (ACM)
- p. 67-78
The Impact of the bug number on Effort-Aware Defect Prediction: An Empirical Study
Previous research have utilized public software defect datasets such as NASA, RELINK, and SOFTLAB, which only contain class label information. Almost all Effort-Aware Defect Prediction (EADP) studies are carried out around these datasets. However, EADP studies typically relying on bug density (i.e., the ratio between bug numbers and the lines of code) for ranking software modules. In order to investigate the impact of neglecting bug number information in software defect datasets on the performance of EADP models, we examine the performance degradation of the best-performing learning to rank methods when class labels are utilized instead of bug numbers. The experimental results show that neglecting bug number information in building EADP models results in an increase in the detected bugs. However, it also leads to a significant increase in the initial false alarms, ranging from 45.5% to 90.9% of the datasets, and an significant increase in the modules that need to be inspected, ranging from 5.2% to 70.4%. Therefore, we recommend not only the class labels but also the bug number information should be disclosed when publishing software defect datasets, in order to construct more accurate EADP models.
- 4 August 2023
- Published by Association for Computing Machinery (ACM)
- p. 67-78
Open AccessThe Impact of the bug number on Effort-Aware Defect Prediction: An Empirical Study
Previous research have utilized public software defect datasets such as NASA, RELINK, and SOFTLAB, which only contain class label information. Almost all Effort-Aware Defect Prediction (EADP) studies are carried out around these datasets. However, EADP studies typically relying on bug density (i.e., the ratio between bug numbers and the lines of code) for ranking software modules. In order to investigate the impact of neglecting bug number information in software defect datasets on the performance of EADP models, we examine the performance degradation of the best-performing learning to rank methods when class labels are utilized instead of bug numbers. The experimental results show that neglecting bug number information in building EADP models results in an increase in the detected bugs. However, it also leads to a significant increase in the initial false alarms, ranging from 45.5% to 90.9% of the datasets, and an significant increase in the modules that need to be inspected, ranging from 5.2% to 70.4%. Therefore, we recommend not only the class labels but also the bug number information should be disclosed when publishing software defect datasets, in order to construct more accurate EADP models.