Technical Report on Neural Language Models and Few-Shot Learning for Systematic Requirements Processing in MDSE
Vincent Bertram, Miriam Bo{\ss}, Evgeny Kusmenko, Imke Helene, Nachmann, Bernhard Rumpe, Danilo Trotta, Louis Wachtmeister

TL;DR
This paper explores using large pretrained language models with few-shot learning to automatically translate informal automotive requirements into structured, formal languages, enhancing automation and reducing ambiguity in systems engineering.
Contribution
It introduces a novel application of few-shot learning with pretrained language models for translating informal requirements into formal DSLs in automotive systems engineering.
Findings
Few-shot learning with less than ten examples effectively trains models.
Models successfully incorporate keywords and syntactic rules.
Improves automation and reduces ambiguity in requirements processing.
Abstract
Systems engineering, in particular in the automotive domain, needs to cope with the massively increasing numbers of requirements that arise during the development process. To guarantee a high product quality and make sure that functional safety standards such as ISO26262 are fulfilled, the exploitation of potentials of model-driven systems engineering in the form of automatic analyses, consistency checks, and tracing mechanisms is indispensable. However, the language in which requirements are written, and the tools needed to operate on them, are highly individual and require domain-specific tailoring. This hinders automated processing of requirements as well as the linking of requirements to models. Introducing formal requirement notations in existing projects leads to the challenge of translating masses of requirements and process changes on the one hand and to the necessity of the…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
