Examples of how Rhapsody DiffMerge handles renamed elements

The following examples show you various scenarios of how Rhapsody DiffMerge handles renamed elements.

Example 1: Element is renamed

The following figure shows a comparison that found a match by element ID when a name match could not be found. This is the default method used by Rhapsody DiffMerge. As you can see, the Dishwasher class has been renamed to NewDishwasher. The difference report shows the change as a trivial diff.

Comparison of found match by element ID when name match could not be found

The following figure shows a comparison by name of element only. As you can see, the renamed class (NewDishwasher, as shownin the previous figure) does not appear in the Right Value column in this comparison method. Notice that the difference report reports that the unit (Dishwasher) has been deleted, which is untrue. As you can see from the previous figure, the class was only renamed.

Comparison by name of element only

Example 2: More than one element is renamed

The following figure shows a comparison where more than one element has been renamed. In addition, nested elements have been renamed.

Comparison where more than one element has been renamed

Example 3: Element is renamed and type is changed

The following figure shows a comparison that found matches by element IDs where the MyOriginalObject element was renamed to MyObjectBecameABlock, and then was converted into a block. Notice that Rhapsody DiffMerge reports two different elements as before.

Comparison that found matches by element IDs