This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi folks, Do you guys create a component diagram for each use case defined in the assignment ? I am wondering on what basis do you break down the component diagram ? Is it on use case or logically ? Also, do you include all your WAF components in all your component diagrams or just create one component diagram for WAF components only and refer from all your diagrams. Thanks a lot. Bijan [ August 18, 2003: Message edited by: Bijan Mohanty ]
Since component diagrams show *all* applications components, there should be only one component diagram. You should include Web tier components, enterprise components(ejbs) and anything else that make up your application.
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Joined: Apr 16, 2002
Hi Ajith, Thanks for the reply. But, if you make just one component diagram, don't you think, putting all your components(JSP, Servlet, BusinessDeligates, EJBs, subsystems) will make the diagram pretty big and unmanageble ? Thanks. Bijan
Joined: Mar 17, 2000
It will certainly make it pretty big, no doubt about it. But it is typical to have one component diagram per system. Frankly I have not seen multiple component diagrams and definitely not one per use case. May be creating multiple component diagrams- one for the web tier, one for the enterprise tier etc, makes sense, but doesn't the assignment guidelines specifically say only one each of class diagram and component diagram is required? You may be risking non-compliance by submitting multiple component diagrams.....
Originally posted by Bijan Mohanty: Hi Ajith, Thanks for the reply. But, if you make just one component diagram, don't you think, putting all your components(JSP, Servlet, BusinessDeligates, EJBs, subsystems) will make the diagram pretty big and unmanageble ? Thanks. Bijan
Hi Ajith/Nalla, Thanks a lot for your inputs. I'll keep only one component diagram then. I have one last question on this topic. I am using the same kind of WAF that Petstore uses. So in this case I need to show the RequestProcessor, ScreenFlowManager(They will be just one component) and the Action classes(will be many for my domain) and the Event classes(Again many classes for my domain). I am wondering if it's necessary to show all the Action classes and Events for my domain or just showing one component as "WebAction" and one component as "EJBAction" will be sufficient ? What you guys have done if you have used this WAF ? If you have used Structs, do you show all your domain action classes or just one component as the strutAction ? I hope I am not confusing you guys. Thanks. Bijan
It will certainly make it pretty big, no doubt about it.
How many components did you have on your drawing submitted for part II?
Joined: Feb 22, 2002
Frankly I have not seen multiple component diagrams...
There's three in Sun Certified Enterprise Architect for J2EE Technology Study Guide, Sun Microsystems Press, publisher.
You may be risking non-compliance by submitting multiple component diagrams.....
No, you do not. Jitender Bhatia submitted 4 and scored 100%. An architect must be a leader. An architect should strive to create a design that's easy to understand. If four component diagrams conveys your design more clearly, then draw four. One big diagram with horizontal - vertical scrolling and 125 components is going to be a roadblock unless you can print it out and hang it on the wall.