LEADER 02703oam  2200433   450 
001 9910795516903321
005 20230809235824.0
010   $a3-8325-9259-8
035   $a(CKB)5120000000117387
035   $a(MiAaPQ)EBC6480959
035   $a5c7aad7d-5480-4e7a-8f9d-7583b0dd2d03
035   $a(EXLCZ)995120000000117387
100   $a20210710d2017      uy             0
101 0 $aeng
135   $aurcnu||||||||
181   $ctxt$2rdacontent
182   $cc$2rdamedia
183   $acr$2rdacarrier
200 10$aSoftware clones $eguilty until proven innocent? /$fJan Harder
210  1$aBerlin, Germany :$cLogos Verlag Berlin,$d[2017]
210  4$d©2017
215   $a1 online resource (252 pages) $cillustrations
300   $aPublicationDate: 20171211
311   $a3-8325-4588-3 
320   $aIncludes bibliographical references.
330   $aLong description: Software systems contain redundant code that originated from the use of copy and paste. While such cloning may be beneficial in the short term as it accelerates development, it is frequently despised as a risk to maintainability and quality in the long term. Code clones are said to cause extra change effort, because changes have to be propagated to all copies. They are also suspected to cause bugs when the copied code fragments are changed inconsistently.           These accusations may be plausible but are not based on empirical facts. Indeed, they are prejudice. In the recent past, science has started the endeavor to find empirical evidence to support the alleged effects of clones.           In this thesis, we analyze the effects of clones from three different perspectives. First, we investigate whether clones do indeed increase the maintenance effort in real and long lived software systems. Second, we analyze potential reasons for the cases where clones do cause bugs. Third, we take a new perspective to the problem by measuring the effects of clones in a controlled experiment. This allows us to gather new insights by observing software developers during their work, whereas previous studies were based on historical data.           With our work we aim to empirically find advice for practitioners how to deal with clones and, if necessary, to provide an empirical basis for tools that help developers to manage clones.
606   $aSoftware engineering
606   $aComputer programmers
615  0$aSoftware engineering.
615  0$aComputer programmers.
676   $a005.12
700   $aHarder$b Jan$01468235
801  0$bMiAaPQ
801  1$bMiAaPQ
801  2$bUtOrBLW
906   $aBOOK
912   $a9910795516903321
996   $aSoftware clones$93679307
997   $aUNINA