Computer Laboratory

Course pages 2012–13

Further Java


As described in the Head of Department's Notice, this course has internal deadlines which must be adhered to. These are printed on the first page of the course handout and repeated here.

The automated unit testing system will not accept new requests after Midday on Monday 21st January 2013. All work submitted before the deadline which subsequently passes the unit tests will be assessed. Work which fails the unit tests or is submitted late will not be assessed. Illness on Monday 21st January will not be accepted as an excuse for failing to submit a correct solution by the deadline, so please ensure you have completed all the necessary work well beforehand.

There will be a final marking session with Assessors on the afternoon of Monday 21st January. A sign-up sheet will be posted outside Student Administration at the start of Lent Term so you can book a slot with an Assessor. If you are unwell on Monday 21st January and are unable to attend the final marking session, we will arrange to mark your work later once you are better; please email to arrange this. Remember: illness on Monday 21st January will not be accepted as an excuse for failing to submit a correct solution by the deadline. Therefore we will only mark your work after the deadline if it was submitted on time and passed all the tests.

Workbook and test suite

Workbook 0: once you have tested your program using the data in the file please submit your solution as described in the workbook. The time taken to execute your solution will appear in the leaderboard shown below.

Workbook Errata

The printed workbooks contain (at the very least!) the following errors. Errors are indexed by workbook (W), page (P) and line (L), which may be negative, indicating that the reader should count upwards from the bottom of the page. These errors have been corrected in the on-line versions of the workbooks shown above. If you find any further errors, please email ticks1a-admin[at]



For this exercise the top ten implementations which have been tested by the deadline are awarded a star. We've seen timing variations between repeated tests of the same submission, so stars are also given to solutions which are within 3 seconds of the 10th ranked implementation.

The current leaderboard is as follows: