From Android Bug Reports to Android Bug Handling Process: An Empirical Study of Open-Source Development

From Android Bug Reports to Android Bug Handling Process: An Empirical Study of Open-Source Development

Liguo Yu (Indiana University South Bend, Department of Computer Science, South Bend, IN, USA)
Copyright: © 2016 |Pages: 18
DOI: 10.4018/IJOSSP.2016100101
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

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.
Article Preview

Introduction

Bug reporting, bug tracking, and bug handling are important software management and maintenance activities in a software development process (Linstead & Baldi, 2009; Bettenburg et al., 2008). These activities are related to both quality assurance and project planning. Trackable bug reports not only contain the bug data, but also contain information about how the bug is handled. What’s more, these trackable bug reports might also contain other important information regarding software development process and software project management. Therefore, it is vital for closed-source software projects to document all the reported bugs and make them trackable in order to understand and improve software process. However, because of the closed-source property, software bug information of for-profit companies is only available for internal use. It is hard for an external researcher to access those useful data.

For open-source software products, the information and knowledge about software development and maintenance are usually not explicitly documented. Instead, software process and software project management information could be hidden in product artifacts, such as bug reports, change logs, release notes, and the supporting bug tracking systems (Wang et al., 2012; Schugerl et al., 2008). Accordingly, to retrieve that hidden knowledge, data mining techniques have been used to extract useful information from software repositories, such as bug reports. Statistical analysis is then performed to analyze the data. This area of research is called mining software bug reports. Significant amount of work has been reported in this area (Maalej & Nabil, 2015; Moran et al., 2016a; Moran et al., 2016b; Moran & Poshyvanyk, 2016; Chung et al. 2017; Hindle et al., 2016).

In spite of the intensive research carried out in the past years, bug reports are still considered valuable resource to mine various useful information. In this paper, bug reports are used to understand open-source software project management and development process. Because open-source software project is loosely managed, there are no formal documentations regarding requirement specification, design, implementation, testing, and maintenance. It is hard for researchers to obtain ready-to-use data and documents to study open-source development process. Here, ready-to-use data means well documented data for specific purposes. Therefore, bug reports became a common data source for researchers to study open-source development.

Bug reports and bug reporting systems are considered common tools for open-source projects, such as Linux, Firefox, and Eclipse. Regular users could file bug reports through the project’s bug tracking system. This is part of the common practice of user-involved open-source development. Because everyone can file a bug report to an open-source project, the data could be huge and might contain irrelevant information. Therefore, bug reports must be mined and data must be processed and analyzed in order to retrieve useful information.

In this paper, we use bug reports to study open-source software project management and development process. Through mining bug reports, we would like to answer the following questions, which we believe can help us better understand Android development and management process.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 8: 4 Issues (2017): 1 Released, 3 Forthcoming
Volume 7: 4 Issues (2016)
Volume 6: 1 Issue (2015)
Volume 5: 3 Issues (2014)
Volume 4: 4 Issues (2012)
Volume 3: 4 Issues (2011)
Volume 2: 4 Issues (2010)
Volume 1: 4 Issues (2009)
View Complete Journal Contents Listing