mlsanityData to 14 Oct 2026

Every Maintenance Has Its Exemplar: The Future of Software Maintenance through Migration

arXiv 2602.14046 ↗First posted 15 Feb 2026cs.SEcited by 1

Not on the map. Why?

Abstract (arXiv)

Maintenance is a critical stage in the software lifecycle, ensuring that post-release systems remain reliable, efficient, and adaptable. However, manual software maintenance is labor-intensive, time-consuming, and error-prone, which highlights the urgent need for automation. Learning from maintenance activities conducted on other software systems offers an effective way to improve efficiency. In particular, recent research has demonstrated that migration-based approaches transfer knowledge, artifacts, or solutions from one system to another and show strong potential in tasks such as API evolution adaptation, software testing, and migrating patches for fault correction. This makes migration-based maintenance a valuable research direction for advancing automated maintenance. This paper takes a step further by presenting the first systematic research agenda on migration-based approaches to software maintenance. We characterize the migration-based maintenance lifecycle through four key stages: ding182 identifying a maintenance task that can be addressed through migration, ding183 selecting suitable migration sources for the target project,ding184 matching relevant data across systems and adapting the migrated data to the target context, and ding185 validating the correctness of the migration. We also analyze the challenges that may arise at each stage. Our goal is to encourage the community to explore migration-based approaches more thoroughly and to tackle the key challenges that must be solved to advance automated software maintenance.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). First posted on arXiv 15 Feb 2026.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 14 Oct)

Citing papers per year: 2026: 1.

1 paper.