Better Support for Inheritance/Generalization

[andrewd]

Currently when you "Generalize" a component or class from another you get the option copy all or some of the "Base" component/class members.  The problem is that it is a copy not a link.  If I change the name or parameters in the base component it is not reflected in the components that derived from the base.

This is  a problem for us because we need to separate the role of Architect and designer in our EA models.  The Architect defines the components and their interfaces, where as the designer specifies the internal behaivor.  We need to ensure that the designer does not modify the architecture (i.e. the interfaces and related info).  

We would like the architect to define base components/classes or even interface objects that could be locked by the architect.  The designers would derive from these objects and add internal member varaibles, functions as well as behavorial diagrams.  In order to manage change the base architectural object needs to be linked to the derived requirement otherwise we can not guarentee that the two match if changes are made to the architecture interfaces.

[Eve]

There has been a lot of discussion around here about if a rename in a superclass/interface should be automatically copied to child classes.

There hasn't been sufficient push to add an option for that behavior. I would imagine it should be possible using an add-in though.