This week's giveaway is in the Cloud/Virtualization forum. We're giving away four copies of Secure Financial Transactions with Ansible, Terraform, and OpenSCAP and have Lucian Maly on-line! See this thread for details.
Hi, I'm close to submitting Part II. To keep the component diagram managable I plan to have just a couple of token 'Any JSP's. I have a separate navigation diagram showing all the main JSPs and the route through them for most of the use cases. On the component diagram I also show only the most important entity beans - those accessed directly from the session beans and the one BMP bean. All the beans and their relationships are shown on the class diagram. Is this a bad idea? I've read quite a few comments that absolutely everything has to be on the component diagram. Thanks, Rich.
In a real world scenario, component diagrams are handed over to the developers to help them get the "big picture". I guess it is fine just to show all JSP components as one cluster. Although I have not submitted my assignment yet, I have drawn mine using a rule of thumb - if a component is not architecturally significant, then it has no place in the component diagram. You may opt to completely omit them, or just represent them as a single entity. Make sure you represent everything the assignment asks for.
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
I've been selected to go to the moon! All thanks to this tiny ad:
SKIP - a book about connecting industrious people with elderly land owners