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

Component Diagram conflicts

 
David Carel
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello all,
What's the right way to represent a component in a deployment diagram when parts of that component are divided on seperate tiers? Example: The PetStore Customer component has some parts that are used not just on the middle/application tier, but also in the web tier (AccountModel, for instance). How is a component like that represented on a deployment diagram when the nodes correspond to individual physical pieces of equipment -- show the Customer component on *both* tiers, or just on the middle, or something else?
Also, in the book "UML Components", the authors state that a component exists strictly in the context of a Component Standard (e.g., Enterprise JavaBeans, COM+). So, that would imply that we are supposed to put only EJBs/JSPs/Servlets on the diagram. However, I have heard of people putting "groups of classes" (like a DAO + VO for a certain entity that doesn't have an EJB representing it), the Swing client/jar, and an XML document. By the previous definition, these items seem out of place... or are they?
Thanks in advance for your input,
David
[ January 25, 2002: Message edited by: David Carel ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic