BD is very likely to have a dependency on VO, not association. In BD, VO usually appears (or should appear) as a method parameter, return type, or just as a local variable. These are dependency. An association means a class has a structural relationship e.g. attribute.
Originally posted by Eduardo Rodrigues: If I put the VO�s showing the dependendy then my component diagram will be a confusion!
That's the point. UML diagrams should help to communicate a design or a solution and not make it more incomprehensible.
The same goes for utility classes, like logger classes and so on. Every other class needs it and has a dependency on it. But that's obvious and doesn't need to be communicated via a dependency in a class diagram.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop