Oct 2026· Proceedings of the ACM/IEEE 29th International Conference on Model Driven Engineering Languages and Systems· 0 citations· 6 references
Abstract
Large Language Models are increasingly used to generate structured engineering artifacts, yet the instruction artifacts that govern this generation are rarely treated as modeling artifacts in their own right. They typically appear as monolithic prompt blocks, schemas, or informal examples. When tools, metamodels, APIs, or domain vocabularies evolve, stable domain concepts, volatile tool details, validators, and examples drift together in a single prompt contract. This paper puts forward the thesis that prompt-level instruction artifacts should be understood as versioned modeling languages: explicit artifacts that define the LLM-facing structure required to obtain tool-consumable outputs. We realize this idea through Modular Meta-Language-defined Structure Instructions (MMLDSI), a modular architecture that decomposes structured instructions into versioned modules with explicit interfaces, profiles, adapters, validators, examples, and deterministic rule-deck resolution. Changes to tools or domain concepts can then be represented at the affected modules and profiles rather than hidden inside whole-prompt rewrites. The approach is demonstrated in VR scene generation and automotive security modeling. Across a balanced 320-artifact VR subset, required-key validity reaches 88.1%, while a stricter prompt-contract audit accepts 80.9% and exposes remaining tool-readiness gaps. An offline monolith-to-modular pilot maps 12 legacy feature families and resolves 343 case-specific decks without dependency gaps. Our contribution is not another prompting technique, but a model-management perspective on instruction artifacts for evolving LLM toolchains.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.