• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Component Diagrams

 
carl marais
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Searching the web and book shops there seems to be major lack of information on Component Diagrams. Anyone know a good resource?

carl
 
Tiger Scott
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Any good UML book should tell you about component diagrams.
UML User Guide by Grady Booch et. al has a chapter on Component diagrams.
The key is basicaly undersatnding what is component and how is different from a class.
HTH
Sanjay
[This message has been edited by Sanjay Bahal (edited November 26, 2001).]
 
carl marais
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks will try and find a copy.
 
Required Field
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Sanjay Bahal:
Any good UML book should tell you about component diagrams.
UML User Guide by Grady Booch et. al has a chapter on Component diagrams.
The key is basicaly undersatnding what is component and how is different from a class.
HTH
Sanjay


Can anyone please explain to me the difference between a Component and a Class ?

If EJBs are Components and are to be shown on the component diagram, then what do I show in the class diagram?

Also, is it necessary to draw out the internal structure of each EJB in a diagram? So for e.g. if I have a CustomerEJB (entity bean), then is it sufficient to just show it as a component on the component diagram (with a stereotype of <<entity>> OR do I have to also break down its internal structure (CustomerRemote, CustomerHome, CustomerBeanImpl, ejb-jar.xml etc)?

Isn't the internal structure of an EJB implicit here? I mean if I am designing a J2EE solution somethings are just plain implicit and should be assumed to be 'understood' by the readers/audience. That way I can effectively reduce clutter on my diagrams... Right/Wrong?

Thanks all!
[ February 20, 2006: Message edited by: Akshay Shrivastava ]
 
don brown (aka brownie brownie)
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A component is a deployable/replaceable unit of code. An EJB for instance. An EJB consists of several classes, as we all know. You don't need to show them all. Just name the bean and stereotype it to be <<Entity>> or whatever. You can show POJO's on a component diagram for things like ServiceLocator. This much you can glean from books.
 
Required Field
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by brownie brownie:
A component is a deployable/replaceable unit of code. An EJB for instance. An EJB consists of several classes, as we all know. You don't need to show them all. Just name the bean and stereotype it to be <<Entity>> or whatever. You can show POJO's on a component diagram for things like ServiceLocator. This much you can glean from books.


Thanks brownie brownie!
 
Parag Bharambe
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Suppose I have designed my domain model as entity bean. So do I need to show all my domain classes in my component diagram?

OR how can I show all domain classes in my compnent diagram?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic