• Journal of KIISE
• /
• v.42 no.6
• /
• pp.755-763
• /
• 2015

As fixing bugs is a large part of software development and maintenance, estimating the time to fix bugs -bug fixing time- is extremely useful when planning software projects. Therefore, in this study, we propose a way to estimate bug fixing time using bug reports. First, we classify previous bug reports with meta fields by applying a k-NN method. Next, we compute the similarity of the new bug and previous bugs by using data from bug reports. Finally, we estimate how long it will take to fix the new bug using the time it took to repair similar bugs. In this study, we perform experiments with open source software. The results of these experiments show that our approach effectively estimates the bug fixing time.

• Journal of the Institute of Electronics and Information Engineers
• /
• v.52 no.5
• /
• pp.235-241
• /
• 2015

Nowadays, research and industry on the internet of things is rapidly developing. Bug fixed field of the Software development related internet of things is a very important things. In this study, we analyze the properties that can affect what the bug fix-time by analyzing the time required to fix a bug associated with the Internet of Things. Using the k-NN classification method based on the attribute information to be classified as bug reports. Extracts a bug report based on the results of a similar property. Bug fixed by calculating the time of a similar bug report predicts the fix-time for new bugs. Depending on the prediction of the properties that affect the bug correction time, the properties of os, component, reporter, and assignee showed the best prediction accuracy.

• KIISE Transactions on Computing Practices
• /
• v.21 no.9
• /
• pp.616-621
• /
• 2015

Recently developed software systems have many components, and their complexity is thus increasing. Last year, about 375 bug reports in one day were reported to a software repository in Eclipse and Mozilla open source projects. With so many bug reports submitted, developers' time and efforts have increased unnecessarily. Since the bug severity is manually determined by quality assurance, project manager or other developers in the general bug fixing process, it is biased to them. They might also make a mistake on the manual decision because of the large number of bug reports. Therefore, in this study, we propose an approach of bug severity prediction to solve these problems. First, we find similar topics within a new bug report and reduce the candidate reports of the topic by using the meta field of the bug report. Next, we train the reduced reports by applying Naive Bayes Multinomial. Finally, we predict the severity of the new bug report. We compare our approach with other prediction algorithms by using bug reports in open source projects. The results show that our approach better predicts bug severity than other algorithms.

• Journal of Internet Computing and Services
• /
• v.20 no.2
• /
• pp.29-37
• /
• 2019

As software development technology evolves, the quality of software has increased. But software created through sophisticated technology is still defective. The developer will be aware of the defect through a bug report and the reported defect must be fixed as soon as possible for the software to function correctly. It is important to know which component of the program is related to the reported defect and should be fixed. However, even though the developer understands the developed software, the task of tracing faults is a time-consuming task and requires effort. Therefore, if there is a way for developers to support tracing faults, they could fix defects more quickly. Because fixing defects rapidly is a factor of software reliability, fault traceability is essential and an effective method is needed. Therefore, in this paper, we propose a model-based fault traceability enhancement technique by using bug report and commit information and verify the effectiveness of the proposed technique.