Skip navigation
The Australian National University

Assignment

Academic Honesty and Integrity

Honesty and integrity are of utmost importance. These goals are not at odds with being resourceful and working collaboratively. You should be resourceful, you should collaborate within your team, and you should discuss the assignment and other aspects of the course with others taking the class. However, you must never misrepresent the work of others as your own. If you have taken ideas from elsewhere or used code sourced from elsewhere, you must say so with utmost clarity. At each stage of the assignment you will be asked to submit a statement of originality, either as a group or as individuals. This statement is the place for you to declare which ideas or code contained in your submission were sourced from elsewhere.

Please read the ANU's official position on academic honesty. If you have any questions, please ask me.


Assignment Deliverables

The assignment is worth 30% of your total assessment, and it will be marked out of 30. So each mark in the assignment corresponds to a mark in your final assessment for the course. Note that for some stages of the assignment you will get a group mark, and for others you will be individually marked.

The following table outlines the seven stages of the assignment, their due dates and the marks associated with them. Note that most stages are due in your weekly lab, but Stage 6 is due at the same time for everyone, 5pm Friday, week 11. Your work will be marked via your tutor accessing mercurial, so it is essential that you carefully follow instructions for setting up and maintaining your group repository. At each deadline you will be marked according to whatever is committed to your repository at the time of the deadline. You will be assessed on how effectively you use mercurial as a development tool.

Stage Deliverable Week Marks
1 Organize groups, assign roles 2 1
2 Analysis and design 4 3
3 Individual class implementation 6 1
4 Individual class and testing 8 4
5 Integration demo 9 3
6 Final submission (Friday 5pm) 11 15
7 Final demo and presentation 12 3

Problem Description

The problem is described here.

Updated:  29 July 2012 / Responsible Officer:   JavaScript must be enabled to display this email address. / Page Contact:   JavaScript must be enabled to display this email address.