ICSE '91 Proceedings of the 13th international conference on Software engineering
The Pragmatics of Model-Driven Development
IEEE Software
Fixing Inconsistencies in UML Design Models
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Detecting model inconsistency through operation-based model construction
Proceedings of the 30th international conference on Software engineering
Incremental Detection of Model Inconsistencies Based on Model Operations
CAiSE '09 Proceedings of the 21st International Conference on Advanced Information Systems Engineering
Detecting and resolving model inconsistencies using transformation dependency analysis
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Transformation and validation with SWRL and OWL of ODM-based models
MEDI'12 Proceedings of the 2nd international conference on Model and Data Engineering
| Hi-index | 0.00 |
Keeping the consistency between design models is paramount in complex contexts. It turns out that the underlying Model Representation Strategy has an impact on the inconsistency detection activity. The Operation Based strategy represents models as the sequence of atomic editing actions that lead to its current state. Claims have beenmade about gains in time and space complexity and in versatility by using this kind of representation when compared to the traditional object based one. However, this hypothesis has never been tested in an industrial context before. In this paper, we detail our experience evaluating an Operation Based consistency engine (Praxis) when compared with a legacy system based on EMF. We evaluated a set of industrial models under inconsistency rules written in both Java (for EMF) and PraxisRules (the DSL - Domain Specific Language - for describing inconsistency rules in Praxis). Our results partially confirm the gains claimed by the Operation Based engines.