Deferring addition of implemented interface method

[Emilio]

EA 7.5

The subject line is not long enough for a proper description....

When one creates a class in the diagram and draws a Generalization or Realization association to a parent class/interface EA shows a dialog with "Methods to override/implement".

Now the question here is, should one only add them IF one is going to modify the behaviour (override)? or do they get automatically generated during code generation in which case there is less cluttering in a diagram because one can already see WHAT it is implementing.

My other question here is... when the parent interface or class is added an method that can be overriden (or implemented) what would happen? Apparently EA has no way to allow the user that deferred this action to add these at a later time. You either have to retype the whole thing again or drop the relationship and draw it again.

IMHO there should be an option in the context menu to pop up the list of methods to implement/override which already takes into consideration which of those have already been implemented.

[Geert Bellekens]

Doesn't Ctrl-O show you this dialog?

I also think you should make the distinction between abstract/concrete operations.
Abstract operation always have to be implemented by a concrete subclass.
Since by definition all operations on an interface are abstract, all these operation have to be implemented by the concrete class realizing the interface.
This is different when the realizing class/subclass is abstract. In that case you don't have to repeat the abstract operations on the abstract class as they are already inherited by this class. So you only show the concrete operations on this class and the own defined abstract operations.

Geert

[«Midnight»]

...
The subject line is not long enough for a proper description....
...

I submitted a bug report or feature request regarding increasing the subject length.

The answer was No.