From android bug reports to android bug handling process: An empirical study of open-source development

被引：0
作者：
Yu L. [1 ]
机构：
[1] Indiana University South Bend, Department of Computer Science, South Bend, IN
来源：
Int. J. Open Source Softw. Processes | / 4卷 / 1-18期
关键词：
Android; Android Bug Report; Bug Handling Process; Bug Reports; Data Mining; Empirical Study; Mining Software Repository; Open-Source Project; Statistical Analysis;
D O I：
10.4018/IJOSSP.2016100101
中图分类号：
学科分类号：
摘要：
Android is an operating system for mobile devices. Its development is led by Google and some other companies. Because of the open-source property of Android, anyone can report a bug through its online bug tracking system. In this paper, we analyze the bug reports of Android operating systems. Specifically, through this study, we would like to answer the following questions regarding Android development and its project management: (1) Could Android bug reports be handled on time? (2) What is the distribution of different maintenance activities initiated by Android bug reports? (3) How long does it take to handle an Android bug report? (4) Are the number of followers and the number of following messages of an Android bug report related to the effort spent on handling this bug report? Through answering these questions, this paper presents a comprehensive study of Android bug reporting and handling process. The information and knowledge obtained through this case study could help us better understand open-source software project, such as its development process and project management. © 2016, IGI Global.
引用
收藏
页码：1 / 18
页数：17
相关论文
共 25 条
  • [1] Anvik J., Murphy G.C., Determining implementation expertise from bug reports, Proceedings of the 4th International Workshop on Mining Software Repositories, (2007)
  • [2] Anvik J., Murphy G.C., Reducing the effort of bug report triage: Recommenders for development-oriented decisions, ACM Transactions on Software Engineering and Methodology, 20, 3, (2011)
  • [3] Bettenburg N., Just S., Schroter A., Weiss C., Premraj R., Zimmermann T., What makes a good bug report?, Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering, pp. 308-318, (2008)
  • [4] Bettenburg N., Premraj R., Zimmermann T., Kim S., Extracting structural information from bug reports, Proceedings of the 2008 International Working Conference on Mining Software Repositories, pp. 27-30, (2008)
  • [5] Bhattacharya P., Neamtiu I., Bug-fix time prediction models: Can we do better?, Proceedings of the 8th Working Conference on Mining Software Repositories, pp. 207-210, (2011)
  • [6] Breu S., Premraj R., Sillito J., Zimmermann T., Information needs in bug reports: Improving cooperation between developers and users, Proceedings of the ACM Conference on Computer Supported Cooperative Work, pp. 301-310, (2010)
  • [7] Chen I.X., Jaygarl H., Yang C.Z., Wu P.J., Information retrieval on bug locations by learning co-located bug report clusters, Proceedings of the 31st Annual International ACM SIGIR Conference on Research and Development in Information Retrieval, pp. 801-802, (2008)
  • [8] Chung J., Jung H., Koo J., Kim Y., Kim U.M., A development of power consumption measurement system for Android smartphones, Proceedings of the 11th International Conference on Ubiquitous Information Management and Communication, (2017)
  • [9] Guo P.J., Zimmermann T., Nagappan N., Murphy B., Not my bug! and other reasons for software bug report reassignments, Proceedings of the ACM Conference on Computer Supported Cooperative Work, pp. 395-404, (2011)
  • [10] Hindle A., Alipour A., Stroulia E., A contextual approach towards more accurate duplicate bug report detection and ranking, Empirical Software Engineering, 21, 2, pp. 368-410, (2016)
123