Jo�o Batista

I believe it's only a matter of choice here, since there's no specific requirements for the questions you presented.
Do what suits you best and you'll be fine.

I agree that the verbose documentation is not a bad idea at all (I wrote javadoc for everything as well), but that number "150" seems a bit exaggerated.
I believe you could do some refactoring. At least to guarantee less errors.

Can't tell the exact numbers but:
Classes: Around 30 (including 5 interfaces and at least an enum), nearing 4k LOC
Choices: A page and a half, maybe less.. it was really small
Userguide: 2 HTML pages with nice formatting and full of images. Got really fancy on that one.

What they mean by online is not on the web, but an option to access that documentation inside the running application. You need to provide everything is needed in the submission jar.

It's a good thing to javadoc them. It's an information that is useful to who's understanding the API.
There is no need to change the signature for that, though.

There are many who did not implement the 48-hour.
I implemented in my case, but it was a really simple implementation.
I suggest you document carefully this choice, whatever it is.

I hadn't much trouble with that. Clients may not be 100% sure of what they want/need, so my solution complies with both cases. Just make sure that you justify your choice and you'll be file.

Congrats!
It's now time to update that signature

Originally posted by Aaron John:


Hi Joao,

I could not follow your previous post. Could you give me an example please?

Thanks.

There are other threads mentioning this subject. A popular trend here is to use RuntimeException to deal with that error.

If your instructions does not mention that feature as a MUST, then you are correct

First, congratulations! You managed to go pretty well in the overall!

Second, did you handle deadlock? I am not sure that this is actually needed (there is nothing on the specs about it), but you never know.
That infamous score got me pretty scared in the beginning, but there are threads discussing locking tests, which helped a lot at making the test cases.
Also, modifying code to create artificial conditions is a good thing to do.

Congratulations!

Think about the kinds of Exception that a method can throw and how they affect the method signature.
You'll find a way to disguise that IOException.

@All:
Thanks guys, I appreciate that!

@Roberto:
Yep, I am a brazilian as well. More precisely, a capixaba.
How long are you in the "waiting period"? Mine took about 7 business days, not counting the day I took the test.

@Ulises:
I cannot tell precisely how long it took, since I had to do it in my usually scarce free time. But I can say that an year has passed since I started.

@Soroj:
Looking back at implementation, I think that I really did more than I should do. I just wanted to be on the safe side, and documenting well my choices. That did pay off in both Locking and GUI sections. While it did lower the OO score... I really want to know what I overlooked.
Regarding UI, I had changed the design many times until I was satisfied with.
I had adaptors for the service implementations, used by the controller, which is mainly a collection of actions. Nothing fancy about that.
The topic "Textbox vc combobox" has bugged me for a while, and decided for editable combobox, combining both worlds.
Other than that, I paid attention to tooltips, mnemonics, and everything else needed to make the application user-friendly (including manual)
I did not, however, have any checkbox for case sensitiveness, 48h rule (I implemented that), etc. Those were all documented in the choices. I believe the main thing is to document well that choices document, no matter what design you have (with certain restrictions, I suppose).
I was really satisfied to ace the GUI section.

@Jose
What's next? Some time to relax! I am afraid that won't last long, though...
So I am already making up my mind to SCBCD. That should be useful in my current situation.

Hi all,

Just an observation: I am actually Rafael Prado, but I lost access to that account, and it seems that no e-mail address that I currently use is the one I used here. Hence, I had to create this new account.
I didn't intend of breaking any rules, but since I was extremely busy, I didn't have time to sort this out (don't know if I can).

Enough of that, onto results!

I really thought I wouldn't be able to control my anxiety in the "waiting for results" period, but the real life job really managed to keep me busy on that!
I only lost 5 cryptic points in O-O design, labeling a 395 in my history. I am too happy to worry about what went wrong.

I'd like to thank everyone in this forum, specially Ken (comments), Eugene (heavy MVC topics) and Andrew (wonderful book).
This is a very nice forum, and I plan to be of assistance whenever possible.

Even though I don't drink, the beer is on me!