Domain-specific model differencing in visual concrete syntax
summary
Automatic derivation produces a diff metamodel from an existing metamodel and reuses its concrete syntax to display differences; implementation uses EMF Compare, Sirius/Obeo Designer and Git commit histories. A rule editor is generated so engineers write pattern-based semantic-diff rules that collapse low-level changes into domain events. On an Arduino Designer corpus a refactor reduced 20 classes and 22 associations to 1 class and 2 associations, semantic patterns recur across commits, and the pipeline runs end-to-end.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:21Domain-specific language engineering
- 2:09Text-based model comparison
- 16:24Where do semantic diff rules come from?
- 17:50Validation
- 18:44Case study. Arduino Designer
- 21:39Future work
- 23:00Conclusion
related talks
29mData Diffing Based Software Architecture Patterns
21mAconite: Towards Generating Sirius-Based Graphical Editors from Annotated Metamodels
01h 00mSemantic Driven Modeling in distributed systems
35mThe holy war of modeling notations - what fits best and why?
26mTowards Efficient Model Comparison Using Automated Program Rewriting
47mDomain driven redesign
39mDiagrams as Code 2.0
14mAutomating the Synthesis of Recommender Systems for Modelling Languages