| Tweet | |
| M. Iriyama, Y. Higo, and S. Kusumoto, "Classification of Changes Based on API," In Proceedings of the 23rd International Conference on Product-Focused Software Process Improvement (PROFES2022), pp. 061-070, November 2022. | |
| ID | 770 |
| 分類 | 国際会議 |
| タグ | api changes classification |
| 表題 (title) |
Classification of Changes Based on API |
| 表題 (英文) |
|
| 著者名 (author) |
Masashi Iriyama,Yoshiki Higo,Shinji Kusumoto |
| 英文著者名 (author) |
Masashi Iriyama,Yoshiki Higo,Shinji Kusumoto |
| 編者名 (editor) |
|
| 編者名 (英文) |
|
| キー (key) |
Masashi Iriyama,Yoshiki Higo,Shinji Kusumoto |
| 書籍・会議録表題 (booktitle) |
Proceedings of the 23rd International Conference on Product-Focused Software Process Improvement (PROFES2022) |
| 書籍・会議録表題(英文) |
|
| 巻数 (volume) |
|
| 号数 (number) |
|
| ページ範囲 (pages) |
061-070 |
| 組織名 (organization) |
|
| 出版元 (publisher) |
|
| 出版元 (英文) |
|
| 出版社住所 (address) |
|
| 刊行月 (month) |
11 |
| 出版年 (year) |
2022 |
| 採択率 (acceptance) |
|
| URL |
|
| 付加情報 (note) |
|
| 注釈 (annote) |
|
| 内容梗概 (abstract) |
In software maintenance process, software libraries are occasionally updated, and their APIs may also be updated. API changes can be classified into two categories: changes that break backward compatibility (in short, breaking changes) and changes that maintain backward compatibility (in short, maintaining changes). Detecting API changes and determining whether each is a breaking or maintaining change is useful for code reviews and release note generations. Since it is burdensome to check API changes manually, research on automatic detection of API changes has been conducted. APIDiff is a tool that automatically detects API changes and classifies the detected changes into breaking and maintaining ones. APIDiff takes two versions of a Java library as input, and it detects API changes based on the similarity of the input code. Each detected change is classified into the two kinds of changes. However, since APIDiff identifies breaking changes for each type of change, it tends to fail to correctly classify changes if multiple changes were conducted to a single API. On the other hand, our proposed technique in this paper groups changes by APIs and checks whether each group contains changes that break backward compatibility. Classifying API changes more correctly by our technique will be helpful for release note generations in maintenance process. We conducted experiments on eight open-source software and confirmed that our technique could detect API changes more correctly than APIDiff. We also confirmed that the proposed technique could classify API changes more correctly into breaking and maintaining ones than APIDiff. |
| 論文電子ファイル | m-iriyam_202211_profes.pdf (application/pdf) [一般閲覧可] |
| BiBTeXエントリ |
@inproceedings{id770,
title = {Classification of Changes based on {API}},
author = {Masashi Iriyama and Yoshiki Higo and Shinji Kusumoto},
booktitle = {Proceedings of the 23rd International Conference on Product-Focused Software Process Improvement (PROFES2022)},
pages = {061-070},
month = {11},
year = {2022},
}
|