• Post Reply Bookmark Topic Watch Topic
  • New Topic

Part II: Dependencies in Component Diagram

 
Allexicus Kernikus
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just can't decide an the dependencies within my component diagram. Cade used nothing but <<uses>> stereotypes.

But in my opinion the dependencies should be the following:
- remote EJB calls: <<Reference>> (following the JSR-26 standard, which maps JEE elements to UML)
- Calls between classes (same container): <<uses>>
- Calls to external system (e.g. via SOAP or LDAP): <<call>>
- Access of DBs (e.g. JDBC): <<uses>>

What do you guys say? Cade has such a simplified version of all diagrams, that I just can't believe that such a design will let you pass...


 
Jeanne Boyarsky
author & internet detective
Sheriff
Posts: 36027
432
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All but two of mine are <<uses>>. I think you should go what makes sense for your design.
 
Anil Chowdary
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have used all <<uses>>, just like the example in the book. It worked for me. You may go ahead your specialized representations(if you believe it's necessary), it wont be harmful. But certainly keeping it simple doesn't necessarily mean that you lose marks. Clarity of the diagram is important.
 
Gravity is a harsh mistress. But this tiny ad is pretty easy to deal with:
the new thread boost feature: great for the advertiser and smooth for the coderanch user
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!