Representation of overloaded methods in UML

Question

I am trying to create a UML diagram representing some Java code.

In the class, I have a method that is overloaded.

As far as I know, parameters for methods are not shown in UML diagrams.

How can I imagine method overloading in UML?

Thanks.

Answer 1

The subclass defines the method with the same signature as the method you want to override, and add a note {redefines} to the method. For example:

+doSomething(p:AThing):int{redefines} 

This means that the doSomething () method overrides the method in the superclass. And yes, the parameters for the methods are shown in the diagrams. As in the example, p is an AThing type parameter.

Answer 2

Speaking of overloading - for example, in your class you have more methods with the same name but with a different signature (parameters, perhaps the return value depending on the address language ...), you should provide a signature. UML does not indicate that you cannot have method parameters.

Answer 3

Check the display options for the entire chart or individual class / interface. Most UML tools have display options showing a list of method parameters.

Answer 4

You don't say your tool and UML diagram (I think the diagram class), but you have 2 ways:

• You can write a note about this method;
• You can use the stereotype keyword that spells <overloaded → in this method;

Answer 5

Most of the answers above are correct given a specific question. Alepucio, Vincent and bmatthews68 have answers that make sense in context.

** If the question is about overriding the superclass method with the same signature as overriding, this is the correct definition. If it is overloaded with the fact that you create the same method that takes different arguments, then I don’t think that this can be modeled structurally, you can show it using a sequence diagram, for example, a behavioral one, but not really.

So + doSomething (p: AThing): int {redefines} is correct, as Vincent did.

** If your problem / question concerns parameters that do not appear visually on the chart, which is usually a parameter in most UML tools.

** If you want to make it even clearer what you are doing, use the <> keyword, also note that the keyword is not a stereotype, as it is not part of the metamodel.