Anatomy of a Visual Domain-Specific Language Project in an Industrial Context

Wienands, Christoph; Golm, Michael

doi:10.1007/978-3-642-04425-0_35

Cited by 8 publications

(6 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The requirement R3.5 was only partially fulfilled, because of the synchronization problems. Similar observations in GMF have been made in [29] during the implementation of a DSML for elevator controllers. This problem is common in non-orthogonal modeling languages, i.e., those that represent the same Figure 1.…”

Section: The Requirements Not or Partially Implemented Because Of Prosupporting

confidence: 74%

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

Godena

Lukman

Heričko

et al. 2015

ITC

View full text Add to dashboard Cite

Model-driven engineering (MDE) is a software-engineering paradigm that is being introduced into a growing number of domains. One of the most important success factors for a new MDE approach is the availability of the appropriate tool support for it. Although the literature discusses the development of support tools, only a few reports and analyses are available about the development of tool support for real-life modeling languages and MDE approaches. The goal of this paper is to fill this gap through an experience report about developing a tool-suite prototype for an MDE approach for the process control domain that is capable of supporting the development of real-life process control software. Before the work presented in this paper an initial prototype tool suite was already developed. However, it was not able to adequately support industry-scale projects. The paper starts with an analysis of the past development of this already-existing laboratory prototype and then moves on to a report about the development of the industrial prototype, which is influenced by the findings of the analysis. Then a comparison between the two prototypes is made and the lessons learned are described, which may be useful to practitioners who attempt to develop support tools for an MDE approach that are useful in practice. The most important lesson learned is that when developing tool support for complex modeling languages, the traditional development approach should not be easily rejected.

show abstract

Section: The Requirements Not or Partially Implemented Because Of Prosupporting

confidence: 74%

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

Godena

Lukman

Heričko

et al. 2015

ITC

View full text Add to dashboard Cite

show abstract

“…Polishing transformations may not have similar productivity results in terms of the number of model elements they produce/modify (for example the polishing transformation in Listing 1.3 takes 25 lines of code to create 3 and modify 2 elements), however in our experience the effort spent for construcing them quickly pays off as graphical editor development is a highly iterative process [2].…”

Section: Case Studymentioning

confidence: 95%

“…Unfortunately, in practice this wizard fails to yield useful results for anything beyond very simple metamodels [2] -and this is reasonable given how little can be generally inferred about the graphical syntax based on the abstract syntax alone. As a result, in practice these three models need to be hand-crafted using a set of very basic tree-based editors provided by GMF, and this is widely-recognized to be a laborious and error-prone process, particularly given the complexity of the metamodels these models conform to, and the lowlevel error messages that GMF produces if they are not configured in a valid way.…”

Section: Specifying the Graphical Syntax And Generating Code With Gmfmentioning

confidence: 99%

“…Given that implementing a simple graphical editor is typically one of the first steps attempted by most of the newcomers in MDE [2], the risk of giving up or forming a negative impression about the quality of the MDE tool-chain from their interaction with GMF is considerable. Moreover, even for seasoned MDE developers 5 , this predominately manual and repetitive process is clearly tedious.…”

Section: Specifying the Graphical Syntax And Generating Code With Gmfmentioning

confidence: 99%

“…However, the trade-off for power and flexibility is increased complexity. As discussed in the industrial experience report presented by Wienands and Golm [2], implementing a graphical editor for a modelling language using EMF and GMF is a loosely-guided and error prone process, mainly because it requires developers to hand craft and maintain a number of low-level, complex interconnected models. Increased complexity in conjunction with suboptimal tool support for creating and maintaining the required low-level models make implementing a graphical editor with GMF a painful experience, particularly for inexperienced developers.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Taming EMF and GMF Using Model Transformation

Kolovos

Rose

Abid

et al. 2010

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Abstract. EMF and GMF are powerful frameworks for implementing tool support for modelling languages in Eclipse. However, with power comes complexity; implementing a graphical editor for a modelling language using EMF and GMF requires developers to hand craft and maintain several low level-interconnected models through a loosely-guided, labour-intensive and error-prone process. In this paper we demonstrate how the application of model transformation techniques can help with taming the complexity of GMF and EMF and deliver significant productivity and quality benefits. In particular we demonstrate EuGENia, a widely-used tool that adopts a single-sourcing approach and advanced model transformation techniques for automatically producing and maintaining the low-level models required by EMF and GMF. We evaluate EuGENia through automated testing and substantial feedback from researchers and practitioners within the Eclipse modelling community.

show abstract

Building Models for Ubiquitous Application Development in a Model-Driven Engineering Approach

Vieira

Carvalho

2020

Special Topics in Multimedia, IoT and Web Technologies

View full text Add to dashboard Cite

Anatomy of a Visual Domain-Specific Language Project in an Industrial Context

Cited by 8 publications

References 4 publications

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

The Experience of Implementing Model-Driven Engineering Tools in the Process Control Domain

Taming EMF and GMF Using Model Transformation

Building Models for Ubiquitous Application Development in a Model-Driven Engineering Approach

Contact Info

Product

Resources

About