Computing Reviews
Today's Issue Hot Topics Search Browse Recommended My Account Log In
Review Help
Search
Oops! . . . I changed it again
Göde N., Harder J.  IWSC 2011 (Proc. of the 5th International Workshop on Software Clones, Waikiki, Honolulu, HI, May 23, 2011)14-20.2011.Type:Proceedings
Date Reviewed: Apr 18 2012

Much effort has been expended in attempting to discover how errors are introduced into software, with the hope of being able to reduce the potentially serious faults occurring in applications. One area of interest is clones--fragments of code that are repeated within a piece of software. It has long been recognized that sections of repeated code can cause problems when one section is changed to correct an error while a repeated section is not updated; as a result, the repeated section still contains the uncorrected problem. It is also common for clones to change in separate ways (inconsistently) during code development.

Previous work has studied how individual clones change during an application’s development and how to identify unwanted inconsistencies. The work reported here tries to go one step further by investigating consecutive changes to clones over a substantial period (five years) of the lifetime of a number of applications. The authors provide a systematic description of consecutive changes to clones and go on to analyze three applications with a full Subversion history. They then use one application (a tool they had written to identify and track clones in software) to see whether they can identify any changes that led to undiscovered errors.

As the case study failed to provide any strong conclusions, this paper should be regarded as a first step; therefore, it’s primarily only of interest to researchers in this area. A less specialized reader would have benefited greatly if the example given near the end of the paper had been brought forward and described in more detail.

Reviewer:  T. Hopkins Review #: CR140066 (1209-0929)
Bookmark and Share
  Featured Reviewer  
 
Restructuring, Reverse Engineering, And Reengineering (D.2.7 ... )
 
Would you recommend this review?
yes
no
Other reviews under "Restructuring, Reverse Engineering, And Reengineering": Date
Software evolution: the software maintenance challenge
Arthur L., Wiley-Interscience, New York, NY, 1988. Type: Book (9789780471628712)
Mar 1 1989
The year 2000 computing crisis
Murray J., Murray M., McGraw-Hill, Inc., New York, NY, 1996. Type: Book (9780079129451)
Oct 1 1996
Constraint-based design recovery for software reengineering
Woods S., Quilici A., Yang Q., Kluwer Academic Publishers, Norwell, MA, 1998. Type: Book (9780792380672)
Dec 1 1998
more...

E-Mail This Printer-Friendly
Send Your Comments
Contact Us
Reproduction in whole or in part without permission is prohibited.   Copyright 1999-2024 ThinkLoud®
Terms of Use
| Privacy Policy