Judging

Your work will be judged on two things. The exact criteria are up to the judges: the list given here only contains some suggestions for things to look at.

• The software itself.
  • Does it work?
  • Is the structure any good?
  • Are there enough comments in the sources?
  • Is it fail safe?
  • Is it hacker proof?
• Your documented experiences.
  • Do you make a solid case?
  • Do the judges agree with your arguments?
  • Are your arguments based on facts (from the contest) or is it still unclear why you state your arguments?

The documentation

You can deliver your documentation in any format that you see fit, but if you use a word processor, please also deliver a PDF document. If you don't have any tool at hand, go download a copy of Webby. Although its intended use is for creating small websites, it might well do your documentation job for you. If you use Webby, you need to have Java installed to deliver a PDF.

Examples

You can keep detailed records of experiences you had wile developing the solution. E.g.:

10-7	Started work, but couldn't register my components from work. I looked on the web and found a suggestion in newsgroup foo.blah.com and that worked.
12-7	The documentation in the help file about clipboard formats was inconclusive. The MSDN documentation came to rescue
20-7	Tried my software on a Windows XP machine, but it didn't work. Pressing F1 popped up an Microsoft exception dialog.

You can also write a single document at the end of the 'project' summarizing your experiences. If you do keep a log of events it might help you though.