Triple Graph Grammars in the Large for Translating Satellite Procedures

Hermann, Frank; Gottmann, Susann; Nachtigall, Nico; Ehrig, Hartmut; Braatz, Benjamin; Morelli, Gianluigi; Alain, Pierre; Engel, Thomas; Ermel, Claudia

doi:10.1007/978-3-319-08789-4_9

Cited by 12 publications

(7 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…ATL (Jouault and Kurtev, 2006) and QVT (Object Management Group, 2008) are examples of model transformation approaches, which automatically create the traces. Henshin (Arendt et al, 2010) allows transformation developers to manually add trace links, whereas the Triple Graph Grammar approach of Hermann et al (2014), which is based on Henshin, automatically creates trace links.…”

Section: State Of the Artmentioning

confidence: 99%

“…In the area of model transformations, Bidirectional Model Transformations like JTL (Cicchetti et al, 2010) and Triple Graph Grammars (TGG) (Hermann et al, 2014;Hildebrandt et al, 2013;Schürr, 1995) have been developed to transform between models. They enable the synchronization of different design aspects by re-creating one model from the other and, thus, ensuring consistency by construction.…”

Section: Consistency Between Other System Design Aspectsmentioning

confidence: 99%

See 1 more Smart Citation

Evolution of software in automated production systems: Challenges and research directions

Vogel‐Heuser

Fay

Schaefer

et al. 2015

Journal of Systems and Software

243

View full text Add to dashboard Cite

a b s t r a c tCoping with evolution in automated production systems implies a cross-disciplinary challenge along the system's life-cycle for variant-rich systems of high complexity. The authors from computer science and automation provide an interdisciplinary survey on challenges and state of the art in evolution of automated production systems. Selected challenges are illustrated on the case of a simple pick and place unit. In the first part of the paper, we discuss the development process of automated production systems as well as the different type of evolutions during the system's life-cycle on the case of a pick and place unit. In the second part, we survey the challenges associated with evolution in the different development phases and a couple of cross-cutting areas and review existing approaches addressing the challenges. We close with summarizing future research directions to address the challenges of evolution in automated production systems.

show abstract

Section: State Of the Artmentioning

confidence: 99%

Section: Consistency Between Other System Design Aspectsmentioning

confidence: 99%

Evolution of software in automated production systems: Challenges and research directions

Vogel‐Heuser

Fay

Schaefer

et al. 2015

Journal of Systems and Software

243

View full text Add to dashboard Cite

show abstract

“…The terminology of patterns differs between authors, and especially between the model transformation and graph transformation communities. For example, phasing (Sequential Composition) [51] is termed layering in graph transformation languages [94], [173], and one approach (retyping) for structural preservation is termed relabelling in GT [31]. Map Objects before Links is also known as Entities before Relations [166].…”

Section: A the Extent And Type Of Pattern Usagementioning

confidence: 99%

“…Positive results for the customisability achieved by the Factor Code Generation pattern is described in [71]. Efficiency improvements from Sequential Composition/layering are shown in [94]. Efficiency improvements from the use of Active Operations are shown in [113].…”

Section: B Benefits Of Mt Pattern Usementioning

confidence: 99%

A survey of model transformation design patterns in practice

Lano

Kolahdouz-Rahimi

Yassipour-Tehrani

et al. 2018

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…Concerning our example scenarios from industry automation; bx approaches have been applied in various other industrial domains: Hermann et al [23] report on using TGGs to translate satellite procedures, Blouin et al [4] demonstrate an incremental 7:23 synchronisation layer between textual and graphical editors, Giese et al [17] present a synchronisation solution for SysML and AUTOSAR models, while Cunha et al [7] propose a bidirectional transformation approach for model-driven spreadsheets. Using our description languages, such projects could provide their results, solution strategies, and lessons learnt in a uniform and comparable manner; this would enable the identification and reuse of further method patterns for consistency management.…”

Section: Related Workmentioning

confidence: 99%

Description Languages for Consistency Management Scenarios Based on Examples from the Industry Automation Domain

et al. 2018

View full text Add to dashboard Cite

To cope with the increasing complexity of developing and maintaining modern (software) systems, multiple abstractions (models) of the same system can be established and used to allow different domain experts to collaborate and contribute their respective expertise. This divide-and-conquer, model-based approach requires, however, support for a concurrent engineering process, i.e., providing a means of checking, restoring, and ensuring the consistency of all involved and concurrently maintained models. The task of providing such support is often referred to as consistency management.Although there exist various approaches to consistency management and numerous (industrial) case studies described in the literature on bidirectional transformations (bx), there is currently no uniform description of diverse but related industrial applications of model synchronisation and other forms of consistency management. This makes it challenging to detect similarities and differences related to requirements, constraints, applied techniques and tools. It is thus difficult to compare and transfer knowledge gained from (successful) projects to other bx approaches or even other bx tools for the same general approach.In this paper, therefore, we propose a description language for envisioned scenarios in the problem domain of consistency management, as well as a complementary description language for solution strategies in terms of method fragments and method patterns in the solution domain of Model-Driven Engineering (MDE). Our work is inspired by previous research in the bx and MDE communities, and is also based on our collective experience from over ten years of investigating a series of application scenarios in the industry automation section together with Siemens AG as an industrial partner.We use our proposed description languages to discuss a series of application scenarios that are diverse but all require varying forms of support for consistency management. By using a common notation and focusing only on aspects directly related to consistency management, we are able to abstract from project-specific details and uniformly describe how consistency management is required and can be currently supported in the industry automation sector. Based on this formal and macroscopic view of the projects, we provide a systematic discussion of our experience and results applying Triple Graph Grammars (TGGs) as a concrete bx approach in the industry automation domain. ACM CCS 2012 1 Introduction and MotivationThe development and maintenance of increasingly complex software systems often requires a suitable decomposition of the system into multiple abstractions (models), which can be concurrently maintained by experts in their respective domains. Such a concurrent engineering process can be well supported by model-based approaches and techniques, especially approaches to ensure that the consistency of all related models, representing views of the same system, can be maintained via suitable change propagation and synchronisation. Numerous, diver...

show abstract

Triple Graph Grammars in the Large for Translating Satellite Procedures

Cited by 12 publications

References 19 publications

Evolution of software in automated production systems: Challenges and research directions

Evolution of software in automated production systems: Challenges and research directions

A survey of model transformation design patterns in practice

Description Languages for Consistency Management Scenarios Based on Examples from the Industry Automation Domain

Contact Info

Product

Resources

About