2019
DOI: 10.1049/iet-sen.2018.5104
|View full text |Cite
|
Sign up to set email alerts
|

UML2Merge: a UML extension for model merging

Abstract: Model merging plays a chief role in many software engineering activities, e.g. evolving Unified Modelling Language (UML) models for adding new features. Software developers may evolve UML models using merge relationships. However, given the growing heterogeneity of merge strategies and the UML limitations for expressing merge relationship, it is particularly challenging for them to specify merge relationships. Consequently, developers, end up expressing improperly merge relationships. Today, the UML can neithe… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 8 publications
(6 citation statements)
references
References 29 publications
0
6
0
Order By: Relevance
“…In addition to the above methods, the following is the most recent work on merging class diagrams; they were not included in our comparison. The approach in [38] defines the semantics of the merging relationship between UML packages and the order in which multiple merge relationships are executed. The approach extends the UML meta model, which is a drawback.…”
Section: Comparison With Other Methodsmentioning
confidence: 99%
“…In addition to the above methods, the following is the most recent work on merging class diagrams; they were not included in our comparison. The approach in [38] defines the semantics of the merging relationship between UML packages and the order in which multiple merge relationships are executed. The approach extends the UML meta model, which is a drawback.…”
Section: Comparison With Other Methodsmentioning
confidence: 99%
“…-Visualization: Limitation on the graphical aspect and the need to visualize the conflict representation. For instance, A51 [122] reports lack of proper support to visualize conflicts in the graphical modeling interfaces. Moreover, A22 [79] specifies the need to represent conflicts, which has paramount importance for usability reasons.…”
Section: Map Limitations and Future Directionsmentioning
confidence: 99%
“…They [32] have also presented the multi‐view collaboration method using knowledge‐base and shown a research demonstrator use‐case, still the method works in model level. As many approaches are developed for software engineering like [33], Wolfenstetter et al [34] introduce a software tool called TRAILS (standing for traceability, integration, and life‐cycle management support) which aims to convert existing information from different domain‐specific model into a uniform format by defining the relationship between the metamodels like Link model. Similarly, correspondence and consistency rules can be defined for a set of metamodels of the targets for flexible views in virtual single underlying metamodel (VSUMM) suggested by Kramer et al [35].…”
Section: State Of the Artmentioning
confidence: 99%