Surfnet

Permanent URI for this collection

https://prism.ucalgary.ca/handle/1880/100111

Browse

Browsing Surfnet by Author "Asaduzzaman, M."

Now showing 1 - 2 of 2
  • No Thumbnail Available
    ItemMetadata only
    Bug introducing changes: A case study with Android
    (IEEE, 2012) Asaduzzaman, M.; Bullock, M.C.; Roy, C.K.; Schneider, K.A.
    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.
  • No Thumbnail Available
    ItemMetadata only
    Evaluating Code Clone Genealogies at Release Level: An Empirical Study
    (IEEE, 2010) Saha, R.K.; Asaduzzaman, M.; Zibran, M.F.; Roy, C.K.; Schneider, K.A.
    Code clone genealogies show how clone groups evolve with the evolution of the associated software system, and thus could provide important insights on the maintenance implications of clones. In this paper, we provide an in-depth empirical study for evaluating clone genealogies in evolving open source systems at the release level. We develop a clone genealogy extractor, examine 17 open source C, Java, C++ and C# systems of diverse varieties and study different dimensions of how clone groups evolve with the evolution of the software systems. Our study shows that majority of the clone groups of the clone genealogies either propagate without any syntactic changes or change consistently in the subsequent releases, and that many of the genealogies remain alive during the evolution. These findings seem to be consistent with the findings of a previous study that clones may not be as detrimental in software maintenance as believed to be (at least by many of us), and that instead of aggressively refactoring clones, we should possibly focus on tracking and managing clones during the evolution of software systems.