Sean Beecroft

General Con: 100 90
Documentation: 70 70
OOD: 30 30
GUI: 40 27
Locking: 80 80
Data Store: 40 40
Network Server: 40 40
Total: 400 377

Passed with flying colours!

My design was fairly simple. I did not save when the user saved, but rather
I have a cache in ram that would save all of the records once every 30 seconds and when the application was closed.

My GUI I thought was good. I will figure out what I did wrong - but - it is in the past now.

Thanks for all of the help.



On a side note - that was the hardest assignment I've done!

[ July 21, 2008: Message edited by: Sean Beecroft ]
[ July 21, 2008: Message edited by: Sean Beecroft ]

Thanks to everyone who helped!
It took me a long time and alot of effort - but I passed!

There is no point in denying that it is a difficult exam. Even for very experienced programmers. I wouldn't be discouraged, just keep trying.

Eventually you'll get it.

Sean, I don't know the result of my assignment yet, but I will say this, I don't think I would have even had the slightest chance without a good testing strategy.

Testing is critical for this assignment.

I already submitted my project. I will shout back here and let you know how it goes. Hopefully they won't penalize me.

With regards to saving on power failure:
It is true that it would lose data on a power failure.

I did not see any requirement to save in the event of power failure.
It saves just fine on normal shut down.

Theoretically any design could fail to write a record on a power failure.

The reason I did it was because it made it much easier to read.

Keep you updated on the results.
[ April 02, 2008: Message edited by: Sean Beecroft ]

I've gone ahead implementing my vacuum functionality.

Anyone think this is a bad idea?

go back to the drawing board. You are required to lock the record.

The fact that I said "Strange Architecture" is not a great way to start off.
I should have said that differently.

I found the code was too awkward and difficult to understand before. (I previously had the "simple" architecture). My new architecture is alot easier for me to read.

It basically has a hash map which is easy enough to understand, and then it has a routine which writes that to the file every once and a while.

That is probably a fairly common architecture for any database app. Re-writing the app at this point would be alot of extra work.

I have a strange architecture.. all of the changes occur and are written to a hash map, and then on a regular basis (as specified by a timer and on certain events (such as exit)) it re-writes the contents of the file. This enables me to "remove" records that were deleted - thus saving file space. My question is this, will I be penalized for having an architecture which is perceived as "too complex".

My question is just - any ideas anyone has for final submission. Things to double check, things not to forget, or things someone wished they did.

I'm very close to submitting my final assignment, so I'm nervous that I don't forget anything.

I was hoping anyone here could share some things they thought of doing before submitting final submission.

So far, I've got:

-Spell checking
-General QA on all must requirements
-General QA on usability
-Testing on multiple platforms
-Reading all of my Javadocs for accuracy.

Trying to think of more things I can do...

I've got a working application, and it seems to meet the requirements.
However, before I submit my project, perhaps some could share any ideas on final QA processes, or things to look for / check for before submitting the final project.

Stuff one might forget to check.

I've got 36 classes. There are a few more anonymous classes.

Is this too many?

I did mine by date.

I've had to modify this test for the BS. It is more comprehensive then my own concurrency testing. As a result I may have found a dead lock in my code.

Congrats Alex!

I think thats a pretty good score. I've got a long way to go on mine, it seems. Finally I've got the app meeting the requirements. Now its a long trek of refactoring and fixing things. I followed you through it, so I'm glad you passed. Now I'm worried about my own.

WeakReferenceMap? Uh-oh back to the drawing board for me.