File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Component diagram - depicting dependency

 
Shruti Verma
Greenhorn
Posts: 8
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a very simple question about depicting dependency between components and between layers in component diagram -

Using bubble and socket

OR

using <<uses>> stereotype with a dependency association (Cade's way)?
 
Sadanandam Kurapati
Ranch Hand
Posts: 78
Eclipse IDE Java Tomcat Server
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For dependency between components, I used Cade's way <<uses>>.

Regards,
Sadanand
 
Shashi Kulkarni
Greenhorn
Posts: 26
Java
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I second Sadanand here. I also followed the Cade's way and used <<uses>> for showing the dependency between components.
 
Vijaykumar Dixit
Ranch Hand
Posts: 32
Eclipse IDE Java Tomcat Server
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Wherever possible component dependency should be shown by required and provided interfaces i.e. sockect and bubble notation. That makes a component isolated, replaceable and independent. I think <<uses>> notation is just a work around when we do not have clarity on specific interfaces within a component.

Just my opinion.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic