SCJD begins

Hi People,
I have registered for this exam yesterday and soon within 1 week ill be downloading the assignment.

Can anyone provide me the typical list of design patterns that are useful while completing this assigments

Also how long does it take to complete this assignment (average) considering I can give 2 hours every day and more n weekends

Thanks in advance

I spent about 16 hours of coding the whole assignment. That was the funny part, now i am writing on the choices document, user manual and javadoc. Totally i think it will take less than 40 hours to complete.

Hi Yogesh,

I've found that most people take about 6 months to complete the assignment. Three months, if you're moving @ a fast clip. That assumes about 10 hours a week.

All best,
M

Originally posted by Mike Vess:
I spent about 16 hours of coding the whole assignment.

16 Hours !!! Thats way too less .. (Go ahead and write a book on "SCJD in one Week ") You must be really already a pro in Mulitthreading and OOP/RMI etc

I spent about 16 hours of coding the whole assignment. That was the funny part, now i am writing on the choices document, user manual and javadoc. Totally i think it will take less than 40 hours to complete.

Wow. Granted, I suppose it can be done that quickly... but I have never seen it done (successfully). Mike, let us know when you pass.

I expect to take around a year to do the project, but I am also only working about 5 or 6 hours a week. (I have two wonderful children that seem to think my spare time is better spent playing with them.

)

I think I spent about 5 hours just writing JUnit tests for my project. The rest of the Java development took about 70 hours (not including full javadoc comments) for me -- ie: 2 weekends and one long weekend. But I implemented every method in the Data interface.

Although the type of project wasn't "typical" IMO (esp: creating an RMI server, Swing GUI, and using flatfiles), there were many considerations that were left out that seemed to mimic some of my real-life projects. Ironically it's those issues that seem to take a lot of time to sort out -- even if it boils down to 20 lines of code. IRL, they can prove critical, and it's worth spending time on them.

Anyway, have fun.