This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Component diagram - depicting dependency Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Component diagram - depicting dependency" Watch "Component diagram - depicting dependency" New topic

Component diagram - depicting dependency

Shruti Verma

Joined: Dec 18, 2011
Posts: 8
I have a very simple question about depicting dependency between components and between layers in component diagram -

Using bubble and socket


using <<uses>> stereotype with a dependency association (Cade's way)?
Sadanandam Kurapati
Ranch Hand

Joined: Sep 09, 2011
Posts: 78

For dependency between components, I used Cade's way <<uses>>.


Shashi Kulkarni

Joined: May 29, 2011
Posts: 26

I second Sadanand here. I also followed the Cade's way and used <<uses>> for showing the dependency between components.

SCJP, OCMJEA, PMP, Brainbench certified OO Concepts, Brainbench certified OO Design Patterns, Brainbench certified EJB 3
Vijaykumar Dixit
Ranch Hand

Joined: Jul 04, 2011
Posts: 32

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.
It is sorta covered in the JavaRanch Style Guide.
subject: Component diagram - depicting dependency
It's not a secret anymore!