Computer Science


Assignments: COMPSCI 230 Semester 1, City Campus

Dates

Assignment marks are 16% (= 4% + 5% + 5% + 2%) of your final marks.

  • Assignment 1 (4%), due 4pm Friday 27 March 2015. Sample answers and marking guide. Final release: v1.02 of 2015-03-16 (with minor changes and clarifications), umlexamples.zargo (version: 2014-03-14), for use in question 7. hbbv1.jar (version: 2015-03-11), for use in questions 8 and 9. zargofile corresponding to hbbv1.jar (version: 2015-03-11).
  • Assignment 2 (5%), due 4pm Friday 1 May 2015. As announced in lecture on Friday 24 April, submissions prior to 4pm Monday 4 May 2015 will not be penalised for lateness. However the -50% penalty for late submissions is still in force, and the final submission deadline is still 4pm Wednesday 6 May 2015. Full release: v1.0 of 15 April 2015. hbbv2.01.jar. hbbv2.01.zargo. Sample answers and marking guide.
  • Assignment 3 (5%), due 4pm Friday 22 May 2015. Sample solution. Marking schedule. Full release: v1-0 of 08 May 2015. A3v1-0.zip. Update release: v1.1 of 14 May 2015. A3v1-1.zip.
  • Assignment 4 (2%), due 4pm Friday 29 May 2015. Marking schedule. Handout v1.01 with clarified experimental units in question 3 (note that you should not rework your experimentation on this question if you have already completed it, instead you should analyse the data you have collected), jarfile for SE8 only, jarfile for SE7. Note: due to the late release of a jarfile compatible with SE7 (at 9pm on 25 May), there will be no lateness penalties on this assignment. However the final submission deadline is still 4pm Wednesday 3 June, and no late submissions will be accepted for marking.

Quizzes are 4% (= 1% + 1% + 1% + 1%) of your total marks. Quizzes are multichoice, and are administered online via Cecil.

  • Quiz 1, available from 9am Friday 13 Mar to 11:30pm Monday 16 Mar.
  • Quiz 2, available from 9am Friday 3 Apr to 11:30pm Monday 20 Apr. Note: the mid-semester break is 4-19 Apr.
  • Quiz 3, available from 9am Friday 8 May to 11:30pm Monday 11 May
  • Quiz 4, available from 9am Friday 29 May to 11:30pm Tuesday 2 Jun. Note: Monday 1 June is the Queen's Birthday holiday.

Top
Assignment Dropbox

All assignments will be submitted and returned electronically. Assignment 1 is handled by the Assignment Drop Box. You should look to the individual assignment to find the submission instructions -- some may use the Cecil assignment submission facility. Please note that the Cecil facility accepts only a single file from each student: you must submit a zip archive, if you want to submit multiple files.

Top
Marking Policies

  • If you are sick, or for some other serious reason would need an extension, email the lecturer who has set the assignment.
  • Before submitting:
    • Check carefully that your project runs in the lab (i.e. not only on your home or office machine). This is the only environment that will be used by the markers.
    • Your marker will not correct or improve your code, even if only minor corrections are required.
    • Please re-check your zip file, immediately before submitting it. Are you submitting all the required files? Did you unpack them from your archive into an empty directory, on a lab machine, to confirm that they will compile and run? If not, then you are in danger of getting very poor marks.
  • After receiving your marks, if you think that the marking was not fair (and have good arguments), please send an email to the course coordinator.
  • Assignment submissions will be accepted after the due date, but with a substantial penalty for lateness.
    • -20% of possible marks, if submitted by 4pm three days after the due date.
    • -50% of possible marks, if submitted by 4pm five days after the due date.
  • You cannot sit a quiz after the deadline, because we will be releasing the answers on the due date.

Top
Plagiarism / Cheating on Assignments

Although you are welcome to verbally discuss assignment problems with your friends, you must develop the code for your assignments on your own - it is not acceptable to submit code or parts of a program written by someone else claiming it was your work.

We use many ways to check that the work each student submits for marking is their own work and was not produced by, or copied from, someone else.

  • We start our checks by running a comparison program, which automatically compares all submissions from students.

All assignments deemed to be too similar will be assigned a zero mark on the entire assignment, and will be invited (by email) to discuss the situation with the course coordinator.

  • Both the person who copied the work, and the person whose work was copied, are allocated a zero mark.
    • It is important that you do not lend your assignments to others. Never give anyone a copy of your assignment. It is the responsibility of each student to ensure that others do not copy their work.
  • Offenders may be referred to the University Disciplinary Committee.
  • For more information, please see the University's Academic Integrity webpage.

Top


Apply now!


Handbook

Postgraduate study options

Computer Science Blog



Please give us your feedback or ask us a question

This message is...


My feedback or question is...


My email address is...

(Only if you need a reply)

A to Z Directory | Site map | Accessibility | Copyright | Privacy | Disclaimer | Feedback on this page