This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
2013 17th European Conference on Software Maintenance and Reengineering
Using Version Control History to Follow the Changes of Source Code Elements
Genova, Italy Italy
March 05-March 08
ISBN: 978-1-4673-5833-0
Version control systems store the whole history of the source code. Since the source code of a system is organized into files and folders, the history tells us the concerned files and their changed lines only but software engineers are also interested in which source code elements (e.g. classes or methods) are affected by a change. Unfortunately, in most programming languages source code elements do not follow the file system hierarchy, which means that a file can contain more classes and methods and a class can be stored in more files, which makes it difficult to determine the changes of classes by using the changes of files. To solve this problem we developed an algorithm, which is able to follow the changes of the source code elements by using the changes of files and we successfully applied it on the Web Kit open source system.
Index Terms:
Static Analysis,Version Control System,Repository Mining
Citation:
Zoltan Toth, Gabor Novak, Rudolf Ferenc, Istvan Siket, "Using Version Control History to Follow the Changes of Source Code Elements," csmr, pp.319-322, 2013 17th European Conference on Software Maintenance and Reengineering, 2013
Usage of this product signifies your acceptance of the Terms of Use.