Finally: after nearly a month!!! Colombia has a new SCEA!!
Thanks to all in the forum for sharing their experience!
First and most important KISS.
Used Jude as the UML modeling tool and exported PNG.
Used maven for documenting my assumptions and presenting the project in HTML (gives it that profesional look we all want!)
st: Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061) Date Taken: 2005-12-15 21:19:19.687 Registration Number: ma6lam5083 Site: cl29 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) .......................... 43 Component Diagram (44 maximum) ...................... 38 Sequence/Colloboration Diagrams (12 maximum) ........ 11
Congratulations Mauricio, Its a great achievment. Can you please tell me to complete all the parts 1, 2 & 3 right from the beginning how many months it took for you? And also if you have time please list out the brief preparation techniques in each part. Thanks, -Surya
To tell the truth I studied about one week for part I. Mainly cause I knew most of the stuff. Personally, I'd recommend people to focus their study on declarative transactions and patterns definitions. The rest of the exam IMHO is something you aquire with experience.
Part II: My class diagram is real simple (only 12 classes) and concetrated on the domain model objects and their interaction. Component diagram showed immplementation guidelines (Web tier, EIS tier) and sequence diagrams were really simple. Didn't focus much on details about leg, flight, etc... Simply documented their relationships using UML.
Part III: My opinion is that an Architect has real value when he is able to express himself well. Since this are essay type questions you should be concerned on being as clear as possible and avoid being too technical. Be shure to understand architectural system capabilities (escalabiliy, security, testability, etc...)