Like others, I am also somewhat stuck into exactly what Sun is looking for in the class diagram. There is already the Buisness Domain diagram, is it just a matter of adding entities to this? Or do they want us to show Session beans, Servlets and JSPs on it too? Thanks in advance for any help, Jehan
Hi, I looked at the postings of some of the top performers and it looks like they have shown only business level objects without showing J2EE specific stuff in the class diagrams. But then, there are other top performers who have shown J2EE objects in the class diagrams and still have got top percentages.... I guess there is no black or white answer to this one except that you make sure that you show all the aspects in some relevant UML diagram(s) in your architecture. Hope this helps. Sridhar-
Yes, I stand by what Sridhar has written. Class diagrams should limit implementation specific entities( such as EJBHome, Remote etc ) to avoid clutter. You may use stereotypes to indicate how an entity is implemented eg., <<SessionBean>> but keep the diagram simple but complete. The idea is to represent the design classes that surface during the analysis when you apply the business requirements to the logical domain object model.
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
sunglasses are a type of coolness prosthetic. Check out the sunglasses on this tiny ad: