Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Resource-constrained edge devices increasingly require local AI inference while providing limited memory, storage, compute capability, and operating-system support. This paper presents a cartridge-oriented architecture in which model-specific inference information is packaged as a compact, validated artifact executed by a reusable native inference engine. Unlike conventional deployments that embed models within a general-purpose inference runtime, the proposed approach establishes an explicit deployment boundary between the reusable execution engine and replaceable AI cartridges. A prototype was implemented as a bare-metal system and evaluated using QEMU RISC-V and ARM Cortex-M3 targets. The experiments demonstrate independent artifact replacement, loader-level validation, execution of multiple operator structures, and byte-identical cartridge portability across the two architectures. The results provide evidence that a model-specific deployment artifact can be separated from a reusable native execution engine without requiring a general-purpose operating system or interpreter. The idea is conceptually inspired by the cartridge-based architecture of classic Mario game consoles: a reusable console provides the execution platform, while a replaceable cartridge contains game-specific content and logic. Note: This is an unpublished preprint version of a manuscript that was previously considered at an IEEE venue. The authors retain full copyright of this early draft version. The work is being self-archived here prior to extension and future journal/conference submission.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.