Bug introducing changes: A case study with Android

Simple item page
dc.contributor.authorAsaduzzaman, M.
dc.contributor.authorBullock, M.C.
dc.contributor.authorRoy, C.K.
dc.contributor.authorSchneider, K.A.
dc.date.accessioned2015-07-29T19:21:45Z
dc.date.available2015-07-29T19:21:45Z
dc.date.issued2012
dc.description.abstractChanges, 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.refereedYesen_US
dc.identifier.doi10.1109/MSR.2012.6224267
dc.identifier.urihttp://hdl.handle.net/1880/50697
dc.identifier.urihttps://doi.org/10.11575/PRISM/46165
dc.publisherIEEEen_US
dc.publisher.urlhttp://dx.doi.org/10.1109/MSR.2012.6224267en_US
dc.titleBug introducing changes: A case study with Androiden_US
dc.typeunknown
Files
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.84 KB
Format:
Item-specific license agreed upon to submission
Description:
Download
Collections
Surfnet