Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Questions on Component Diagram

 
Rahul Mishra
Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Is it fair to show some common framework components in 'Component Diagram' even though we dont show them in class/sequence diagram?

Such components might be responsible for security,exception handling,logging

Your views?


Regards


 
wolfgang unger
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think it's ok.
components like persistence, security, java mail service with stereotypes <<util>> or <<infrastructre>> make sense in the component diagram.
of course they shouldn't be in the class diagram.
 
Rahul Mishra
Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any thoughts on how to link these infrastructure/utility components to the main components -

Because a component diagram lets me link components to components..linking every application component to a infrastucture component is clumsy..so can we just leave it hanging in there and put something in notes?


Your views?
 
wolfgang unger
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
so can we just leave it hanging in there and put something in notes?

your components/classes will use them, right? thats why you want to show them in the diagram.
so simply draw an use-association from you component to e.g. <<infrastructure>> persistence
 
Rahul Mishra
Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you think about it, infrastructure/utility components like security, exception handling need to be connected with multiple application components.

This essentially clutters a diagram, hence the premise of my question.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, but you can put them in another diagram or a separate part of the diagram. Any real world project isn't going to be able to show all classes in the same diagram. That's why we use views.
 
wolfgang unger
Greenhorn
Posts: 28
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't think you will need so many of these boxes.
If you use JPA you can draw a box for persistence/jpa. it is used by your components. itself it will connect a <<database>>SuD-Schema box (or <<system>> database).
You may use security if required. Maybe Java-MailService. What else? Can't be so much more.
You won't show ExceptionHandling in the component diagram! I wouldn't even show it in the class diagram. I don't think it's necessary to create an Error/Exception Class Hierarchy for the assignment.

 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jeanne Boyarsky wrote:Yes, but you can put them in another diagram or a separate part of the diagram. Any real world project isn't going to be able to show all classes in the same diagram. That's why we use views.

To clarify - I missed the fact we were talking about a component diagram. I would include them in a class diagram, but not a component diagram.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic