Home > Research > Publications & Outputs > Mining framework usage changes from instantiati...

Research

Links

Text available via DOI:

Keywords

View graph of relations

Mining framework usage changes from instantiation code

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Mining framework usage changes from instantiation code. / Schäfer, Thorsten; Jonas, Jan; Mezini, Mira.
ICSE '08 Proceedings of the 30th international conference on Software engineering. New York: ACM, 2008. p. 471-480.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Schäfer, T, Jonas, J & Mezini, M 2008, Mining framework usage changes from instantiation code. in ICSE '08 Proceedings of the 30th international conference on Software engineering. ACM, New York, pp. 471-480, ICSE '08: 30th International Conference on Software Engineering , Leipzig, Germany, 10/05/08. https://doi.org/10.1145/1368088.1368153

APA

Schäfer, T., Jonas, J., & Mezini, M. (2008). Mining framework usage changes from instantiation code. In ICSE '08 Proceedings of the 30th international conference on Software engineering (pp. 471-480). ACM. https://doi.org/10.1145/1368088.1368153

Vancouver

Schäfer T, Jonas J, Mezini M. Mining framework usage changes from instantiation code. In ICSE '08 Proceedings of the 30th international conference on Software engineering. New York: ACM. 2008. p. 471-480 doi: 10.1145/1368088.1368153

Author

Schäfer, Thorsten ; Jonas, Jan ; Mezini, Mira. / Mining framework usage changes from instantiation code. ICSE '08 Proceedings of the 30th international conference on Software engineering. New York : ACM, 2008. pp. 471-480

Bibtex

@inproceedings{2122b84042c04e43af5b34b06e9d8ed2,
title = "Mining framework usage changes from instantiation code",
abstract = "Framework evolution may break existing users, which need to be migrated to the new framework version. This is a tedious and error-prone process that benefits from automation. Existing approaches compare two versions of the framework code in order to find changes caused by refactorings. However, other kinds of changes exist, which are relevant for the migration. In this paper, we propose to mine framework usage change rules from already ported instantiations, the latter being applications build on top of the framework, or test cases maintained by the framework developers. Our evaluation shows that our approach finds usage changes not only caused by refactorings, but also by conceptual changes within the framework. Further, it copes well with some issues that plague tools focusing on finding refactorings such as deprecated program elements or multiple changes applied to a single program element.",
keywords = "evolution, framework comprehension, migration",
author = "Thorsten Sch{\"a}fer and Jan Jonas and Mira Mezini",
year = "2008",
doi = "10.1145/1368088.1368153",
language = "English",
isbn = "978-1-60558-079-1 ",
pages = "471--480",
booktitle = "ICSE '08 Proceedings of the 30th international conference on Software engineering",
publisher = "ACM",
note = " ICSE '08: 30th International Conference on Software Engineering ; Conference date: 10-05-2008 Through 18-05-2008",

}

RIS

TY - GEN

T1 - Mining framework usage changes from instantiation code

AU - Schäfer, Thorsten

AU - Jonas, Jan

AU - Mezini, Mira

PY - 2008

Y1 - 2008

N2 - Framework evolution may break existing users, which need to be migrated to the new framework version. This is a tedious and error-prone process that benefits from automation. Existing approaches compare two versions of the framework code in order to find changes caused by refactorings. However, other kinds of changes exist, which are relevant for the migration. In this paper, we propose to mine framework usage change rules from already ported instantiations, the latter being applications build on top of the framework, or test cases maintained by the framework developers. Our evaluation shows that our approach finds usage changes not only caused by refactorings, but also by conceptual changes within the framework. Further, it copes well with some issues that plague tools focusing on finding refactorings such as deprecated program elements or multiple changes applied to a single program element.

AB - Framework evolution may break existing users, which need to be migrated to the new framework version. This is a tedious and error-prone process that benefits from automation. Existing approaches compare two versions of the framework code in order to find changes caused by refactorings. However, other kinds of changes exist, which are relevant for the migration. In this paper, we propose to mine framework usage change rules from already ported instantiations, the latter being applications build on top of the framework, or test cases maintained by the framework developers. Our evaluation shows that our approach finds usage changes not only caused by refactorings, but also by conceptual changes within the framework. Further, it copes well with some issues that plague tools focusing on finding refactorings such as deprecated program elements or multiple changes applied to a single program element.

KW - evolution

KW - framework comprehension

KW - migration

U2 - 10.1145/1368088.1368153

DO - 10.1145/1368088.1368153

M3 - Conference contribution/Paper

SN - 978-1-60558-079-1

SP - 471

EP - 480

BT - ICSE '08 Proceedings of the 30th international conference on Software engineering

PB - ACM

CY - New York

T2 - ICSE '08: 30th International Conference on Software Engineering

Y2 - 10 May 2008 through 18 May 2008

ER -