Abstract
Open source software (OSS) programs are adopted as embedded systems regarding their server usage, due to their quick delivery, cost reduction, and standardization of systems. Many OSS programs are developed using the peculiar style known as the bazaar method, in which faults are detected and fixed by developers around the world, and the result is then reflected in the next release. Furthermore, the fix time of faults tends to be shorter as the development of the OSS progresses. However, several large-scale open source projects encounter the problem that fault fixing takes much time because the fault corrector cannot handle many fault reports. Therefore, OSS users and project managers need to know the stability degree of open source projects by determining the fault fix time. In this paper, we predict the transition of the fix time in large-scale open source projects. To make the prediction, we use the software reliability growth model based on the Wiener process considering that the fault fix time in open source projects changes depending on various factors such as the fault reporting time and the assignees to fix the faults. In addition, we discuss the assumption that fault fix time data depend on the prediction of the transition in fault fixing time.
Highlights
The source code of open source software (OSS) is freely available for use, reuse, fixing, and re-distribution by the users
The prediction of development effort and fixing time for individual faults can be assessed by using conventional OSS reliability evaluation methods
There is no research in terms of the transition of the fault fixing time for a long time, i.e., there is no research for predicting the fault fixing time
Summary
The source code of open source software (OSS) is freely available for use, reuse, fixing, and re-distribution by the users. Many IT companies often develop OSS for commercial use. OSS programs are developed using the bazaar method [1], in which the source code is disseminated to the public through the Internet. OSS programs are promoted by an unspecified number of users and developers. The bug-tracking system is one of the systems used to develop OSS. Much fault information such as fix status, the details, and fix priorities are registered through the bug-tracking system. OSS programs have been actively developed and used in recent years, there are problems with promoting open source projects. It becomes difficult to fix the faults quickly [3,4]
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have