Avoiding Unnecessary Information Loss: Correct and Efficient Model Synchronization Based on Triple Graph Grammars

Commutative Event Sourcing vs. Triple Graph Grammars

“…This section revisits the work of Fritsche et al [9]. The running example of [9] and of this paper is the synchronisation of Java package and Java class models with JavaDoc folders and files.…”

“…This section revisits the work of Fritsche et al [9]. The running example of [9] and of this paper is the synchronisation of Java package and Java class models with JavaDoc folders and files. Figure 1 shows the class diagrams for the two models as used in our implementation of this example.…”

“…In addition, a JavaPackage may have many classes of type JavaClass. Our class model extends the example from [9] with id attributes and with a vTag attribute. The latter will be used to discuss some editing or merge conflicts that are not handled by [9].…”

“…Our class model extends the example from [9] with id attributes and with a vTag attribute. The latter will be used to discuss some editing or merge conflicts that are not handled by [9]. The id attributes are used for referencing across tools.…”

“…the effort for model synchronisation is proportional to the model change performed. In [9] Fritsche et al present recent advances in achieving incremental model synchronisation.…”