• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II - struggling with component diagram

 
Steven De Groote
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

from previous experience and habit, I tend to make a giant class diagram, and so I did, but it seems that I'm going to split that off, as that also contains my beans, system lookups, pattern implementations etc. Back in my UML 1.1 days, people were hardly busy with component diagrams (or at least those who I learnt from weren't...

I am wondering though... an EJB in a component diagram, how do you model that exactly? If you have an OrderBean, would that mean that every method (which is an action obviously) is to be modelled as a component provided interface?


Thanks,
Steven
 
deepak adlakha
Ranch Hand
Posts: 325
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is what i did.

I showed all component(JSP/ EJB..and more) in component diagram, nothing specific to method level details. Only a component talking to another component, very high level.
 
Steven De Groote
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
deepak adlakha wrote:This is what i did.

I showed all component(JSP/ EJB..and more) in component diagram, nothing specific to method level details. Only a component talking to another component, very high level.

You didn't show any interfaces in your diagram then? (like with the lollypop)
I thought that would be a requirement as I read that "a component provides one or more interfaces that other components can use to interact with it".
 
deepak adlakha
Ranch Hand
Posts: 325
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Wherever interface was available in my design, i use interface instead of implementation in component diagram. Like in case of JSP, no interface is available, so i used something else.
 
P Das
Ranch Hand
Posts: 123
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
my suggestion to you: do not break up your class diagram as doing so may attract penalty for "bad fragmentation" although it may seem against intuition.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic