Component Diagram and Part 2

[Kumar Amit]

Hi Friends,
Do we need to show each Session Beans as separate component from corresponding entities in the component diagram? For example I have 3 session beans (Managers) and 3 entities. Do I have to show 6 separate components in the "business logic and persistence" tier on the component diagram unlike Mark cade's example where it shows SessionBean and entity bean as combined/single component.

Thanks
Amit

[Kumar Amit]

Also, which of the following should be shown in the component diagram:
1. JSF <<framework>> as a component
2. FacesServlet <<controller>>as a component
3. or none of the above

[Rajan Choudhary]

I am showing 2 boxes for 2 modules of JSP and then controller and all managed bean at the web tier along with important filters/listeners/handlers. I did not find anything else to be shown at that level. The sad part is repeatation of components/classes in class diagrams and component diagram. Is it an issue?

[Will Myers]

I am not going into that much detail, my class diagram looks similar to Cade's showing jsf pages and a controller talking to session beans, I have mentioned things like logging, exception handling, auditing, etc in my assumptions.

[Rajan Choudhary]

will myers wrote:I am not going into that much detail, my class diagram looks similar to Cade's showing jsf pages and a controller talking to session beans, I have mentioned things like logging, exception handling, auditing, etc in my assumptions.

True, but I don't know what else to show for getting a score of 40 points -

Everything is clear in class diagram and sequence diagrams so I see component diagram a complete duplication of classes/objects.

[Kumar Amit]

Rajan Choudhary wrote:I am showing 2 boxes for 2 modules of JSP and then controller and all managed bean at the web tier along with important filters/listeners/handlers. I did not find anything else to be shown at that level. The sad part is repeatation of components/classes in class diagrams and component diagram. Is it an issue?

Hi Rajan,
How are you showing your controller in the component diagram's web tier like <<framework>>Faces Servlet?

Are you showing generic filters in component diagram e.g AuditFilter(intercepting), LoginFilter(intercepting) or are they specific to some business logic of your system?

Are you showing these filters/listeners in class diagram as well?

[Rajan Choudhary]

I am showing just the names in a UML component icon which means that's a component. I already that, I have 75% duplication in class and component diagram but I don't know where to keep what? As cade's book says, I am showing JSPs in class diagram and then showing one group of components for all jsps. This is duplicacy. If you have better idea, please share.

[Kumar Amit]

Rajan Choudhary wrote:I am showing just the names in a UML component icon which means that's a component. I already that, I have 75% duplication in class and component diagram but I don't know where to keep what? As cade's book says, I am showing JSPs in class diagram and then showing one group of components for all jsps. This is duplicacy. If you have better idea, please share.

I reckon you have taken the right approach. There will be some duplicacy. Few things that can make component diagram different from class diagram can be to show filters/listeners in component diagram and not in class diagram/sequence diagrams. I may be wrong. Lets ask what other people think.
BTW, which filters are you showing web tier?

[Ranganathan Kaliyur Mannar]

Rajan Choudhary wrote:[True, but I don't know what else to show for getting a score of 40 points -

Everything is clear in class diagram and sequence diagrams so I see component diagram a complete duplication of classes/objects.

I agree 100%. I have the same feeling that 40 marks is high for component diagram. Some of this could have been offset to deployment diagram and even sequence diagram (less marks for more work).

I am showing 'FacesServlet' only in my component diagram.

[Kumar Amit]

Hi Friends,
Do we need to show each Session Beans as separate component from corresponding JPA entities in the component diagram? For example I have 3 session beans (Managers) and 3 entities. Do I have to show 6 separate components in the "business logic and persistence" tier on the component diagram unlike Mark cade's example where it shows SessionBean and entity classes as combined/single component.

This question of mine remained answered last time, so asking it again to get your opinion.