COMP132: Assignments

See also the weekly timetable with lecture, lab and help desk times. Assignments are due at 5pm on Fridays.

Your Marks for all assignments and tests.

Assig Out Due Submit
Marks and
Assignment1 20 24 Jul Submit Marks
Assignment2 27 Jul 7 Aug Submit v1, Submit v2 Marks v1, Marks v2
Assignment3 10 Aug 4 Sep Submit Marks
Assignment4 7 Sep 18 Sep Submit Marks
Assignment5 21 Sep 2 Oct Submit Marks
Assignment6 5 Oct 16 Oct Submit Marks

Assignments and Practical Work.

The lab assignments will be described in handouts that will normally be distributed at the Monday lectures, and will also be available from the website.

The first assignment is mainly an introduction to using the computers (your own and in our lab facilities) and the software that you will be using throughout the course. The other assignments consist primarily of programming tasks. The assignments are a critical learning component of the course. They address most of the concepts and techniques that are introduced in the lectures, and they are the most important way of coming to grips with the material in the course.

The assignments are intended to take about 5 hours per week, but the actual time required will vary considerably from student to student. The scheduled lab sessions will help you get started the assignments, and then help you solve issues that you are stuck on, but you will need to spend more time outside the scheduled sessions. There will be scheduled online help-desk times when a tutor is available to answer individual questions about the assignments.

Please note that that copies of assessed work will be retained for inspection by the discipline review panel and the engineering accreditation panel.

Course Specific Information about Plagiarism.

Please read the School policy on Plagiarism. We will penalise anyone we find plagiarising, whether from students currently doing the course, or from other sources. Students who knowingly allow other students to copy their work may also be penalised. If you have had help from someone else (other than a tutor), it is always safe to state the help that you got. For example, if you had help from someone else in writing a component of your code, it is not plagiarism as long as you state (eg, as a comment in the code) who helped you in writing the method.

In COMP 132, we may use an automated system to check all submitted code in order to identify students submitting the same code who have not stated that they were working with a partner. The system does not make any code available to people other than the organiser of the course and the managers of the system.

Copyright: Although students own the copyright of any code that they write for an assignment, but you are not permitted to post to the web, or distribute in any other way. Also, you may not distribute model solutions to anyone other than a student currently in the course. Breaking this rule is a violation of the university's statute on student conduct. If we find that you have distributed our code on the web or by other means, we will seek disciplinary penalties. Don't ruin the course for future students by giving them answers!