General remarks

1. Solutions should be submitted as printed hard-copy to the Informatics Department Office (4C13) by
   4.00 pm, Thursday 25 May 2006.
2. You may use, and import into your code, any classes from the DataStructures package.
3. Because this may be a fairly complex programming problem, you should pay particular attention to making your solution well-structured and easy to understand, so that it is easy to verify its correctness by inspecting the code alone. It is probably advisable to get a simple program up and running first, particularly the part to do with storing and searching the dictionary, before adding additional features.
4. Your code should follow consistent conventions, and you are invited to consult Sun's Java Code Conventions.
5. You should include brief comments with your code. See, for example, the Comments section in the Java Code Conventions.
6. You should also include a brief report describing your design decisions and the reasons for them. The report should also explain the rules your program uses for dealing with upper and lower case characters: see above. If appropriate, you should also explain how your program finds variant correct spellings, and discuss the complexity of these operations (i.e. how many lookups are involved).
7. You should also include evidence that you have properly tested your program. In particular you must show the output when your spell checker is applied to the given test file: see above.
8. You should be familiar with the rules on plagiarism and collusion (see §7 of the BSc Handbook for Candidates.You may discuss general issues with others, but the code you submit must be your own. Note also that fabrication of results also constitutes misconduct. Solutions will be examined carefully for misconduct under each of these headings.
9. The rules about late submissions, evidence of impairment etc. are in §6 of the BSc Handbook for Candidates.