Computer Laboratory

Course pages 2015–16

Further Java


The deadline for Ticklet 0 is Monday 12th October at 5pm.

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

Each workbook has an associated 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 I Tick. You will need to complete ticklets 3, 4 and 5 to receive the Further Java Programming II Tick.

The automated unit testing system will not accept new requests for Tick I (i.e. ticklets 0, 1 and 2) after noon on Friday 6th November 2015 and it will not accept new requests for Tick II (i.e. ticklets 3, 4 and 5) after noon on Friday 20th November. 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 near the deadline 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 for Tick I on Monday 9th November, and for Tick 2 on the afternoon of Monday 23rd November. A sign-up sheet will be available so you can book a slot with an Assessor. If you are unwell and therefore unable to attend the final marking session, we will arrange to mark your work later once you are better; please email [Javascript required] to arrange this. Remember: illness near the deadline 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.

Session sign-up

Due to a limited number of tickers and demonstrators we need to split the year evenly over two sessions. Please sign up online to your chosen session.

Session allocation sign up sheet: Session 1 (2-4pm), Session 2 (4-6pm)

The sign up site doesn't work very well with Internet Explorer but Firefox and Chrome seem to be OK.

Tick list

View the current tick list. Please contact ticks1b-admin if you notice an error.

Ticking sign-up

When you are ready to collect a ticklet you should sign-up online for a slots with a ticker. These ticking slots take place during the practical session in the Intel lab. You should take your work to your ticker at your chosen time.

Ticking sessions for Week 1: Session 1 and Session 2.

Ticking sessions for Week 2: Session 1 and Session 2.

Ticking sessions for Week 3: Session 1 and Session 2.

Ticking sessions for Week 4: Session 1 and Session 2.

Ticking sessions for Week 5: Session 1 and Session 2.

Ticking sessions for Week 6: Session 1 and Session 2.

Ticking sessions for Week 7: Session 1 and Session 2.

Programming style

Start from ticklet 1 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.

You'll see that we are using (with permission) a slight adaption of the BAE Systems Applied Intelligence coding standard. You should comply with everything described on the 3 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.

3 page summary of guidelines as annotated code: BAES Applied Intelligence-Java coding standards_v1-summary.pdf

Complete document with full explanations and examples: BAES Applied Intelligence-Java coding standards_v1.pdf

Workbook and test suite

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 ticks1b-admin[at]

No errors have been reported so far this year.


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 competition has now closed. Subject to a code inspection by a Ticker, the following students have been awarded stars: jrtc4 (0s000), cs799 (9s928), lm649 (11s051), sl715 (11s919), cjl77 (12s193), mnj24 (13s327), tpt26 (14s404), gs509 (15s450), rt438 (17s096), jf549 (18s494), at698 (19s801), ml693 (20s781), na412 (20s875), jmw248 (21s036)

The current leaderboard, which includes submissions after the deadline, is as follows: