Jason Marshall wrote:
Is the server classes the hardest part of this assignment or is there more curlers to come?
Hi Jason,
I will give a quick view how i experienced this assignment. Remark: I'm doing this assignment together with a full-time job and a social life, so I've only time to develop in the evenings and the weekends.
I started January 2009 with the SCJD-assignment and started with the Data-class (implementing sun's interface) and i made my own test providing 100% test coverage: a test-case for each possible situation (normal run of method, exceptions that could be thrown,...). Then i used
Roberto Perillo's test-case to make sure my locking mechanism won't result in a deadlock. Each time when i made a change to Data I ran those tests again, to make sure changes don't have any effect on the program. Duration: 6 weeks.
I chose to use a seperate business layer, so i made my local implementation (+ full coverage test) and my RMI implementation (+ full coverage test + a test to see if my booking process is flawless). At the end of March i finished it (was 2 weeks unable to code due to illness).
And if everything goes as expected, this weekend i should complete my GUI and thus i should finish the coding part (and i did not spend more time each day on it then in the first 3 months).
So implementing sun's interface is the most important thing + making sure your code doesn't deadlock, so i spend most of my time doing that because if your code deadlocks you may receive 0/80 for locking and so it's almost impossible to pass. During development i used a wip-package and if my class was finished i javadoc'ed it completely and moved it to the appropriate package. So a finished class is really finished and i don't have to spend extra time to javadoc afterwards.
So you could easily say server class are the hardest and most important of the whole assignment. marking confirms this: 160 points on server, just 40 on gui, 70 on javadoc and 130 on general consideration + object oriented)
Kind regards and good luck,
Roel