MINING EFFORT DATA FROM THE OSS REPOSITORY OF DEVELOPER’S BUG FIX ACTIVITY
DOI:
https://doi.org/10.33736/jita.38.2010Keywords:
Software repository, mining effort data, estimation models, developer expertise and open source software.Abstract
During the evolution of any software, efforts are made to fix bugs or to add new features in software. In software engineering, previous history of effort data is required to build an effort estimation model, which estimates the cost and complexity of any software. Therefore, the role of effort data is indispensable to build state-of-the-art effort estimation models. Most of the Open Source Software does not maintain any effort related information. Consequently there is no state-of-the-art effort estimation model for Open Source Software, whereas most of the existing effort models are for commercial software. In this paper we present an approach to build an effort estimation model for Open Source Software. For this purpose we suggest to mine effort data from the history of the developer’s bug fix activities. Our approach determines the actual time spend to fix a bug, and considers it as an estimated effort. Initially, we use the developer’s bug-fix-activity data to construct the developer’s activity log-book. The log-book is used to store the actual time elapsed to fix a bug. Subsequently, the log-book information is used to mine the bug fix effort data. Furthermore, the developer’s bug fix activity data is used to define three different measures for the developer’s contribution or expertise level. Finally, we used the bug-fix-activity data to visualize the developer’s collaborations and the involved source files. In order to perform an experiment we selected the Mozilla open source project and downloaded 93,607 bug reports from the Mozilla project bug tracking system i.e., Bugzilla. We also downloaded the available CVS-log data from the Mozilla project repository. In this study we reveal that in case of Mozilla only 4.9% developers have been involved in fixing 71.5% of the reported bugs.References
Ahsan,S.N., Ferzund, J., Wotawa, F. (2009). Program File Bug Fix Effort Estimation Using Machine Learning Methods for OSS, In proceddings of 21st Software Engineering and Knowledge Engineering (SEKE), pp.129-134, Boston, USA.
Albrecht, A.J., Gaffney, J.E., Jr. (1983). Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation, IEEE Transactions on Software Engineer, vol. SE-9, no.6, pp. 639-648, Nov. 1983
https://doi.org/10.1109/TSE.1983.235271
Alonso, O., Devanbu, P.T., Gertz M. (2008). Expertise identification and visualization from CVS. In Proceedings of the 2008 international Working Conference on Mining Software Repositories (Leipzig, Germany, May 10 - 11, 2008). MSR '08. ACM, New York, NY, 125-128. DOI= http://doi.acm.org/10.1145/1370750.1370780
https://doi.org/10.1145/1370750.1370780
Asundi. J. (2005). The need for effort estimation models for open source software projects. SIGSOFT Software Engineering Notes 30, 4 (Jul. 2005), 1-3. DOI= http://doi.acm.org/10.1145/1082983.1083260.
https://doi.org/10.1145/1083258.1083260
Ball, T., Kim, J.-M.., Porter, A. A. Siy, H. P(1997). If your version control system could talk ... In ICSE "97 Workshop on Process Modeling and Empirical Studies of Software Engineering, May 1997.
Boehm, B. Clark, B Horowitz, E., Westland, C., Madachy, R., Selby, R. (1995). Cost Models for Future Software Life Cycle Process: COCOMO 2, Annals of Software Engineering, 1995.
https://doi.org/10.1007/BF02249046
Boetticher, G. (2001). An Assessment of Metric Contribution in the Construction of a Neural Network-Based Effort Estimator, Second Int. Workshop on Soft Computing Applied to Software Engineering, 2001.
Fischer, M.. Pinzger, M., Gall. H. (2003). Analysing and relating bug report data for feature tracking. In Proceeding of 10th Working Conference on Reverse Engineering (WCRE 2003), Victoria British Columbia, Canada, 2003 IEEE
Gousios, G Kalliamvakou, E, and ,Spinellis, D.(2008). Measuring developer contribution from software repository data. In Proceedings of the 2008 international Working Conference on Mining Software Repositories (Leipzig, Germany, May 10 - 11, 2008). MSR '08. ACM, New York, NY, 129-132. DOI= http://doi.acm.org/10.1145/1370750.1370781.
https://doi.org/10.1145/1370750.1370781
Hahn, J., Moon, J.Y. and Zhang, C. (2006) Impact of Social Ties on Open Source Project Team Formation. In The Second International Conference on Open Source Systems - OSS 2006, (Como, Italy, 2006).
Herraiz, I., Daniel M. G., Jesus M. G., Gregorio R (2008) Towards a simplification of the bug report form in eclipse. Proceedings of the 2008 international working conference on Mining software repositories, 2008, Leipzig, Germany. http://doi.acm.org/10.1145/1370750.1370786.
https://doi.org/10.1145/1370750.1370786
Joseph, F., Brian, F. (2001). Understanding Open Source Software Development. Addison Wesley, Pearson Education Book, Dec 2001
Kawin N., Dongsong Z., A Gunes K., Lina Z., Rober N. (2008). An Exploratory Study on the Evolution of OSS Developer Communities. Proceedings of the 41st Hawaii International Conference on System Sciences 2008
Koch, S. (2008). Effort Modeling and Programmer Participation in Open Source Software. Projects, Information. Economics and Policy, 20(4): 345-355.
https://doi.org/10.1016/j.infoecopol.2008.06.004
Lanza, M., Ducasse. S. (2002). Understanding Software Evolution using a Combination of Software Visualization and Software Metrics. In Proceedings of LMO 2002.
https://doi.org/10.3166/objet.8.1-2.135-149
Panjer, L.D. (2007) Predicting Eclipse Bug Lifetimes, Mining Software Repositories, ICSE Workshops MSR apos;07. 20-26 May 2007 Page(s):29 - 29.
https://doi.org/10.1109/MSR.2007.25
Pressman. R.S. (2000) Software Engineering: A Practitioner's Approach. McGraw Hill Higher Education
th edition. December 1, 2000. ISBN-13 978-0071181822.
Raymond, E.S. (1999) The Cathedral & the Bazaar. O'Reilly Retrieved, 1999.
https://doi.org/10.1007/s12130-999-1026-0
Scacchi, W. (2005) Socio-Technical Interaction Networks in Free/Open Source Software Development Processes S.T. Acuña and N. Juristo (eds.), Software Process Modeling, pp. 1-27, Springer Science and Business Media Inc., New York, 2005.
https://doi.org/10.1007/0-387-24262-7_1
Schröter, A., Zimmermann, T., Premraj, R., Zeller, A (2006).. If your bug database could talk. In Proceedings of the 5th International Symposium on Empirical Software Engineering, Volume II: Short Papers and Posters. 2006.
Schuler, D. Zimmermann, T. (2008). Mining usage expertise from version archives. In Proceedings of the 2008 international Working Conference on Mining Software Repositories (Leipzig, Germany, May 10 - 11, 2008). MSR '08. ACM, New York, NY, 121-124. DOI= http://doi.acm.org/10.1145/1370750.1370779.
https://doi.org/10.1145/1370750.1370779
Weiss, C., Premraj, R., Zimmermann, T., and Zeller, A. (2007). How Long Will It Take to Fix This Bug?, In Proceedings of the Fourth international Workshop on MSR (20-26 May, 2007). International Conference on Software Engineering. IEEE Computer Society, Washington, DC, 1.
https://doi.org/10.1109/MSR.2007.13
Yu, L. (2006). Indirectly predicting the maintenance effort of open-source software. Research. Articles, Journal of Software Maintenance and Evolution, (5 Sep, 2006), pages: 311-332.
Downloads
Published
How to Cite
Issue
Section
License
Copyright Transfer Statement for Journal
1) In signing this statement, the author(s) grant UNIMAS Publisher an exclusive license to publish their original research papers. The author(s) also grant UNIMAS Publisher permission to reproduce, recreate, translate, extract or summarize, and to distribute and display in any forms, formats, and media. The author(s) can reuse their papers in their future printed work without first requiring permission from UNIMAS Publisher, provided that the author(s) acknowledge and reference publication in the Journal.
2) For open access articles, the author(s) agree that their articles published under UNIMAS Publisher are distributed under the terms of the CC-BY-NC-SA (Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License) which permits unrestricted use, distribution, and reproduction in any medium, for non-commercial purposes, provided the original work of the author(s) is properly cited.
3) For subscription articles, the author(s) agree that UNIMAS Publisher holds copyright, or an exclusive license to publish. Readers or users may view, download, print, and copy the content, for academic purposes, subject to the following conditions of use: (a) any reuse of materials is subject to permission from UNIMAS Publisher; (b) archived materials may only be used for academic research; (c) archived materials may not be used for commercial purposes, which include but not limited to monetary compensation by means of sale, resale, license, transfer of copyright, loan, etc.; and (d) archived materials may not be re-published in any part, either in print or online.
4) The author(s) is/are responsible to ensure his or her or their submitted work is original and does not infringe any existing copyright, trademark, patent, statutory right, or propriety right of others. Corresponding author(s) has (have) obtained permission from all co-authors prior to submission to the journal. Upon submission of the manuscript, the author(s) agree that no similar work has been or will be submitted or published elsewhere in any language. If submitted manuscript includes materials from others, the authors have obtained the permission from the copyright owners.
5) In signing this statement, the author(s) declare(s) that the researches in which they have conducted are in compliance with the current laws of the respective country and UNIMAS Journal Publication Ethics Policy. Any experimentation or research involving human or the use of animal samples must obtain approval from Human or Animal Ethics Committee in their respective institutions. The author(s) agree and understand that UNIMAS Publisher is not responsible for any compensational claims or failure caused by the author(s) in fulfilling the above-mentioned requirements. The author(s) must accept the responsibility for releasing their materials upon request by Chief Editor or UNIMAS Publisher.
6) The author(s) should have participated sufficiently in the work and ensured the appropriateness of the content of the article. The author(s) should also agree that he or she has no commercial attachments (e.g. patent or license arrangement, equity interest, consultancies, etc.) that might pose any conflict of interest with the submitted manuscript. The author(s) also agree to make any relevant materials and data available upon request by the editor or UNIMAS Publisher.
