@conference {TNF13,
	title = {Using Version Control History to Follow the Changes of Source Code Elements},
	booktitle = {Proceedings of the 17th European Conference on Software Maintenance and Reengineering (CSMR 2013)},
	year = {2013},
	month = {mar},
	pages = {319{\textendash}322},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Genova, Italy},
	abstract = {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.},
	keywords = {Repository Mining, Static Analysis, Version Control System},
	doi = {10.1109/CSMR.2013.40},
	url = {http://ieeexplore.ieee.org/document/6498479/},
	author = {T{\'o}th, Zolt{\'a}n and Nov{\'a}k, G{\'a}bor and Rudolf Ferenc and Istv{\'a}n Siket}
}
