Utilizing multi-level concepts for multi-phase modeling

Abstract

In model-based systems engineering projects, engineers from multiple domains collaborate by establishing a common system model. Multi-level modeling is a technique that can be used to model the development from abstract ideas to concrete implementations. However, current multi-level modeling approaches are not adequate for processes with multiple modeling phases that might have to be rearranged later. In this paper, we introduce multi-phase modeling that utilizes concepts of multi-level modeling by considering a description of the expected phase ordering per domain. Constraints aware of this context can express that certain elements are only valid in specific phases without having to determine a concrete phase ordering for a particular model. This enables using multi-phase modeling in flexible workflows, adapting to changing requirements and the definition of access rules in domain notation. We show feasibility of this multi-phase modeling by applying it to multiple real-life systems engineering projects of the aerospace domain.

Evolution of Domain-Specific Modeling Language: An Example of an Industrial Case Study on an RT-Sequencer

“…Consequently, the model on M1.2 is constructed using elements defined in the metamodel (level M2) and the model on level M1.1. With this separation into two models (on sublevels M1.1 and M1.2), RT-Sequencer supports multi-level modeling on this level [36][37][38], which will be discussed later in this paper.…”

“…Multi-level modeling [36,37] is an approach to conceptual modeling with multi-level DSMLs and multi-level modeling in general. This idea is based on several hierarchical levels, where an individual modeling environment on a specific level is created according to the sequence of previous (meta) models.…”