• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

UML Version and Component Diagrame

 
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Gentlepeople,
What version of UML must our diagram conform to?

Also, due to lack of knowledge, I have a couple of questions regarding it - went throught this article hereUML 2 Component Diagram. It says a component can provide or require interfaces represented by a lollipop and a socket. If you look at the diagram, these two interfaces are linked by a placing the lollipop and socket next to each other. Also, they are linked by a dashed line? What does that mean? When one is required over the other?

Thanks.
BR
 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Brian,
I didn't use anything fancy (lollipop and socket), just basic features in Rational Rose will be enough, I think.
 
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Brian,

A major concept about the component diagram is that the components in the diagram interact with each other via clear and well-defined interfaces. These interfaces can be APIs, protocols, etc. Among classes the interaction is usually via APIs, but when the components represent an external system, the interface should be explicitly specified.

I use Jude which has the interface notation.

Now, the dashed line denotes a dependency while the lollipop and socket represent the interface. So, both are required when using an interface.

Regards,
Dan
 
Brian Smith
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Do you also show the PROTOCOL if used to communicate among components?
BR
 
Dan Drillich
Ranch Hand
Posts: 1183
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sure.
 
Brian Smith
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Changski,

Originally posted by Changski Tie Zheng Zhang:
Hi Brian,
I didn't use anything fancy (lollipop and socket), just basic features in Rational Rose will be enough, I think.



Ok, so if I don't use the lollipop and the socket, the remaining notation for component diagram are the dashed arrow and the solid arrow which I believe have the same semantic as in Class diagram ie, dependency and association. Nnow when do I use association vs dependency in Component Diagram?

Also, do you use a bi-directional association?

BR
[ November 08, 2006: Message edited by: Brian Smith ]
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Brian,

I download a community edition of visual paradigm for UML which has everything you need to complete the assignment. FYI, I have lollipops and sockets on my component diagram. As long as you have the well designed session beans. You shouldn't have any problem to come up with a ver good looking diagram.

Good luck!

CH
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic