Department of Computer Science and Technology

Course pages 2017–18

Further Java


Practical sessions will run in the Intel Lab in the Computer Laboratory from 13:30 until 16:00 on Thursdays as follows:

  • 19th October - mark Ticklet 0, start Ticklet 1
  • 26th October - mark Ticklet 1, start Ticklet 2
  • 2nd November - mark Ticklet 2, start Ticklet 3
  • 9th November - mark Ticklet 3, start Ticklet 4
  • 16th November - mark Ticklet 4, start Ticklet 5
  • 23rd November - mark Ticklet 5

Workbook and test suite

Remaining workbooks will appear on the day of their starting practical session.

Workbook Errata

Thanks to Patryk Balicki (ppb2) for finding an updated version of the academic paper used for Ticklet 3*. This paper clarifies a couple of points on the operation of the algorithm required to pass this ticklet; Workbook 3* is now updated with a reference to this version of the paper.

Programming style

This year the tickers will be checking your code for good programming style. We understand that this is a subjective area but would like you to try and comply with the following guidelines. We will use (with permission) a slight adaption of the BAE Systems Applied Intelligence coding standard. You should comply with everything described on the three-page summary except where we have marked it as optional ('Opt'). If you have any questions then please ask a lecturer or demonstrator during the practical session.

Three-page summary of guidelines as annotated code: BAE Java coding standards (summary)

Complete document with full explanations and examples: BAE Java coding standards


You will need to complete one workbook each week. Each workbook has an associated exercise, or ticklet, which is described at the end of the workbook. You will need to complete ticklet 0 (issued with Workbook 0 in Easter Term, and available from the course web page) together with ticklets 1 and 2 to gain the Further Java Programming Tick I. You will need to complete ticklets 3, 4 and 5 to receive the Further Java Programming Tick II.

There are internal deadlines, enforced by the automated tester, as follows:

  • Ticklet 0, Monday 9th October at 1700
  • Ticklet 1, Thursday 26th October at 1200
  • Ticklet 2, Thursday 2nd November at 1200
  • Ticklet 3, Thursday 9th November at 1200
  • Ticklet 4, Thursday 16th November at 1200
  • Ticklet 5, Thursday 23rd November at 1200

Work which fails the unit tests or is submitted late will not be assessed. Requests for extensions will be considered if received from a Director of Studies. If you are unwell and unable to attend a marking session, we will arrange to mark your work later once you are better; please email [Javascript required] to arrange this as soon as possible, ideally before the session starts.

Marking times with a Ticker


For the Ticklet 0 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 final leaderboard is as follows: