Test: Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061) Date Taken: 2007-04-12 18:47:33.197 Registration Number: o8bsyd555a Site: ii98 Grade: P Score: 92 Comment: This report shows the total points that could have been awarded in each section and the actual amount of points you were awarded. This information is provided in order to give you feedback on your relative strengths on a section basis. The maximum number of points you could have received is 100, minimum to pass is 70. Class Diagram (44 maximum) .......................... 39 Component Diagram (44 maximum) ...................... 42 Sequence/Colloboration Diagrams (12 maximum) ........ 11
I was a silent observer of this forum, and your posts helped me a lot to learn ,understand and finally to make this happen.
Please share with us any tips you have or material you would recommend reading/referring to.
Thank you, Ishan
Joined: Jun 24, 2005
SCEA gives a good opportunity to read and practice Java Pattern and Practices, OOAD and UML. Thus SCEA is a great learning experience. We don't have to worry too much on how we define - Segment-Flight-Seat relationships, but just use common sense. I think importance is given to how well we define our design using J2EE and Java Pattern and Practices, and conformance to UML standards.
I have used following books for reference.
1. The Unified Modelling Language User Guide by Grady Booch , James Rumbaugh , Ivar Jacobson
2. UML Disttled (Martin Fowler) is a good nutshell
3. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, Third Edition by Craig Larman ( In fact I found this as a good book to build fundamental OOAD thinking style)
1. J2ee Pattern and Practices
2. Cade's SCEA guide
3. The J2EE Architect's Handbook (by Derek Ashmore, from theserverside.com )
4. Enterprise JavaBeans, Second/Third Edition By Richard Monson-Haefel (Especially for understanding CMP Relations)
I lost marks in all parts: 5 in Class Diagram, 1 in SD and 3 in Component Diagram, I am not sure what/where went wrong. It could be my design logic or UML conformance....