Bug introducing changes: A case study with Android
| dc.contributor.author | Asaduzzaman, M. | |
| dc.contributor.author | Bullock, M.C. | |
| dc.contributor.author | Roy, C.K. | |
| dc.contributor.author | Schneider, K.A. | |
| dc.date.accessioned | 2015-07-29T19:21:45Z | |
| dc.date.available | 2015-07-29T19:21:45Z | |
| dc.date.issued | 2012 | |
| dc.description.abstract | Changes, a rather inevitable part of software development can cause maintenance implications if they introduce bugs into the system. By isolating and characterizing these bug introducing changes it is possible to uncover potential risky source code entities or issues that produce bugs. In this paper, we mine the bug introducing changes in the Android platform by mapping bug reports to the changes that introduced the bugs. We then use the change information to look for both potential problematic parts and dynamics in development that can cause maintenance implications. We believe that the results of our study can help better manage Android software development. | en_US |
| dc.description.refereed | Yes | en_US |
| dc.identifier.doi | 10.1109/MSR.2012.6224267 | |
| dc.identifier.uri | http://hdl.handle.net/1880/50697 | |
| dc.publisher | IEEE | en_US |
| dc.publisher.url | http://dx.doi.org/10.1109/MSR.2012.6224267 | en_US |
| dc.title | Bug introducing changes: A case study with Android | en_US |
| dc.type | unknown |
Files
License bundle
1 - 1 of 1
No Thumbnail Available
- Name:
- license.txt
- Size:
- 1.84 KB
- Format:
- Item-specific license agreed upon to submission
- Description: