Generalized Multi-Release Framework for Fault Prediction in Open Source Software

Generalized Multi-Release Framework for Fault Prediction in Open Source Software

Shozab Khurshid (University of Kashmir, Srinagar, India), A.K. Shrivastava (International Management Institute, Kolkata, West Bengal, India), and Javaid Iqbal (University of Kashmir, Srinagar, India)
Copyright: © 2019 |Pages: 22
DOI: 10.4018/IJSI.2019100105
OnDemand PDF Download:
No Current Special Offers


Software developing communities are shifting to open source software (OSS) because of the reason that software development takes place in successive releases, thereby improving its quality and reliability. Multi-release development of OSS can provide an opportunity to inculcate the dynamic needs of the user in a very short span of time to survive in the market. In spite of having these benefits, numerous challenges can be faced during the multi-release OSS development. Some of the challenges can be the generation of errors during the addition of new features. To address the changing fault detection process, a change point phenomenon is considered so as to give more practicality to the model. In this article, we present a general framework for multi-release OSS modelling incorporating imperfect debugging and change points. Parameter estimation and model validation is done on the three releases of Apache, an open source software project.
Article Preview

Literature Review

In the field of information technology, reliable software has become the most important concern. Software reliability is defined as “the probability of error free operation of the software for a given time period within some specified environment” (Kapur et al., 2011; Pham, 2006). Software Reliability Growth Models are used to quantitatively estimate the reliability of the software during the testing phase. A mathematical relationship between the testing time and total number of faults is given by SRGMs. Although a number of reliability models have been proposed so far, but all these are based on some limitations (Musa, 2004; Kapur et al., 2011).

Tremendous work has been done to assess the reliability and also to find a suitable model for Open Source Software. The phases that are involved in the development process of OSS was given by (Jorgensen, 2001). A comparative study between open and closed software was done by (Ven et al., 2008). In their study, comparison between the two was carried with respect to the development, cost, number of users and software design. Due to the limitations in the time and the resources, it becomes impossible for the developers to deliver a software product meeting the desired level of reliability within a single Software Development Life Cycle. Successive release is planned by the software developers which provides a number of benefits over a single release policy. The benefits that are provided by successive release policy has been studied by (Garmabaki et al., 2012). Kapur et al. (2014) proposed a multi up-gradation model for closed software that considers the issues related to the generation of faults when new functionality is added in the software. The SRGM proposed by them has the capability to capture the faults that are generated due to the add-ons along with the faults from the previous release that have been left undetected.

Complete Article List

Search this Journal:
Volume 11: 1 Issue (2023)
Volume 10: 4 Issues (2022): 2 Released, 2 Forthcoming
Volume 9: 4 Issues (2021)
Volume 8: 4 Issues (2020)
Volume 7: 4 Issues (2019)
Volume 6: 4 Issues (2018)
Volume 5: 4 Issues (2017)
Volume 4: 4 Issues (2016)
Volume 3: 4 Issues (2015)
Volume 2: 4 Issues (2014)
Volume 1: 4 Issues (2013)
View Complete Journal Contents Listing