Entropy Based Software Reliability Analysis of Multi-Version Open Source Software

The number of issues fixed in the current release of the software is one of the factors which decides the next release of the software. The source code files get changed during fixing of these issues. The uncertainty arises due to these changes is quantified using entropy based measures. We develope...

Full description

Saved in:
Bibliographic Details
Published inIEEE transactions on software engineering Vol. 44; no. 12; pp. 1207 - 1223
Main Authors Singh, V.B., Sharma, Meera, Pham, Hoang
Format Journal Article
LanguageEnglish
Published New York IEEE 01.12.2018
IEEE Computer Society
Subjects
cobb-douglas
Computer bugs
Entropy
feature improvement
Fixing
Freeware
Growth models
new feature
Open source software
Optimization
Poisson density functions
Public domain
release time problem
Reliability analysis
Software product lines
Software reliability
software repositories
Source code
Online AccessGet full text

Cover

More Information
Summary:The number of issues fixed in the current release of the software is one of the factors which decides the next release of the software. The source code files get changed during fixing of these issues. The uncertainty arises due to these changes is quantified using entropy based measures. We developed a Non-Homogeneous Poisson Process model for Open Source Software to understand the fixing of issues across releases. Based on this model, optimal release-updating using entropy and maximizing the active user's satisfaction level subject to fixing of issues up to a desired level, is investigated as well. The proposed models have been validated on five products of the Apache open source project. The optimal release time estimated from the proposed model is close to the observed release time at different active user's satisfaction levels. The proposed decision model can assist management to appropriately determine the optimal release-update time. The proposed entropy based model for issues estimation shows improvement in performance for 21 releases out of total 23 releases, when compared with well-known traditional software reliability growth models, namely GO model <xref ref-type="bibr" rid="ref1">[1] and S-shaped model <xref ref-type="bibr" rid="ref2">[2] . The proposed model is also found statistically significant.
Bibliography:ObjectType-Article-1
SourceType-Scholarly Journals-1
ObjectType-Feature-2
content type line 14
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.2017.2766070