Originally posted by Thang Vu:
I have just passed part 1 of SCEA exam today, with 100% scores! I would like to share my experience in preparation, and some information about the contents of the test itself.
Actually, the test was easier than I expected. One thing that helped me a lot is my experience in architecting real-world enterprise applications using J2EE. Most of the questions checked whether you understand the core concepts, best practices and ideas of the Java 2 platform, especially EJB. Broad (not deep) knowledge of all exam objectives is required in order to analyze scenarios and come up with the right choices. There was no question about J2EE API.
Below is the list of resources that I used:
1) Sun Certified Enterprise Architect for J2EE Technology Study Guide, Cade-Roberts
2) Mastering EJB 2, Ed Roman
3) Applied Java Patterns, Stelting-Maassen
4) Leo Crawford's notes (http://www.leocrawford.org.uk/work/jcea/part1/index.html)
5) SCEA Nutshell (http://groups.yahoo.com/group/scea_j2ee/files/SCEA-Nutshell/)
6) Chris Broecker's notes (http://groups.yahoo.com/group/scea_j2ee/files/)
7) WhizLabs SCEA
I started preparation by using WhizLabs  to identify my weaknesses, then studied related topics with [2,3,4,5,6]. I used Cade's book to summarize knowledge gained, and practiced scenario-based questions with WhizLabs. I would say that WhizLabs's questions are more difficult than the exam's questions, especially the scenarios. However, make sure that you understand the topics, understand how to analyze situations, not just remember answers provided by WhizLabs. A day before taking test, I reviewed the objectives going through the notes [4,5,6] once again. Of course, follow this forum and study from your discussions here was a big advantage (though this is just my first post ).
Overall, I have spent about 2 months with 2-3hours/day to prepare for the test.
I believe the part II & III are much harder and do hope to receive your help. BTW, what is the good starting point for part II?
Good luck to you all.
Originally posted by Pradeep Bhat:
what is the difference between latency and response time?
Originally posted by Ram Krishna:
Passed part I today with 87%. Just wanted to thank everybody for posting all the information out here. I haven't been active on the site myself but have been following all the threads and that helped a lot.
You guys rule !!!
Originally posted by priya shankar:
Can anybody explain me what is Functional and Loading Testing
Originally posted by Debanjana Dasgupta:
Just passed Part 1.
Some of the questions had upto 8 choices.
But overall, Sun doesn't try to trick you.
I studied Monson-Haefel, Mark Cade, and lots of material from the yahoo groups and SCEA links page here.Whiz Labs mock tests were also helpful.
Thanks to all the ranchers ! Now all set for Part 2.
Originally posted by Tauqueer Ali:
Hi Fellow Ranchers,
I passed 486 exam with 89% two days back. A large share for this success goes to this excellent
forum. Questions discussed by Desai Sandeep and Junilu Lacar were particularly helpful.
Thanks a lot.
Let me share my experience with you guys.
I applied the iterative and incremental approach to my exam preparation and found it to be
very useful. It took me exactly 28 days to prepare for the exam. I started with Larman.
During the first iteration I went quickly through all the chapters to get an overall idea
of the whole thing. At the same time I kept marking the difficult topics(high risk topics).
During the second iteration I deliberately chose the high risk topics in the beginning and cleared
them keeping in account their relevance to the exam.
The third iteration didn't add any new major concepts to my preparation. It was more of
bug fixing sort of iteration where I tried to revalidate my concepts.
All the iterations were time boxed and I tried my best not to exceed them.
1st iteration 8 days
2nd iteration 6 days
3rd iteration 4 days
After that I started with UML distilled. Its actually a very easy read after Larman but
it's a must read from exam point of view.
5 days before writing the exam I purchased OOAD@Whiz. Found it to be quite useful.
you may not get very similar questions in actual exam but it helps.
Pre assessment test is an indispensable resource. It completely defines the scope of the
exam. I found the actual exam to be quite similar to it.
My comments regarding the 2 books that I used, "Applying UML and Patters" by Craig Larman and
"UML Distilled" by Martin Fowler :
Larman's book is an excellent book and is a must to get the true idea of iterative
and incremental development(Unified process). Understanding of this process is the
key to the exam.
UML Distilled is a very concise book. It'll give you all the necessary factual information like
types of diagrams,
when to use a particular diagram (very important from exam point of view),
a very brief idea about the Unified Process.
To get a complete and comprehensive idea about Process, you should read Larman.
One particular resource that I would like to mention here is the case study on Larman's site.
(Instructor resources link on the home page ). Its actually an exam question to be used by
instructors who plan to use Larman's book.
I found it to be an excellent learning tool. Did it after I finished reading both the books.
A thorough understanding of class diagrams, including associations classes, aggregation and composition
is a must. I'm mentioning these topics here because these are somewhat more involved than
other topics and should not be left for the end.
Hope that helps,
Originally posted by Edy Yu:
Here is the details:
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) .......................... 42
Component Diagram (44 maximum) ...................... 42
Sequence/Colloboration Diagrams (12 maximum) ........ 7
I lost about 40% on seuqnece diagram which is reasonable because I didn't pat much attention to it.
I was trying to give a detailed design when I started the assignment. But I finally realized I was not a developer anymore and should not concentrate on those trivias. I didn't design the application client. My whole focus was on the business tier.
This forum is helpful. But again, don't put too much effort on details. It's an architecture design, not the real implementation.
[ December 10, 2002: Message edited by: Edy Yu ]
[ December 10, 2002: Message edited by: Edy Yu ]
Originally posted by RAEES UZHUNNAN:
Passed with 91 %.
Guys please give me some directions to appear for part II
Originally posted by Robert Wright:
I just got back a 100% score on part II/III. Many thanks to those in this group; you’ve been a great help to me.
Here’s my advice.
JUST GET STARTED. Don't spend a lot of time wondering how much detail or what patterns or things like that. This is a "learn by doing experience" not "learn by thinking". Move through the complete design several times, improving it on each pass. It's OK if the first pass is awful, just keep refining it. Don't be afraid to tear it apart and start over if that is what is needed. You'll be surprised how much you will learn about design just by doing it.
Document your design clearly. I had several pages of written documentation. I included:
-- My assumptions (there were many)
-- Naming conventions (I had a clear set of conventions that I followed throughout the project)
-- Explanations of how the classes interacted and what jobs they did
-- What patterns I had used
-- Brief justifications of design decisions
Read carefully through the doc and make sure that you actually address each requirement that they give you at some point. Don't skip anything. Look over the "ilities" (Scalability, Maintainability, Reliability, Availability, Extensibility, Manageability) and see how your design addresses these.
COMMUNICATE. I spent a lot of time making the drawings look good. Use the same font family for everything and limit the number of styles and sizes that you use. Go for a simple, clean look. Make sure EVERYTHING lines up down to the pixel. (I used SmartDraw for the drawings). I didn't put a whole lot in each drawing; I broke them down into logical sections. Make sure your written docs read well, are cleanly organized and have no typos. Write, edit, re-write and edit again. Don't use any unnecessary verbiage. Make your English teacher proud. A major part of the job of an architect is to COMMUNICATE his design effectively. The person you have to communicate this design to is the examiner. MAKE THEIR JOB EASY.
Go over your materials for part I and apply them to part II. You will find a lot of things you can use.
I did everything "The Java Way," using patterns and solutions extracted from Sun documentation. I mostly did this because I treated the whole thing as a learning exercise. If I ran into a problem that I didn't know how to solve, I looked at the approaches taken in the Sun docs. I was always able to find a pattern that made sense to me (even within the Sun docs there is often more than one way to solve a problem.) Use the solutions that others have developed, don't just mis-understand what others have done and then spin off into "creative solutions."
Think things out for yourself. Can't decide whether to store client state in HTTPSession or Stateful Session Beans? How did others do it? What are the arguments for each approach? How do they affect your design? Work it out, make your decision and then put your reasons in your docs.
My best advice is to make a clear, well-organized presentation of a design that you feel confident in.
This was the best set of notes that I found.
You will probably have to join this Yahoo group to get access, it's free and it's a good group.
Don't get too fancy with your UML. Keep it simple. Spend some time checking over the UML in your diagrams and make sure it's "by the book."
This is the Sun study guide. It's not everything you need but it's worth the price.
Core J2EE Patterns
This one was very useful. Read all the design patterns in the book and understand them. See if you can apply them to your design. Mention in your documentation that you are using the pattern. Don't just use patterns just because you feel you have to. Find patterns that actually improve the design and use them.
These are some very good presentation slides that outline the Pet Store Architecture. Go over these carefully and find things to apply to your design. If you get stumped as to how to solve a particular problem, take a look at these.
Originally posted by Ilja Preuss:
Certainly, yes! And there are *many* projects out there of the size a team of a dozen developers could handle. Experiences of agile teams seem to suggest that most of those projects could be run without much more written down than code.
Originally posted by stephen callaghan:
Thanks alot for all the posts, study notes and discussions in this group. Really helped me prepare for this exam which at the beginning looked really daunting! I'd also recommend JWhizz emulator for getting you in the mood for all those scenario questions (even though there are a number of bugs/mistakes in the current version).
My exam followed the pretty standard distribution of EJBs, design patterns and UML making up the core questions. These core questions were easier than i thought they would be but some of the questions in the smaller sections were harder (like security).
Would recommend that anyone going for this certification uses it to learn alot more than just what is needed to pass the exam but rather an opportunity to really get to grips with design patterns, j2ee , uml etc.
Anyway, onto the last exam! Thanks again.
Originally posted by Ilja Preuss:
Netherless, those requirements somehow need to be communicated. If you think you need to write them down, I wouldn't mind wether I called them "Use Cases", "Meta Stories" or something else...
Originally posted by Fisher Daniel:
Is it true that Use Case is ideal to capture non-functional requirements (scalability, maintainability, etc ) ?
Originally posted by Meg I:
After just over 5 weeks wait, I received my part II and III results. I passed with 82%. Not excellent but am still happy to have passed. Here is the break down of my results -
Class Diagram 32/44
Component Diagram 39/44
Sequence/Colloboration Diagrams 11/12
I passed part I with 93%.
The only study guides I used were
Mark Cade's "Sun Certified Enterprose Architect for J2EE technology Study Guide"
and the Blueprint for developping J2EE applications. Although, I have previously read the EJB specifications and the GoF design patterns books along with a few other java books.
I used MagicDraw for the assignment. I found it could do everything I needed it to do but ran very slowly on my machine. Although then I only have 64M ram.
I read several of the old threads in this forum to see other people's comments regarding how to approach the assignment. I found this very useful.
Thanks to everyone who has contributed to this forum.
Originally posted by Jayakumar Duraisamy:
I am happy to share that I have passed Part II and III with 100%.
Here are my suggestions to the budding Architects...
1. Keep things simple
2. Follow the domain model
I used Rational Rose on my Linux and used Rosegraph on windows to produce gif images for models.
Eventhough I was not very active here. I often cleared my doubts from Javaranch old discussions
The three threads that were very useful for me was
http://www.coderanch.com/forums/ - Segment and Flight Discussion
http://www.coderanch.com/t/149629/java-Architect-SCEA/certification/Passed-Part-II-III - AMANDA WAITE
http://www.coderanch.com/t/150197/java-Architect-SCEA/certification/Passed-PartII-III - JIGNESH1 SHAH
Thanks a million to Javaranch