Consistency Control for Model Versions in Evolving Model-Driven Software Product Lines

Schröpfer, Johannes; Schwägerl, Felix; Westfechtel, Bernhard

doi:10.1109/models-c.2019.00043

Cited by 3 publications

(3 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the merge of two versions, two different indices for the features with the same value arise conflict since the feature values cannot be represented with both indices in the merged version. Although most of the modeling languages, e. g., EMF models, allow specifying ordered features, only 20.3 % (14 of 69) of the approaches (e. g., A25 [87], A37 [106], A42 [113]) in our study support conflicts resulting from ordered features. We also noticed that only three approaches (i. e., A01 [47], A05 [55], and A42 [113]) are fully implemented, indicating the need for more empirical works.…”

Section: Support Of Ordered Featuresmentioning

confidence: 69%

“…Although most of the modeling languages, e. g., EMF models, allow specifying ordered features, only 20.3 % (14 of 69) of the approaches (e. g., A25 [87], A37 [106], A42 [113]) in our study support conflicts resulting from ordered features. We also noticed that only three approaches (i. e., A01 [47], A05 [55], and A42 [113]) are fully implemented, indicating the need for more empirical works.…”

Section: Support Of Ordered Featuresmentioning

confidence: 69%

“…-Domain-specific: The techniques presented only guarantee the general level of EMF models and do not address additional domain-specific constraints. For instance, A42 [113] can only ensure the generic consistency control such as well-formedness conditions for EMF models regardless of the underlying Ecore model. As other examples, A55 [126] only considers constraints and rules for consistency between a single element type, or A65 [143] is limited to the homogeneous model since they cannot define the merging process at a notational level.…”

Section: Map Limitations and Future Directionsmentioning

confidence: 99%

See 2 more Smart Citations

Conflict management techniques for model merging: a systematic mapping review

2022

View full text Add to dashboard Cite

Model merging conflicts occur when different stakeholders aim to integrate their contradicting changes that are applied concurrently to update software models. We conduct an extensive systematic mapping study on conflict management techniques and relevant collaboration attributes to the versioning and merging models from 2001 to the middle of 2021. This study follows the standard guidelines within the software engineering domain. We analyzed a total of 105 articles extracted from an initial pool of more than 1800 articles to infer a taxonomy for conflict management techniques. We use this taxonomy to classify existing approaches to understand characteristics, shortcomings, and challenges on conflict management techniques in merging models. It also provides a solid foundation for future work in this area. We show that syntactic conflicts are the most studied type and that the top three popular conflict detection techniques are constraint violation, change overlapping, and pattern matching. We observe the lack of a comprehensive state-of-theart comparison between academic or industrial tools, as well as the need for real-world case studies. Finally, we show that recent trends have focused on online collaboration, where teams of stakeholders work on large-scale models.

show abstract