Class diagram and Usage arrows

[Antonio Rafael Rodrigues]

Hello. I'm here again =]

The class diagram shown in the Cade's book has indications about the usage among the classes, some doted arrows with the <<uses>> stereotype.

I think it's is good on some levels, but sometimes it seems like be adding dificult without add value. Can I selectivelly omitted some of them, or I have to put all the <<uses>> indications in my class diagram.

Thanks

[Jeanne Boyarsky]

I put it in mine all over. I wouldn't in the real world, but I wasn't sure if they'd take off points for omitting it.

[Antonio Rafael Rodrigues]

Thanks for you reply Jeanne, I think I'm going by the same way.

[Mike Degteariov]

I really, really hope the reviewers of Part 2 assignments agreed with Martin Fowler:

http://martinfowler.com/bliki/DependencyAndAssociation.html

You don't want to show every dependency on a UML diagram - there are far too many. You need to be very selective and show only those that are important to whatever it is you are communicating.

I am not going to show every dependency. There are indeed far too many.

[Antonio Rafael Rodrigues]

Well, after I split my class diagram as you suggested in some topics ago, my class diagram is readable even with all the ref lines. But, as wisely detected by you, I lose the references between classes of different packages.
After that, I was thinking about how to indicate the relationships without arrows and I came to the conclusion that i could indicate references between EJBs by putting a reference as a field in the EJB that injects.

[Mike Degteariov]

Ji Antonio,

Humm, sounds interesting, but I do not think I understand how you achieve showing the dependencies in compliant way - could you provide more details, or probably some example ?

I could probably use it.

Thanks !

[Antonio Rafael Rodrigues]

Hello Mike.

I think that with options 2 or 3 we're still showing the use even if the used class TableDAO isn't visible in the current diagram (it is in another diagram).

Cheers.