Answers are grounded in this paper and cite their sources.
Increasingly sophisticated customer needs and regulatory constraints lead to growing complexity in product development. A common solution to manage this complexity is Model‐based Systems Engineering, where activity diagrams contribute to the design of functional architectures. However, their modeling process is time‐consuming and complex, creating the demand for assistance and acceleration. Current methods are limited to basic activity diagrams and overlook architecture definition activities. Moreover, new possibilities through Large Language Models haven't been explored in detail. To address this, a comprehensive three‐part approach using Large Language Models is proposed. The first part defines the use case's behavior with an activity diagram. The second part assigns actions to system functions, starting functional architecture generation. The third part deploys a pipeline to define information exchange between actions across architectural elements. Latter two pipelines use vector databases to reuse existing modeling elements. An preliminary evaluation by expert interviews shows that the proposed approach can offer assistance for manual modeling activities. With that, a step towards a faster and more complete generation of activity diagrams and functional architectures is taken.
No takes yet. Share an insight, caveat, or question.
Schleifer et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: