Model synchronization as a problem of maximizing model dependencies

Authors:
Igor Ivkovic;Kostas Kontogiannis
Affiliations:
University of Waterloo, Waterloo, Canada;Technical University of Crete, Chania, Greece
Venue:
OOPSLA '04 Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Year:
2004

Citing 3
Cited 0

MDA Explained: The Model Driven Architecture: Practice and Promise

MDA Explained: The Model Driven Architecture: Practice and Promise
Heterogeneous view integration and its automation

Heterogeneous view integration and its automation
Tracing Evolution Changes of Software Artifacts through Model Synchronization

ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance

Quantified Score

Hi-index	0.00

Visualization

Abstract

During the course of its evolution, software is modified through models at different levels of abstraction, from the requirements specification to source code. To enable systematic development and maintenance, related models need to be kept synchronized. In order to establish and maintain consistency, we need to precisely define what it means for two models to be synchronized. In this paper, we present our view of model synchronization as a problem of maximizing model dependencies. Our conceptual view of software models is as graphs, and model transformations are viewed in terms of basic graph transformations such as node insertions and deletions. Based on this view, a set of transformations applied to one model is traced and propagated to the other by choosing, from a set of possible transformation paths, a path that maximizes underlying model dependencies.