Enabling consistency in view-based system development — The Vitruvius approach

Klare, Heiko; Kramer, Max; Langhammer, Michael; Werle, Dominik; Bürger, Erik; Reussner, Ralf

doi:10.1016/j.jss.2020.110815

Cited by 36 publications

(13 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An execution strategy finds a new model assignment only by executing the transformations of the network, as more precisely defined by Klare et al [15,Definition 8]. If S(N, M ) = ⊥, we say that the strategy "resolves" N and M .…”

Section: Definition 6 a Universal Execution Strategy Determines An Omentioning

confidence: 99%

Finding a Universal Execution Strategy for Model Transformation Networks

Gleitze

Klare

Bürger

2021

Fundamental Approaches to Software Engineering

Self Cite

View full text Add to dashboard Cite

When using multiple models to describe a (software) system, one can use a network of model transformations to keep the models consistent after changes. No strategy exists, however, to orchestrate the execution of transformations if the network has an arbitrary topology. In this paper, we analyse how often and in which order transformations need to be executed. We argue why linear execution bounds are too restrictive to be useful in practice and prove that there is no upper bound for the number of necessary executions. To avoid non-termination, we propose a conservative strategy that makes execution failures easier to understand. These insights help developers and users of transformation networks to understand under which circumstances their networks can terminate. Additionally, the proposed strategy helps them to find the cause when a network cannot restore consistency.

show abstract

Section: Definition 6 a Universal Execution Strategy Determines An Omentioning

confidence: 99%

Finding a Universal Execution Strategy for Model Transformation Networks

Gleitze

Klare

Bürger

2021

Fundamental Approaches to Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Single-underlying models [16] combine multiple models into one single source of truth, thus enabling both multi-model consistency preservation and multi-view modeling. Meier, Werner, Klare, et al [20] compare different SUM-based approaches, examples are VITRUVIUS [21] and NAOMI [25]. We use the former for our approach.…”

Section: B Co-evolution Of Modelsmentioning

confidence: 99%

“…We plan on evaluating our approach with the Ecore-based VITRUVIUS framework [21]. VITRUVIUS combines models into a virtual single-underlying model (V-SUM) employing transformation networks.…”

Section: Planned Evaluationmentioning

confidence: 99%

See 1 more Smart Citation

Towards the Co-Evolution of Models and Artefacts of Industrial Tools Through External Views

Saglam

Kühn

2021

2021 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)

View full text Add to dashboard Cite

Modern software systems comprise multiple models. When these models are changed, interdependent models must be evolved accordingly. Manually managing this co-evolution of models is tedious and error-prone. Moreover, other interdependent artefacts, such as persisted states of industrial software applications, must co-evolve accordingly. Automated consistency preservation allows for efficiently managing the co-evolution of models. However, while state-of-the-art approaches operate delta-based, typical software applications persist changes statebased without conforming to explicit metamodels. Additionally, software applications may persist changes infrequently, even though interdependent models might be concurrently modified. As such, current approaches are insufficient for artefacts of industrial tools. To address these issues, we propose an approach for the co-evolution of models and artefacts of industrial tools by treating these artefacts as external views on the models.

show abstract

“…Models are means to manage information in highly complex systems in business modeling, in software engineering and many other fields. The solution to cope with complexity is often seen in the distribution and fragmentation of information between different models or views possibly in different modeling languages, thereby raising the issue of keeping the models consistent [1,13,37].…”

Section: Language Interleaving and Consistencymentioning

confidence: 99%

Formalizing the Four-layer Metamodeling Stack -- Potential and Benefits

Döller

2021

Preprint

View full text Add to dashboard Cite

Enterprise modeling deals with the increasing complexity of processes and systems by operationalizing model content and by linking complementary models and languages, thus amplifying the model-value beyond mere comprehensible pictures. To enable this amplification and turn models into computer-processable structures a comprehensive formalization is needed. This paper presents a generic formalism based on typed firstorder logic and provides a perspective on the potential and benefits arising for a variety of research issues in conceptual modeling. We define modeling languages as formal languages with a signature Σ -comprising object types, relation types, and attributes through types and function symbols -and a set of constraints. Three cases studies are included to show the effectiveness of the approach. Applying the formalism to the next level in the hierarchy of models we create M2FOL, a formal modeling language for metamodels. We show that M2FOL is self-describing and therefore complete the formalization of the full four-layer metamodeling stack. On the basis of our generic formalism applicable to arbitrary modeling languages we examine three current research topics -language interleaving & consistency, operations on models, and automatic translation of formalizations to platform-specific code -and how to approach them with the proposed formalism. This shows that the rich knowledge stack on formal languages in logic offers new tools for old problems.

show abstract

Enabling consistency in view-based system development — The Vitruvius approach

Cited by 36 publications

References 24 publications

Finding a Universal Execution Strategy for Model Transformation Networks

Finding a Universal Execution Strategy for Model Transformation Networks

Towards the Co-Evolution of Models and Artefacts of Industrial Tools Through External Views

Formalizing the Four-layer Metamodeling Stack -- Potential and Benefits

Contact Info

Product

Resources

About