The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
CatchUp!: capturing and replaying refactorings to support API evolution
Abstract
Library developers who have to evolve a library to accommodate changing requirements often face a dilemma: Either they implement a clean, efficient solution but risk breaking client code, or they maintain compatibility with client code, but pay with increased design complexity and thus higher maintenance costs over time.We address this dilemma by presenting a lightweight approach for evolving application programming interfaces (APIs), which does not depend on version control or configuration management systems. Instead, we capture API refactoring actions as a developer evolves an API. Users of the API can then replay the refactorings to bring their client software components up to date.We present catchup!, an implementation of our approach that captures and replays refactoring actions within an integrated development environment semi-automatically. Our experiments suggest that our approach could be valuable in practice.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
A survey of software refactoring
Mens, T., & Tourwe, T. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.1265817 · Cited by 1,193
Refactoring object-oriented frameworks
Opdyke, W. F. (1992) · Illinois Digital Environment for Access to Learning and Scholarship (University of Illinois at Urbana-Champaign) · Cited by 1,126
Kerievsky, J. (2004) · Lecture Notes in Computer Science · doi:10.1007/978-3-540-27777-4_54 · Cited by 406
A model for compound type changes encountered in schema evolution
Lerner, B. S. (2000) · ACM Transactions on Database Systems · doi:10.1145/352958.352983 · Cited by 132
Cited by
Smart Contract Development: Challenges and Opportunities
Zou, W., Lo, D., Kochhar, P. S., Le, X.-B. D., Xia, X., Feng, Y., Chen, Z., & Xu, B. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2942301 · Cited by 727
Kagdi, H., Collard, M. L., & Maletic, J. I. (2007) · Journal of Software Maintenance and Evolution: Research and Practice · doi:10.1002/smr.344 · Cited by 413
UMLDiff: an algorithm for object-oriented design differencing
Xing, Z., & Stroulia, E. (2005) · Proceedings of the 20th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/1101908.1101919 · Cited by 374
An Empirical Study of API Stability and Adoption in the Android Ecosystem
McDonnell, T., Ray, B., & Kim, M. (2013) · 2013 IEEE International Conference on Software Maintenance · doi:10.1109/icsm.2013.18 · Cited by 304
Accurate and efficient refactoring detection in commit history
Tsantalis, N., Mansouri, M., Eshkevari, L. M., Mazinanian, D., & Dig, D. (2018) · Proceedings of the 40th International Conference on Software Engineering · doi:10.1145/3180155.3180206 · Cited by 300
Metadata
- Authors
- Henkel, J., & Diwan, A.
- Venue
- Proceedings of the 27th international conference on Software engineering - ICSE '05
- Publisher
- ACM Press
- Published
- 2005
- Pages
- 274
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2112847033
- Cited by
- 269
- References
- 5
- Type
- conference abstract
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: CatchUp!: capturing and replaying refactorings to support API evolution. https://app.cochat.ai/papers/10.1145/1062455.1062512
- The paper
- Henkel, J., & Diwan, A. (2005). CatchUp!: capturing and replaying refactorings to support API evolution. Proceedings of the 27th international conference on Software engineering - ICSE '05. https://doi.org/10.1145/1062455.1062512
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.