Hot Fixing Software: A Comprehensive Review of Terminology, Techniques, and Applications

January 17, 2024 ยท The Cartographer ยท ๐Ÿ› ACM Transactions on Software Engineering and Methodology

๐Ÿ“š THE CARTOGRAPHER: The Cartographer
Survey/review paper โ€” maps the landscape rather than implementing a method.

"No code URL or promise found in abstract"
"Title-pattern auto-detect: Hot Fixing Software: A Comprehensive Review of Terminology, Techniques, and Applications"

Evidence collected by the PWNC Scanner

Authors Carol Hanna, David Clark, Federica Sarro, Justyna Petke arXiv ID 2401.09275 Category cs.SE: Software Engineering Citations 3 Venue ACM Transactions on Software Engineering and Methodology Last Checked 4 days ago
Abstract
A hot fix is an unplanned improvement to a specific time-critical issue deployed to a software system in production. While hot fixing is an essential and common activity in software maintenance, it has never been surveyed as a research activity. Thus, such a review is long overdue. In this paper, we conduct a comprehensive literature review of work on hot fixing. We highlight the fields where this topic has been addressed, inconsistencies we identified in the terminology, gaps in the literature, and directions for future work. Our search concluded with 91 articles on the topic between the years 2000 and 2022. The articles found encompass many different research areas such as log analysis, runtime patching (also known as hot patching), and automated repair, as well as various application domains such as security, mobile, and video games. We find that many directions can take hot fix research forward such as unifying existing terminology, establishing a benchmark set of hot fixes, researching costs and frequency of hot fixes, and researching the possibility of end-to-end automation of detection, mitigation, and deployment. We discuss these avenues in detail to inspire the community to systematize hot fixing as a software engineering activity.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

๐Ÿ“œ Similar Papers

In the same crypt โ€” Software Engineering