Prototype Evidence for Estimation of Release Time for Open-Source Software Using Shannon Entropy Measure
Software systems are updated either to provide more comfort to the users or to fix bugs present in the current version. Open-source software undergoes regular changes due to high user-end demand and frequent changes in code by the developer. Software comp
- PDF / 128,066 Bytes
- 8 Pages / 439.37 x 666.142 pts Page_size
- 17 Downloads / 189 Views
Abstract Software systems are updated either to provide more comfort to the users or to fix bugs present in the current version. Open-source software undergoes regular changes due to high user-end demand and frequent changes in code by the developer. Software companies try to make the interface more comfortable and user friendly, which requires frequent changes and updation at a certain period of time and addition of new features from time to time as per customer’s demand. In this paper, we have considered the bugs recorded in various bugzilla software releases and calculated the Shannon entropy for the changes in various software updates. We have applied multiple linear regression models to predict the next release time of the software. Performance has been measured using goodness-of-fit curve, different residual statistics and R2 . Keywords Open-source software Software repositories
Shannon entropy
Next release time
1 Introduction Open-source software systems are becoming increasingly popular these days due to the advancement in Internet technologies and communication and thus are proven to be highly successful in various fields. With this growing demand for open-source software in today’s generation, changes in the software are inescapable. In order to
H.D. Arora (&) Ramita Sahni Talat Parveen Department of Applied Mathematics, Amity Institute of Applied Sciences, Amity University, Sector-125, Noida, Uttar Pradesh, India e-mail: [email protected] Ramita Sahni e-mail: [email protected] Talat Parveen e-mail: [email protected] © Springer Science+Business Media Singapore 2016 M. Pant et al. (eds.), Proceedings of Fifth International Conference on Soft Computing for Problem Solving, Advances in Intelligent Systems and Computing 437, DOI 10.1007/978-981-10-0451-3_61
683
684
H.D. Arora et al.
meet customer expectation, changes occur in the software frequently. Bug repair, feature enhancement and addition of new features are the three main types of code changes that occur in the software source code. These changes are being made continuously to remove the bugs, enhance the features and implement new features. Massive changes in the code make the software complex over a time period and results in introduction of bugs and at times cause failure of the software. It is of great significance to record these changes in a proper manner. For this purpose, we have source code repositories which record these changes properly. It also contains various details such as bugs present, record of every change occurred, creation data of a file and its initial content, communication between users and developers, etc. These storage locations, viz. repositories, offer a great opportunity to study the code change process. By code change process we mean to study the patterns of source code modifications. A complex code in the software system is undesirable as this complexity leads to many faults and ultimately faces many delays. Thus, it is a necessary task to manage and measure complexity of source code software.
Data Loading...
