Standard

Measuring Library Stability Through Historical Version Analysis. / Raemaekers, SBA; van Deursen, A; Visser, J.

Proceedings of the International Conference on Software Maintenance (ICSM). ed. / sn. New York / Los Alamitos : IEEE, 2012. p. 378-387.

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

Harvard

Raemaekers, SBA, van Deursen, A & Visser, J 2012, Measuring Library Stability Through Historical Version Analysis. in sn (ed.), Proceedings of the International Conference on Software Maintenance (ICSM). IEEE, New York / Los Alamitos, pp. 378-387. https://doi.org/10.1109/ICSM.2012.6405296

APA

Raemaekers, SBA., van Deursen, A., & Visser, J. (2012). Measuring Library Stability Through Historical Version Analysis. In sn (Ed.), Proceedings of the International Conference on Software Maintenance (ICSM) (pp. 378-387). New York / Los Alamitos: IEEE. https://doi.org/10.1109/ICSM.2012.6405296

Vancouver

Raemaekers SBA, van Deursen A, Visser J. Measuring Library Stability Through Historical Version Analysis. In sn, editor, Proceedings of the International Conference on Software Maintenance (ICSM). New York / Los Alamitos: IEEE. 2012. p. 378-387 https://doi.org/10.1109/ICSM.2012.6405296

Author

Raemaekers, SBA ; van Deursen, A ; Visser, J. / Measuring Library Stability Through Historical Version Analysis. Proceedings of the International Conference on Software Maintenance (ICSM). editor / sn. New York / Los Alamitos : IEEE, 2012. pp. 378-387

BibTeX

@inproceedings{4eebb2d9e6eb4b3f8b08a51f4c8fce9d,
title = "Measuring Library Stability Through Historical Version Analysis",
abstract = "Backward compatibility is a major concern for any library developer. In this paper, we evaluate how stable a set of frequently used third-party libraries is in terms of method removals, implementation change, the ratio of change in old methods to change in new ones and the percentage of new methods in each snapshot. We provide a motivating example of a commercial company which demonstrates several issues associated with the usage of third-party libraries. To obtain dependencies from software systems we developed a framework which extracts dependencies from Maven build files and which analyzes system and library code. We propose four metrics which provide different insights in the implementation and interface stability of a library. The usage frequency of library methods is utilized as a weight in the final metric and is obtained from a dataset of more than 2300 snapshots of 140 industrial Java systems. We finally describe three scenarios and an example of the application of our metrics.",
keywords = "Conf.proc. > 3 pag",
author = "SBA Raemaekers and {van Deursen}, A and J. Visser",
year = "2012",
doi = "10.1109/ICSM.2012.6405296",
language = "English",
isbn = "978-1-4673-1067-3",
pages = "378--387",
editor = "sn",
booktitle = "Proceedings of the International Conference on Software Maintenance (ICSM)",
publisher = "IEEE",
address = "United States",

}

RIS

TY - GEN

T1 - Measuring Library Stability Through Historical Version Analysis

AU - Raemaekers, SBA

AU - van Deursen, A

AU - Visser, J.

PY - 2012

Y1 - 2012

N2 - Backward compatibility is a major concern for any library developer. In this paper, we evaluate how stable a set of frequently used third-party libraries is in terms of method removals, implementation change, the ratio of change in old methods to change in new ones and the percentage of new methods in each snapshot. We provide a motivating example of a commercial company which demonstrates several issues associated with the usage of third-party libraries. To obtain dependencies from software systems we developed a framework which extracts dependencies from Maven build files and which analyzes system and library code. We propose four metrics which provide different insights in the implementation and interface stability of a library. The usage frequency of library methods is utilized as a weight in the final metric and is obtained from a dataset of more than 2300 snapshots of 140 industrial Java systems. We finally describe three scenarios and an example of the application of our metrics.

AB - Backward compatibility is a major concern for any library developer. In this paper, we evaluate how stable a set of frequently used third-party libraries is in terms of method removals, implementation change, the ratio of change in old methods to change in new ones and the percentage of new methods in each snapshot. We provide a motivating example of a commercial company which demonstrates several issues associated with the usage of third-party libraries. To obtain dependencies from software systems we developed a framework which extracts dependencies from Maven build files and which analyzes system and library code. We propose four metrics which provide different insights in the implementation and interface stability of a library. The usage frequency of library methods is utilized as a weight in the final metric and is obtained from a dataset of more than 2300 snapshots of 140 industrial Java systems. We finally describe three scenarios and an example of the application of our metrics.

KW - Conf.proc. > 3 pag

UR - http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2012-012.pdf

U2 - 10.1109/ICSM.2012.6405296

DO - 10.1109/ICSM.2012.6405296

M3 - Conference contribution

SN - 978-1-4673-1067-3

SP - 378

EP - 387

BT - Proceedings of the International Conference on Software Maintenance (ICSM)

A2 - sn, null

PB - IEEE

CY - New York / Los Alamitos

ER -

ID: 1273087