Combining Versioning and Metamodel Evolution in the ChronoSphere Model Repository

Haeusler, Martin; Trojer, Thomas; Kessler, Johannes; Farwick, Matthias; Nowakowski, Emmanuel; Breu, Ruth

doi:10.1007/978-3-319-73117-9_11

Cited by 4 publications

(6 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Tracking the changes of a model has already been studied in the literature (e.g. via model versioning [19] or filmstrip models [22]). However, to produce explanations about the system from those changes, their reasons (i.e.…”

Section: Data Representationmentioning

confidence: 99%

Towards automated provenance collection for runtime models to record system history

Reynolds

García-Domínguez

Bencomo

2020

Proceedings of the 12th System Analysis and Modelling Conference

View full text Add to dashboard Cite

In highly dynamic environments, systems are expected to make decisions on the fly based on their observations that are bound to be partial. As such, the reasons for its runtime behaviour may be difficult to understand. In these cases, accountability is crucial, and decisions by the system need to be traceable. Logging is essential to support explanations of behaviour, but it poses challenges. Concerns about analysing massive logs have motivated the introduction of structured logging, however, knowing what to log and which details to include is still a challenge. Structured logs still do not necessarily relate events to each other, or indicate time intervals. We argue that logging changes to a runtime model in a provenance graph can mitigate some of these problems. The runtime model keeps only relevant details, therefore reducing the volume of the logs, while the provenance graph records causal connections between the changes and the activities performed by the agents in the system that have introduced them. In this paper, we demonstrate a first version towards a reusable infrastructure for the automated construction of such a provenance graph. We apply it to a multithreaded traffic simulation case study, with multiple concurrent agents managing different parts of the simulation. We show how the provenance graphs can support validating the system behaviour, and how a seeded fault is reflected in the provenance graphs. CCS CONCEPTS • Software and its engineering → System modeling languages; Integration frameworks; Model-driven software engineering.

show abstract

Section: Data Representationmentioning

confidence: 99%

Towards automated provenance collection for runtime models to record system history

Reynolds

García-Domínguez

Bencomo

2020

Proceedings of the 12th System Analysis and Modelling Conference

View full text Add to dashboard Cite

show abstract

“…An essential drawback of our solution is that, due to the versioned nature of our data, we cannot rely as much on dictionaries with O(1) access times (e.g., Hash Maps) as regular general-purpose graph databases, because of the temporal resolution steps that hap- Fig. 16 Conceptual ChronoSphere metamodel [28] pen on every navigation. Those steps have a complexity of O(log (n)), which also limits the scalability of our graph.…”

Section: Limitations and Drawbacksmentioning

confidence: 99%

“…It is possible 27 https://git.io/vxZl3. 28 https://git.io/vxZWp. We would like to emphasize that CDO offers several ways of executing queries.…”

Section: Performance Evaluationmentioning

confidence: 99%

“…ChronoSphere [28] Ecore Model Repository https://github.com/MartinHaeusler/chronos/tree/master/org.chronos.chronosphere similar means, we intend to integrate the Epsilon Object Language [42] as sub-expressions in our query framework. This will allow ChronoSphere to offer support for several different query languages within the same underlying engine.…”

Section: Outlook and Future Workmentioning

confidence: 99%

“…11. Sections 4 through 6 consist of a revised, updated and extended version of the content presented in our previous work, mainly [25,27,28]. The remaining sections (most notably 2, 7 and 8) have never been published before.…”

mentioning

confidence: 99%

See 2 more Smart Citations

ChronoSphere: a graph-based EMF model repository for IT landscape models

et al. 2019

Self Cite

View full text Add to dashboard Cite

IT Landscape models are representing the real-world IT infrastructure of a company. They include hardware assets such as physical servers and storage media, as well as virtual components like clusters, virtual machines and applications. These models are a critical source of information in numerous tasks, including planning, error detection and impact analysis. The responsible stakeholders often struggle to keep such a large and densely connected model up-to-date due to its inherent size and complexity, as well as due to the lack of proper tool support. Even though modeling techniques are very suitable for this domain, existing tools do not offer the required features, scalability or flexibility. In order to solve these challenges and meet the requirements that arise from this application domain, we combine domain-driven modeling concepts with scalable graphbased repository technology and a custom language for model-level queries. We analyze in detail how we synthesized these requirements from the application domain and how they relate to the features of our repository. We discuss the architecture of our solution which comprises the entire data management stack, including transactions, queries, versioned persistence and metamodel evolution. Finally, we evaluate our approach in a case study where our open-source repository implementation is employed in a production environment in an industrial context, as well as in a comparative benchmark with an existing state-of-the-art solution. Keywords Model-driven engineering • Model repositories • Versioning • Graph database • IT landscape 1 Introduction Model-driven engineering (MDE) is a discipline that aims at improving the processes, workflows and products of exist-Communicated by Dr. Ana Moreira.

show abstract

Cronista: A multi-database automated provenance collection system for runtime-models

Reynolds

García-Domínguez

Bencomo

2022

Information and Software Technology

View full text Add to dashboard Cite

Combining Versioning and Metamodel Evolution in the ChronoSphere Model Repository

Cited by 4 publications

References 21 publications

Towards automated provenance collection for runtime models to record system history

Towards automated provenance collection for runtime models to record system history

ChronoSphere: a graph-based EMF model repository for IT landscape models

Cronista: A multi-database automated provenance collection system for runtime-models

Contact Info

Product

Resources

About