Show simple item record

dc.contributor.authorMondal, M.
dc.contributor.authorRahman, M.S.
dc.contributor.authorSaha, R.K.
dc.contributor.authorKrinke, J.
dc.contributor.authorSchneider, K.A.
dc.date.accessioned2015-07-29T19:27:46Z
dc.date.available2015-07-29T19:27:46Z
dc.date.issued2011
dc.identifier.urihttp://hdl.handle.net/1880/50703
dc.description.abstractThe impacts of clones on software maintenance is a long-lived debate on whether clones are beneficial or not. Some researchers argue that clones lead to additional changes during the maintenance phase and thus increase the overall maintenance effort. Moreover, they note that inconsistent changes to clones may introduce faults during evolution. On the other hand, other researchers argue that cloned code exhibits more stability than non-cloned code. Studies resulting in such contradictory outcomes may be a consequence of using different methodologies, using different clone detection tools, defining different impact assessment metrics, and evaluating different subject systems. In order to understand the conflicting results from the studies, we plan to conduct a comprehensive empirical study using a common framework incorporating nine existing methods that yielded mostly contradictory findings. Our research strategy involves implementing each of these methods using four clone detection tools and evaluating the methods on more than fifteen subject systems of different languages and of a diverse nature. We believe that our study will help eliminate tool and study biases to resolve conflicts regarding the impacts of clones on software maintenance.en_US
dc.publisherIEEEen_US
dc.titleAn Empirical Study of the Impacts of Clones in Software Maintenanceen_US
dc.typeunknown
dc.description.refereedYesen_US
dc.publisher.urlhttp://dx.doi.org/10.1109/ICPC.2011.14en_US
dc.identifier.doi10.1109/ICPC.2011.14


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record