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 about Composite Entity

 
Tony Tranquil
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am struggling with PART II now, thanks this forum, I've got alot VERY useful information here. I have some questions about Composite Entity.

1. if Component Diagram is pattern-concerned, should Composite Entity be shown on the Component Diagram?

2. in Sequence Diagram, if the Composite Entity's dependent objects are only POJO things, these objects will be shown with sterotype <<POJO>> or just shown as FlightVO-like things?

Thanks
 
I Roberts
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can only state what I actually did on my assignment but I did receive full marks on the Component diagram. Basically, I used the Composite Entity pattern for Entity EJBs that had relationships with other Entity EJBs and POJOs. On the Component diagram I only showed the actual Composite Entity, which is the actual component unit, while on the Sequence diagrams (I recieved full marks again) I showed a lower level. The difference was that a component is at a higher abstract level than an object, although an object itself can be a basic component, and while the Component diagram is specifically for components the Sequence diagram (in the exam context) is at a lower level of detail.

I hope this helps!
 
I Roberts
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I forgot to answer you question regarding stereotypes in Sequence diagrams. The UML tool I used didn't show stereotypes correctly so I didn't put them in. However, I do agree that there is nothing wrong with showing this information so long as it does not clutter the diagram. In my opinion, if they add value use them otherwise leave them out.
 
Tony Tranquil
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Robert for your input.

Do you use Value List Handler pattern? I am using this pattern in my design, but have quite same confusion in the component diagram. Should I put the handler thing in component diagram or just add a note and mention that there are some list handler used here?

Thanks again
 
I Roberts
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is very hard to answer your question without giving you too much indication on what I did exactly. However, in my opinion, I would have used the Value List Handler but would not have shown all the composition of the pattern within the Component diagram. The main decision is what are you trying to show in the Component diagram and do you need to show all the classes as components or are composition of classes defined as a component?

Unfortunately, in the real world you would never show a software system the size of the assignment in a single component diagram but a number of diagrams providing different views. Sun specifically ask for one diagram and therefore (against UML and architecture principles) the diagram becomes cluttered, busy, complex and not the best view of component relationships.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic