Wow! It's all over... after an on/off attempt but 12 months elapsed...
Test: Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061) Date Taken: 2005-01-05 18:44:26.013 Site: gb7 Grade: P Score: 99 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) .......................... 44 Component Diagram (44 maximum) ...................... 43 Sequence/Collaboration Diagrams (12 maximum) ........ 12
My conclusion is....
(1) Don't underestimate Part III. Since Part II and Part III are marked together Part III gives you a chance to show you know what you are trying to describe.
(2) Get on with it. As long as your approach works it doesn't have to be perfect... get it down in UML and submit
(3) Don't fret the detail... Have an idea over the concepts (segment etc.) but don't get too worked up... just go with something consistent and submit.
Good Luck All!!!
Thanks to everyone here that provided motivation. I would have been happy with 70... I probably would have got 70... but the numbers posted by others are a good motivator!!!
>>> 2. Distinction/Interpretation of Segments, Legs etc.
This is my point exactly. Don't worry about it. Just be consistent in your diagrams. Decide yourself what a leg, segment etc. is and GO FOR IT!!! You don't get marked at that level of detail... just show a consistent approach.
>>>How did you solve the problems with crisscrossings in the component diagram ?
Hey! You are half way there... you've spotted that J2EE patterns are important... don't overcomplicate the solution.. but where appropriate use a pattern... ServiceLocator sounds like a candidate... GO FOR IT!!!
My solution was simple. it didn't have many criss crosses!!! Communicate the approach not the detail... this is architecture... the detailed design comes later.
>>> How did you justified your design/solution for Performance and High Availability ?
Use UML to be explict. The assignment shows the overall approach... this is where to determine a target artchitecture and make decisions that give high performance, scalability, etc... Part3 gives a chance to explain why.