arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2604.15468cs.SEcs.AI
收藏

半可执行堆栈:智能软件工程与SE范围的扩展

The Semi-Executable Stack: Agentic Software Engineering and the Expanding Scope of SE

Chalmers University of Technology(挑战者技术大学);Volvo Group(沃尔沃集团)

Robert Feldt, Per Lenberg, Julian Frattini, Dhasarathy Parthasarathy

AI总结:

本文探讨了软件工程领域因AI系统发展而扩展的范围,提出半可执行堆栈模型以分析可执行代码与非可执行 artifacts 的结合,通过三个案例研究重新定义工程目标,提供保留与净化的决策框架。

摘要:

基于LLM和智能代理的AI系统正被视为对软件工程的潜在威胁。随着基础模型增强、代理能跨步骤规划和执行,诸如 scaffolding、常规测试生成、简单bug修复等任务显得更加暴露。本文主张软件工程并不失去相关性,而是工程对象扩展到半可执行 artifacts,包括自然语言、工具、工作流、控制机制和组织规程。半可执行堆栈模型作为六环诊断参考模型,涵盖可执行 artifacts、教学 artifacts、 orchestrated execution、控件、操作逻辑及社会制度适配。该模型帮助定位贡献、瓶颈或组织转型的位置及其依赖的相邻环。本文通过三个案例研究,将熟悉反对意见重新定义为工程目标,并提供保留与净化的决策指南。本文为概念性 keynote,旨在诊断和设定议程而非实证研究。

英文摘要:

AI-based systems, currently driven largely by LLMs and tool-using agentic harnesses, are increasingly discussed as a possible threat to software engineering. Foundation models get stronger, agents can plan and act across multiple steps, and tasks such as scaffolding, routine test generation, straightforward bug fixing, and small integration work look more exposed than they did only a few years ago. The result is visible unease not only among students and junior developers, but also among experienced practitioners who worry that hard-won expertise may lose value. This paper argues for a different reading. The important shift is not that software engineering loses relevance. It is that the thing being engineered expands beyond executable code to semi-executable artifacts; combinations of natural language, tools, workflows, control mechanisms, and organizational routines whose enactment depends on human or probabilistic interpretation rather than deterministic execution. The Semi-Executable Stack is introduced as a six-ring diagnostic reference model for reasoning about that expansion, spanning executable artifacts, instructional artifacts, orchestrated execution, controls, operating logic, and societal and institutional fit. The model helps locate where a contribution, bottleneck, or organizational transition primarily sits, and which adjacent rings it depends on. The paper develops the argument through three worked cases, reframes familiar objections as engineering targets rather than reasons to dismiss the transition, and closes with a preserve-versus-purify heuristic for deciding which legacy software engineering processes, controls, and coordination routines should be kept and which should be simplified or redesigned. This paper is a conceptual keynote companion: diagnostic and agenda-setting rather than empirical.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑