I have a project where class Foo has a member function which takes class FooParam as a parameter. Now I want to draw a UML class diagram representing the relationship between class Foo and FooParam.
From the options on the table, inheritance, implementation, aggregation and composition are automatically excluded. Thus, the options that are left are association and dependency, but to my eyes none of them fits quite right.
Given the options, how exactly do we model method parameters in class diagrams?


FooParamin your example) can be expressed textually in a class diagram. If you are not happy with this, you can add a dependency arrow from theFooclass to theFooParamclass.