Using version control history to follow the changes of source code elements

Zoltán Tóth, Gábor Novák, Rudolf Ferenc, István Siket

Research output: Chapter in Book/Report/Conference proceedingConference contribution

7 Citations (Scopus)

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.

Original languageEnglish
Title of host publicationProceedings of the European Conference on Software Maintenance and Reengineering, CSMR
Pages319-322
Number of pages4
DOIs
Publication statusPublished - 2013
Event17th European Conference on Software Maintenance and Reengineering, CSMR 2013 - Genova, Italy
Duration: Mar 5 2013Mar 8 2013

Other

Other17th European Conference on Software Maintenance and Reengineering, CSMR 2013
CountryItaly
CityGenova
Period3/5/133/8/13

Fingerprint

Computer programming languages
Control systems
Engineers

Keywords

  • Repository Mining
  • Static Analysis
  • Version Control System

ASJC Scopus subject areas

  • Software

Cite this

Tóth, Z., Novák, G., Ferenc, R., & Siket, I. (2013). Using version control history to follow the changes of source code elements. In Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR (pp. 319-322). [6498479] https://doi.org/10.1109/CSMR.2013.40

Using version control history to follow the changes of source code elements. / Tóth, Zoltán; Novák, Gábor; Ferenc, Rudolf; Siket, István.

Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2013. p. 319-322 6498479.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Tóth, Z, Novák, G, Ferenc, R & Siket, I 2013, Using version control history to follow the changes of source code elements. in Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR., 6498479, pp. 319-322, 17th European Conference on Software Maintenance and Reengineering, CSMR 2013, Genova, Italy, 3/5/13. https://doi.org/10.1109/CSMR.2013.40
Tóth Z, Novák G, Ferenc R, Siket I. Using version control history to follow the changes of source code elements. In Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2013. p. 319-322. 6498479 https://doi.org/10.1109/CSMR.2013.40
Tóth, Zoltán ; Novák, Gábor ; Ferenc, Rudolf ; Siket, István. / Using version control history to follow the changes of source code elements. Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR. 2013. pp. 319-322
@inproceedings{c3443d4b2834429588a7f5aee493c4da,
title = "Using version control history to follow the changes of source code elements",
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",
author = "Zolt{\'a}n T{\'o}th and G{\'a}bor Nov{\'a}k and Rudolf Ferenc and Istv{\'a}n Siket",
year = "2013",
doi = "10.1109/CSMR.2013.40",
language = "English",
isbn = "9780769549484",
pages = "319--322",
booktitle = "Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR",

}

TY - GEN

T1 - Using version control history to follow the changes of source code elements

AU - Tóth, Zoltán

AU - Novák, Gábor

AU - Ferenc, Rudolf

AU - Siket, István

PY - 2013

Y1 - 2013

N2 - 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.

AB - 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.

KW - Repository Mining

KW - Static Analysis

KW - Version Control System

UR - http://www.scopus.com/inward/record.url?scp=84877296626&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84877296626&partnerID=8YFLogxK

U2 - 10.1109/CSMR.2013.40

DO - 10.1109/CSMR.2013.40

M3 - Conference contribution

AN - SCOPUS:84877296626

SN - 9780769549484

SP - 319

EP - 322

BT - Proceedings of the European Conference on Software Maintenance and Reengineering, CSMR

ER -