It is not a high score, but finally i can sleep more relax
My class diagram had 21 classes. I put different color to identify Entitys, Services (EJB), and Subsystens. My Component Diagram had 15 components. I didn't not show jsp and servlets. I presumed that Client can be anything such (Web, Desktop, Mobile). I also put different colors to identify Entity Beans, Session Beans, Classes, Subsystems, etc. My Sequence Diagram had nothing special, no colors, no method names, no parameters, etc..
My document had only one page with following topics:
* Design Goals * Service level /Non-functional requirements * Application Tiers * Design assumptions and decisions * List of J2EE and GOF Design patterns used * Deliverables
I hope that this can help anyone.
Someone has any idea about the low score ?
System Analist - Team Leader<br />SCJP - Sun Certified Java Programmer 1.4<br />SCWCD - Sun Certified Web Component Developer 1.4<br />SCEA - Sun Certified Enterprise Architect
Any particular reason for not showing JSP/Servlet in Component diagram.
I think they do provide value to the Component diagram. Because Component diagram provide basic structure of the system and how it will function. But mentioining the JSP/Servelet, the user get much better view of the system in term of how it will function.
Originally posted by Rafael Benevides: My Component Diagram had 15 components. I didn't not show jsp and servlets. I presumed that Client can be anything such (Web, Desktop, Mobile). [...] Someone has any idea about the low score ?
I think that your presumption "that Client can be anything such (Web, Desktop, Mobile)" is great. Never the less I would have shown at least a UI suitable for agents ("have a GUI client") and one for customers ("web interface"), because these are given in the interview of the business analyst.
You could have done this quite easily by drawing your Component diagram as you did and ending it showing the interfaces that any JSP, GUI or whatever UI needs to realize.
Then in two other simple component diagrams you could have shown just those interfaces and either the realizing JSPs or GUI. I also believe you would have got some more points doing so. Midlets etc. you could just have mentioned as you did.
I just put a comment at Component Diagram saying "Web User GUI is a web based application, composed by JSP and Servlets. Travel Agente GUI is a Swing based application provided by Java Web Start"
Congratulations !! another Latin american !! grate news !!!
Could you tell us more about the 1 - sequence diagrams ? did you your DTOS and TOS, creation of DTOs ? interaction with factorys and abstract factorys ? or you show it a high level ?
2 - Component and classes, why you show Entitys in class diagrams ?, wy not in component diagrams ?
Santiago Urrizola : La Plata - Argentina<br />SCEA (89%-92%)<br /><a href="http://gpitech.wordpress.com/" target="_blank" rel="nofollow">http://gpitech.wordpress.com/</a>
Rafael Tabosa<br />From Brazil-Fortaleza<br />Sun Certified Java Associate<br />Sun Certified Java Programmer<br />Sun Certified Web Component Developer<br />Sun Certified Business Component Developer<br />Sun Certified Enterprise Architect (Part I)<br />IBM Certified Enterprise Connectivity with J2EE
Rafael Benevides
Greenhorn
Joined: Jan 24, 2006
Posts: 7
posted
0
Santigo,
i think that i not explain it very well. At Class diagram, i show Classes (Domain Model) and i wrongly called it Entity. Entity Beans was only showed at Component Diagram... It was a mistake when i typed it.
I used TO�s and didn�t use any type of Factory. To�s was created by Session Beans.
0
