2009 ICSE Workshop on Comparison and Versioning of Software Models 2009
DOI: 10.1109/cvsm.2009.5071716
|View full text |Cite
|
Sign up to set email alerts
|

History-based merging of models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
5
3
1

Relationship

1
8

Authors

Journals

citations
Cited by 15 publications
(5 citation statements)
references
References 5 publications
0
5
0
Order By: Relevance
“…For instance, Gorek and Kelter [25] present means for matching sub-models in an early project phase. Other approaches, e.g., published by Wenzel et al [26] trace model elements through different versions of models, or, published by Schmidt et al [27], apply historybased merging of models.…”
Section: Related Workmentioning
confidence: 99%
“…For instance, Gorek and Kelter [25] present means for matching sub-models in an early project phase. Other approaches, e.g., published by Wenzel et al [26] trace model elements through different versions of models, or, published by Schmidt et al [27], apply historybased merging of models.…”
Section: Related Workmentioning
confidence: 99%
“…Other operation-based approaches for models have been presented in [20,22], but no dedicated reordering strategies have been discussed. In [21], the authors mention that finding an appropriate sequence for unifying the changes of two parallel change sets is an optimization problem, but they based their approach on manual conflict resolution during the merge process.…”
Section: Related Workmentioning
confidence: 98%
“…It is also possible to import own models (Mattsson et al, 1998;Pietruszka, 2014). The user-friendly graphical design of these tools makes it easy to use (Schmidt et al, 2009). Nevertheless, the user needs a good knowledge to build manually the system and use effectively one of these tools.…”
Section: Separating and Combining Modelsmentioning
confidence: 99%