I'm studying Craig Larman's "Applying uml and Patterns" (third ed.)
reading at the book it seems (16.6) that Operations and Methods in a
Class diagram are something different but it's not explained what's the
difference.
I always thought they were the same thing.
Do someone knows what's the difference?
thanx alot
Giulio
ps. I'm sorry if this question is not in the right newsgroup, I didn't
know any better one.
Michael G - 11 Sep 2005 19:17 GMT
> I'm studying Craig Larman's "Applying uml and Patterns" (third ed.)
> reading at the book it seems (16.6) that Operations and Methods in a Class
[quoted text clipped - 6 lines]
> thanx alot
> Giulio
I don't have the third edition but am looking at page 186-7 of the
second edition. In this section he states how the *UML defines* operations
and methods. He is not referring to Java or an other programming language.
So in the UML an *operation* is defined as an abstraction (much like an
interface in Java) and a *method* is defined as the implementation of the
abstraction.
operation in the UML
public void setSomething(Something s);
method in the UML
public void setSomething(Something s)
{
this.something = s;
}
If you aren't satisfied with this response or from this group. You might try
comp.object.
Mike
Giulio - 11 Sep 2005 21:31 GMT
thanx it's ok
Jubril - 25 Jan 2006 00:45 GMT
an operation in a programming language can mean the interaction of many
Methods. To calculate the roots of a Quadratic equation which is an
operation, one might need to call several methods like
calculate Square root()
calculate firstroot()
calculate second root()
> thanx it's ok