Assessment

The exact details on this page will be discussed in week 1—you’ll get a chance to have your say before we lock things down.

In COMP2300 you will be assessed on six occasions:

  1. a hurdle lab assessment task in week 4 (1 mark)
  2. a mid-semester exam in week 6 (13 marks)
  3. 3 assignments (12 marks each) in weeks 6, 8, 11
  4. a final exam (50 marks)

a hurdle lab assessment task in week 4 (1 mark)

In your week 4 lab session there will be a hurdle assessment task. This will take the form of a short, q&a-style discussion with your tutor. You will be asked to explain and perform a few basic tasks to do with reading, writing and debugging a simple program running on your discoboard. You will receive a mark of either 1 (pass) or 0 (fail).

Since this is a hurdle exam, you must pass this assessment task to pass the course. This is not meant to be scary—the assessment task will not be difficult. The purpose of this hurdle assessment item is to give you a chance to show that you’ve got the basic skills needed to complete the course. If you don’t have the skills to pass this assessment item, then you’ll really struggle to pass the course, and by having this “check” early on in the course you can avoid some pain if you’re not keeping up (for whatever reason).

a mid-semester exam in week 6 (13 marks)

The mid-semester exam will be a written exam and will happen in week 6 (the final week of term 1). Venue TBC.

3 assignments (12 marks each) in weeks 6, 8, 11

The assignments in this course all build on one another—over the course of these assignments you’ll turn your discoboard into a simple musical instrument (how exciting!). The “skeleton” files for the assignments will be released on the assigments page and you will submit them through the SubmissionApp. You can find the late/extension policies further down this page.

The assignments are the heart of this course, and should be fun! Make sure you start looking at and working on the assignments early. By completing these assignments you’ll be able to demonstrate your understanding of how programs are organised and executed on your discoboard.

a final exam (50 marks)

The final exam will be a written exam and will happen during the exam period. Venue TBC.

Marks and grades

To pass the course, you must satisfy all of these criteria:

  1. score at least 50 overall
  2. successfully pass the week 4 hurdle assessment (more info on this below)
  3. score at least 40% (20/50) on the final exam

Your final mark will be the total of your marks on the individual assessment items, with the caveat that your it may be scaled by the examiners’ conference to provide your overall course mark and grade.

If score less than 20/50 on the final exam, you will fail this course with a grade of N and a final mark that is either 44/100 or the sum of your marks on all the assessment items, whichever is the lower.

If your participation and performance in the course is significantly less than what is required to achieve the minimal learning outcomes (for example if your total assignment mark is less than 12, or if you don’t attend the final exam), you will fail this course with a final grade of NCN, which means a failure due to non-completion.

Supplementary exams

Supplementary exams will be awarded only if you meet one of the following criteria:

  1. you have a final mark of at least 45/100 but less than 50/100
  2. you failed the lab 4 hurdle assessment but still received a final mark of at least 45/100

All supplementary exams will be oral examinations.

Late penalties

Late submissions of assignments (and non-attendance at exams) will result in a mark of zero for the assessment item. This means you must plan ahead—don’t leave your submission to the last minute. It’s much better to get something done early and then refine it from there. We won’t accept last-minute excuses for lost work, etc. so make sure you’re aware of all the submission deadlines and plan accordingly.

Extensions

Postponing assessment deadlines is always possible with good reasons—which are mostly issues which are out of your control. For example, if you feel sick on the day of an exam, please do not sit the exam. See a doctor instead and provide a medical certificate. If you already know beforehand that a specific assessment date or deadline will be a problem for you, then contact us right away (either via email or privately through Piazza) and we will work something out for you. In the interest of fairness we obviously will always require good reasons—but we want to listen to you and give you the opportunity to make your case.

All special assessments will be oral examinations.

Appeals

From the date that your marks for any assessment item is released electronically, you have a period of two weeks in which to appeal your mark. After this period your mark will be final.

Marks and feedback

Marks for all assessment items (excluding the final exam) will be released through streams. Qualitiative comments and feedback will be provided through the submissions app.

Academic integrity

At the ANU we take academic integrity seriously—you are hopefully getting used to hearing this in all of your courses.

In 2300, this means:

  • All your individually submitted work is by default assumed to be entirely your own work. Besides forbidding any direct copies, this also means that no part of your submission is inspired by, based on or a re-formulation of work by somebody else. Re-formulating the work of somebody else is actually worse, because (in addition to plagiarism) it shows a clear intent to deceive.

  • If your work has been inspired by something else (e.g. a classmate) you must clearly indicate this in your submission. Obviously you will not receive the highest mark if all of your work is the idea of your neighbour, but by indicating all ownerships and sources clearly, you will stay on the safe side. Failure to indicate all of your inspirations, sources, or collaboration partners will be regarded as an intent to deceive.

  • This course does allow for collaboration if properly indicated in the submission and some additional rules are followed:

    1. The code and documentation which you intended to submit must always be written entirely by you.

    2. You may exchange ideas on scrap paper, boards and alike, but you may not work together on shared documents which are intended for submission. You may not use any of the scrap documents for your final submission—make sure that they stay in the meeting place.

If you break any of these rules, it’s very likely you’ll get caught—we’re pretty good at finding this stuff out. The consequences of plagiarism can be brutal for the individual—much worse than a bad mark on an assignment—and none of us enjoy being a part of it. Please help to make this a clean course which focuses entirely on the learning process and not on policing academic misconduct issues.

Updated:  / Responsible Officer:  Alistair Rendell/ Page Contact:  Ben Swift