Abstract: Certain example embodiments described herein relate to interactive model merging systems and/or methods and, more particularly, to using basic information obtained during merging to help a user resolve high-level merge conflicts. In certain example embodiments, instead of leaving it to the user to resolve the merge conflicts on the level of the atomic elements (e.g., objects and connections with a non-empty merge state), the recognition of high-level merge conflicts may help capture the semantics of the differences between the models being merged on a larger scale (e.g., covering a possibly very large number of model elements in one conflict) and/or also may generally help allow the user to resolve them easily and quickly within a reduced number of operation. The high-level merge conflicts may be resolvable at their high levels or decomposed and resolved at a lower level depending, in part, on the type of conflict involved.

Abstract: Certain example embodiments relate to selective change propagation techniques for supporting partial roundtrips in model-to-model transformations. In certain example embodiments, enablement checking is performed to determine whether a propagation operation can be performed for an object. If the object passes enablement checking, the propagation is executed by, for example, creating the object(s) in a business-oriented (e.g., EPC) model; updating relevant internal attributes of technical (e.g., BPMN) objects that allow for the successful merge; optionally correcting user-introduced errors in the technical model; and properly connecting the pulled-up objects with their surroundings. The connecting is performed so that the objects advantageously appear as if the current business-oriented model was used for the merge. According to certain example embodiments, the connecting may be deterministic, e.g., such that the result will be the same regardless of order or sequence in which the propagations are made.

Abstract: Certain example embodiments relate to selective change propagation techniques for supporting partial roundtrips in model-to-model transformations. In certain example embodiments, enablement checking is performed to determine whether a propagation operation can be performed for an object. If the object passes enablement checking, the propagation is executed by, for example, creating the object(s) in a business-oriented (e.g., EPC) model; updating relevant internal attributes of technical (e.g., BPMN) objects that allow for the successful merge; optionally correcting user-introduced errors in the technical model; and properly connecting the pulled-up objects with their surroundings. The connecting is performed so that the objects advantageously appear as if the current business-oriented model was used for the merge. According to certain example embodiments, the connecting may be deterministic, e.g., such that the result will be the same regardless of order or sequence in which the propagations are made.

Abstract: Certain example embodiments described herein relate to interactive model merging systems and/or methods and, more particularly, to using basic information obtained during merging to help a user resolve high-level merge conflicts. In certain example embodiments, instead of leaving it to the user to resolve the merge conflicts on the level of the atomic elements (e.g., objects and connections with a non-empty merge state), the recognition of high-level merge conflicts may help capture the semantics of the differences between the models being merged on a larger scale (e.g., covering a possibly very large number of model elements in one conflict) and/or also may generally help allow the user to resolve them easily and quickly within a reduced number of operation. The high-level merge conflicts may be resolvable at their high levels or decomposed and resolved at a lower level depending, in part, on the type of conflict involved.