Method and Operation in EA

[qwerty]

I'm not expecting a fix but rather a confirmation:

[highlight]Help:[/highlight]

Method class: A method represents a UML operation.

Behavior: Some further explanatory behavior notes (for example, pseudocode).

[highlight]Superstructures:[/highlight]

...an operation owned by a class may have a related method that defines its detailed behavior...

So in EA an UML operation is called method and a UML method is called behavior (as attribute of an EA method). Correct?

q.

[Geert Bellekens]

More or less, it depends where you look.

If you look int he GUI then you see the term Operation(s) alongside Attributes (as it should).
In the database it is also called operation (t_operation)

But in the API it is called Method... too bad, we almost got a consistent set of names.

Geert

PS. I wonder wat Paolo has to say about something that is almost consistent  

[qwerty]

He'll most likely chip in  

I tried to get a consistent wording in my books (since I got messed up while using the EA wording and then got to re-think about it after the recent (LinkIn, SO?) discussion; you remember?). I probably have to add a few words in the preface.

q.

[Sunshine]

If some of you remember UML was a combination of Rumbaugh, Booch and Jacobson approaches which had their own terminology. Just dusted off the book from Rumbaugh which defines a method as the implementation of a operation. I understand UML carried on with that definition. Thus you can have a multiple methods that implement an operation in a class hierarchy and hence end up with polymorphism.
Got to say I tried looking up method definition in the UML standard 2.5 - interesting how they've made it almost incomprehensible without any clear definition. No wonder folk get confused. Just saying there is a case for plain English.