FRQ: merge elements

[angel-o-sphere]

Hi,

I often have the problem that I have two elements of same UML:type but with different names, which are in fact the same element.

They are probably in different packages because they got created by different persons.

I like to suggest a option to merge those two elements.

That means all usages of one or the other will be replaced by the new merged version.

Imagine a diagram with screen S and component A denoting that A realizes S and a second diagram with use case U and a component B denoting B realizes U.

Now I want to merge A and B to C and the two diagrams should now both get updated to display C instead of A or B and the new C should have all features, except name merged.

That means C links now to two artifacts: S and U.

The user has to pick a new name and a new package for C ... or you just take the oldes elements features and let the user move and rename it later.

Regards,
  angel'o'sphere

[jps]

I not only second this, but would love to see support for "Refactoring" in general.

In particular would be the ability to extract a super class from a set of methods in a given class.

[Bruno.Cossi]

I second this whole-heartedly.

[sargasso]

Just to link this to the previous expounding of this request.

http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=suggestions;action=display;num=1069178315;start=2#2

Bruce


p.s.  Have I mentioned multiple select recently?