View-based model-driven software development with ModelJoin

Bürger, Erik; Henss, Jörg; Küster, Martin; Kruse, Steffen; Happe, Jens

doi:10.1007/s10270-014-0413-5

Cited by 30 publications

(21 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, few model view approaches focus on integrating strongly interconnected models coming from different data sources. For instance, ModelJoin [7] proposes a DSL for querying different models and building a view as a result. However, it does not currently provide particular support for various model persistence backends (other than the EMF default ones).…”

Section: Related Workmentioning

confidence: 99%

Towards Scalable Model Views on Heterogeneous Model Resources

Brunelière

Kerchove

Daniel

et al. 2018

Proceedings of the 21th ACM/IEEE International Conference on Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

When engineering complex systems, models are used to represent various systems aspects. These models are often heterogeneous in terms of modeling language, provenance, number or scale. They can be notably managed by different persistence frameworks adapted to their nature. As a result, the information relevant to engineers is usually split into several interrelated models. To be useful in practice, these models need to be integrated together to provide global views over the system under study. Model view approaches have been proposed to tackle such an issue. They provide an unification mechanism to combine and query heterogeneous models in a transparent way. These views usually target specific engineering tasks such as system design, monitoring, evolution, etc. In our present context, the MegaM@Rt2 industrially-supported European initiative defines a set of large-scale use cases where model views can be beneficial for tracing runtime and design time data. However, existing model view solutions mostly rely on in-memory constructs and low-level modeling APIs that have not been designed to scale in the context of large models stored in different kinds of sources. This paper presents the current status of our work towards a general solution to efficiently support scalable model views on heterogeneous model resources. It describes our integration approach between model view and model persistence frameworks. This notably implies the refinement of the view framework for the construction of large views from multiple model storage solutions. This also requires to study how parts of queries can be computed on the contributing models rather than on the view. Our solution has been benchmarked on a practical large-scale use case from the MegaM@Rt2 project, implementing a runtime -design time feedback loop. The corresponding EMF-based tooling support and modeling resources are fully available online.• Software and its engineering → Model-driven software engineering; Abstraction, modeling and modularity; • Information systems → Database design and models;

show abstract

Section: Related Workmentioning

confidence: 99%

Towards Scalable Model Views on Heterogeneous Model Resources

Brunelière

Kerchove

Daniel

et al. 2018

Proceedings of the 21th ACM/IEEE International Conference on Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

show abstract

“…The prototypical implementation of the ModelJoin approach is joint work of the authors of the ModelJoin Tech Report [28] and [29]. The project is being developed as open source and can be obtained via the ModelJoin Homepage 2 .…”

Section: Methodsmentioning

confidence: 99%

“…The results of this case study have previously been published in [29]; the study has been conducted in cooperation with the authors of this publication.…”

Section: Empirical Studymentioning

confidence: 99%

“…The concepts and the language definition, which are presented in this section, have been published previously in [29], and are extended in the following subsections. The prototypical implementation of ModelJoin and its technical details are described in the ModelJoin technical report [28].…”

Section: Definition Of Flexible Views At Run-time Using Modeljoinmentioning

confidence: 99%

“…The Java objects that are created in the memory-based store can be serialised and persisted as files using a binary serialization format. In the course of the development of the ModelJoin prototype [29], an Ecore-based metamodel of the Sensor Framework result model and an XMI serialiser for instances of sensor framework data have been developed. If we see the development of the ModelJoin protoype as a part of the process of introducing VITRUVIUS in the component-based scenario, then this development is part of the responsibilities of the methodologist.…”

Section: Processmentioning

confidence: 99%

See 2 more Smart Citations

Flexible views for view-based model-driven development

Bürger¹

2013

Proceedings of the 18th International Doctoral Symposium on Components and Architecture

View full text Add to dashboard Cite

Modern software development faces growing size and complexity of the systems that are being developed. To cope with this complexity, several languages and modelling formalisms are used during the development of a system in order to describe it from various view points and at multiple levels of abstraction. These languages and modeling formalisms are specific to the domain of the system under development, to the paradigms that are followed, and to the developer tools being used. For example, in a component-based process, the software architecture may be defined using a component metamodel, while class diagrams are used for the object-oriented design of the system; performance and reliability models express the extra-functional properties; program code in a general-purpose programming language defines the execution semantics, and is used for the implementation of the system. Although all these artefacts follow different concepts and formalisms, they express the same system from various view points and can thus be understood as views on the system under development. The entirety of these views can be identified as a complete definition of the system. Although the usage of multiple formalisms offers the advantage that different developers can describe the system from different view points, and in languages and models that are specially designed for this purpose, it introduces the problem of fragmentation of information across heterogeneous artefacts in different formats, concepts, and languages. With increasing complexity of the systems, this makes navigation through the system description difficult for developers and other roles in the development process. Furthermore, since the concepts and formalisms are managed independently, they can share semantic overlaps, so that a piece of information about the system under i Abstract development can be expressed in several ways and contexts. For example, while a component model may be used to express the prescriptive software architecture of a system, the implementation in a general-purpose programming language also determines an implicit architecture of the system, which leads to redundancies in the system descriptions. The independent evolution of these artefacts can lead to inconsistencies, which cannot be identified automatically if the semantic correspondances between the artefacts are not modelled explicitly.View-based software development processes offer two fundamental principles of adressing this problem: While synthetic approaches integrate the information of heterogeneous models to form a complete system description, projective approaches introduce a common formalism in which all view points of the system can be represented, and generate the views from this central model. While the pure synthetic approach suffers from a quadratic increase of interdependencies between the view types, which become very numerous with a growing number of formalisms that have to be supported, the projective approach faces the problem of providing a common formalism that is ab...

show abstract

Ensuring safe and consistent coengineering of cyber‐physical production systems: A case study

Tröls

Mashkoor

Demuth

et al. 2020

J Software Evolu Process

View full text Add to dashboard Cite

In today's engineering projects, companies continuously have to adapt their systems to changing customers or dynamic market requirements. This requires a flexible, iterative development process in which different parts of the system under construction are built and updated concurrently. However, concurrent engineering becomes quite challenging in domains where different engineering artifacts from different disciplines come into play, such as safety‐critical cyber‐physical systems, where the involved engineering artifacts are quite heterogeneous in nature. In such systems, it is of utmost importance that different artifacts remain consistent in order to guarantee a correctly functioning end product. In this article, we discuss our experiences (with a leading company working in the areas of production automation and product processing) in maintaining the consistency between electrical models and the corresponding software controller, when both are subject to continuous changes. The article discusses how we let engineers describe the relationships between electrical models and the corresponding software controller code in the form of links and consistency rules. Additionally, we demonstrate that how our approach, through a process of continuous consistency checking, notifies engineers about the erroneous impact of their changes in various engineering artifacts.

show abstract

View-based model-driven software development with ModelJoin

Cited by 30 publications

References 34 publications

Towards Scalable Model Views on Heterogeneous Model Resources

Towards Scalable Model Views on Heterogeneous Model Resources

Flexible views for view-based model-driven development

Ensuring safe and consistent coengineering of cyber‐physical production systems: A case study

Contact Info

Product

Resources

About