Hi, Wish to get your help. I am studying the SUN Micro guide of SAEA. I am working on part II. As for the class diagram, it seems that the classes included are all from EJB side. none of the JSP or servlet is included. Can anyone give some suggestion? Should I include Servlet into class diagram? Thanks a lot [ January 07, 2004: Message edited by: Li Xin ]
I have read many times in this forum from people who have passed the SCEA that they did not put JSP/Servlets in the class diagram. I am still working in my assignment and I am following the approach on Cade�s book (show only business objects and session fa�ades). I have heard that people who have used Struts and passed, but I do not know how they modeled it. In my case I am not using it - though in real life I would.
what about the client application 's JFrame and other view components ? Mark Cade 's book is very sketchy on Java application components , are you putting them as well in your component diagram ?? By the way I see a couple of threads that refer to the assignment that I got , is there just one being recirculated , by sun ?? Are you sticking to one each of class and component , I plan to advise them to print on A3 and in some cases A2 paper ? your thoughts please
K.P.Thottam (K.P.T)<br /> <br />Sun Certified Enterprise Architect,TOGAF 8 Certified,Certified Information System security Professional (CISSP),SCJDWS,SCWCD,SCJP,MCP
I've got SCEA. In my experience, you only need to do what you think is right, and try to prove it. If you convince the assessor, then you pass, otherwise... I prefered to use the class diagram to show my business domain analysis, and let the JSP/Servlet/EJB in component diagram. You see, component diagram may help to describe the system deployment. So it have a closer relationship with specified technique, such J2EE/.net. You may read Mark Cade's book to have a good reference. Just make your solution reasonable, and that's all right! Good luck!
I agree with showing the business domain in the class diagram only. I myself let even the session fa�ades out of the class diagram. (but then I got only 42 points out of 44...) In my opinion a UML diagram must represent just one idea and you choose the diagram that models that idea best. So you use a class diagram which is good at showing relations for modelling the business domain. And you use a component diagram as the 'recipe' of your application, showing which and how application components use eachother. (As I probably would prefer a deployment diagram to describe the system deployment ) By asking for a class and a component diagram (and sequence diagrams) Sun, I think is actually asking for specific ideas about the architecture thereby ruling out the possibility for countless variations of diagrams.