Oct 2026· Proceedings of the 41st IEEE/ACM International Conference on Automated Software Engineering· pp. 4463-4468· 1 citation· 17 references
TL;DR
A hybrid pipeline is presented in which local LLMs extract a formal four-view specification that keeps proprietary source code entirely on-premises, while cloud models generate target implementations from specifications only, never accessing the legacy codebase.
Abstract
We report on the automated modernization of a business-critical terminal operating system deployed across multiple sites of a major European port infrastructure company, comprising a heterogeneous technology stack accumulated over many years of continuous development: over 22,000 source files, about 10,000 of them C#, a multi-layered web forms UI, a complex Oracle database, and extensive operational documentation. Most current LLM-assisted modernization approaches rely on cloud-based models, raising intellectual property and security concerns that prevent adoption in industrial settings. We present a hybrid pipeline in which local LLMs extract a formal four-view specification that keeps proprietary source code entirely on-premises, while cloud models generate target implementations from specifications only, never accessing the legacy codebase. The pipeline extracts structural domain models, behavioral rules, process state machines, and screen presentations across 48 bounded contexts via a two-pass LLM extraction approach. Against a curated reference on a CRM probe, the best local model reaches a structural fidelity of 0.83, while two of seven candidates fail to emit parseable JSON at all; prompt engineering raises the semantic purity of the extracted domain model from 0.71 to 0.94, whereas legacy documentation adds almost nothing. Following a test-first approach, 5,451 behavioral tests were generated from specifications alone before any target implementation, and two runnable application stacks (Python/FastAPI and .NET 8 Blazor) were produced. We report concrete lessons on prompt engineering, structured output generation, and the practical boundaries between automation and manual intervention.
A legacy application re-engineering platform that uses business context data and the source code of a full-stack software system to inform five LLM-based agents that creates and executes the migration plan fully autonomously by only requesting the desired target technology stack.
Sandra Greiner, Andrés Torrejón González, H. Dralle et al.· Proceedings of the 2nd Inter...· 0 citations
Experimental results show that CRTAMS enables trusted-application migration across heterogeneous TEEs with low refactoring cost and moderate execution overhead in the evaluated workloads, while reducing the amount of platform-specific code that developers must write manually.
Di Lu, Qing-Wen Zhang, Yujia Liu et al.· Journal of networking and ne...· 0 citations
Modern software projects increasingly version binary assets alongside source code—files that encode semantic logic authored by engineers yet are stored as opaque blobs by version control systems. Such assets appear across diverse domains: gameplay logic in game engines, circuit designs in EDA tools, and scene hierarchi...
Li-Ran Wang, Zhou-Jun Li· Proceedings of the 28th Inte...· 0 citations
Legacy C codebases remain central to system software and performance-critical infrastructure, but their weak memory safety imposes security and maintenance risks. Recent C-to-Rust translation systems, including LLM-based translators, make automated migration increasingly feasible, yet they still struggle to recover rep...
Jun-Jie Yao, Xiong-Zheng Guan, Jia Feng et al.· 0 citations
We report on our experience validating S3 Express One Zone, a high-performance Amazon S3 storage class launched in November 2023. We focused on its distributed metadata index, which implements a hierarchical namespace using distributed transactions. We check strong consistency and durability under crashes, network dela...
Rajeev Joshi, Bernhard Kragl, V. Fernando et al.· Proceedings of the ACM SIGOP...· 0 citations
This work is building an executable formal semantics for eBPF in F* that explicitly distinguishes cross-platform and platform-specific behaviors and envision this semantics as a practical foundation for a uniform, trustworthy eBPF across platforms.
Yan-Ze Li, Reto Achermann, Ivan Beschastnikh et al.· eBPF@SIGCOMM· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.