

Whether or not Papyrus respects the metaclass hierarchy is irrelevant to this question of changing the nature of an element.

I feel like I must be missing something, since this functionality has been in every other UML tool I've used.

The question regarding classes and interfaces is that, since an interface is a model element that defines a set of operations that other model elements, such as classes, or components must implement, if I, let's say accidentally, realised half way through that the "class" I'd added and filled in was, in fact, totally abstract and was, therefore, an interface in those terms, why would there be a semantic issue in trying to convert the representation in Papyrus to an interface?Īlso, from the point of view of associations, since the "quick link" feature (or whatever it's called), when one end is connected to another element, pops up a list of 9 edges (a small subset of the total), if I select an Association Edge there, how can I constrain the association to be, for example, directional, Composite or Shared, and so on, since the "Properties" page of a plain Association Edge has very few options available.
