Late work, extensions, integrity and support, written for a course whose assessments are built out of your own files.
Policies and support#
Course-wide rules, in one place so the assessment briefs do not each restate them.
Submission and versions#
Submit one file per required artefact. Where an assessment asks for a chain
of artefacts, submit them named so the order is unambiguous. A numeric
prefix is enough, and it is worth more than a word like final.
If you submit twice, the later submission is the one marked. That is a retention policy, and it is the same one every system in this course is criticised for using, applied here because the submission system records who submitted and when, which is the evidence a plain timestamp lacks. If the later file is not the one you meant, say so in writing before the deadline and name the file that is.
Late work#
Work submitted late loses 5% of the available mark per day, counted in whole days from the deadline, for seven days. After seven days the work is not marked and the assessment records a zero.
Extensions#
Ask before the deadline where that is possible. Extensions are granted for circumstances outside your control and are not granted for a hard drive failing, because this is a course about keeping more than one copy of things. Back your work up somewhere that is not the machine you are working on.
Academic integrity#
The four assessments are mostly built from your own files, which makes plagiarism awkward but not impossible. The rule is the ordinary one: the analysis, the classifications and the written verdicts must be yours.
Where an assessment involves a shared package or a partner (the merge in week 7, most obviously), the collaboration is expected and the rationale is individual. Two identical rationales for the same merge is the one case in this course where two near-duplicate files have an uncomplicated explanation.
Declare any assistance, including generated text, in the submission. A declared tool is not a penalty. An undeclared one is the integrity problem, in the same way an undeclared conversion step invalidates a format autopsy.
Your own files, and what you have to submit#
Two of the four assessments ask you to inspect files you already own. You are never required to submit a file whose contents you would rather not share. Where a filename or a document would disclose something personal, substitute it consistently, say in the submission that you have done so, and keep the substitution stable across the artefact. A renamed file is still evidence, as long as the renaming is disclosed and applied the same way throughout. Silently tidying the evidence is the thing that does not work, because the names are part of what is being examined.
Support#
For anything about the course as a whole, contact the convenor. For anything about a specific file, package or lab exercise, ask the tutor. See the People page for both.
If you are unwell or something has gone wrong, the university’s support services handle that, and reaching them is not conditional on telling a lecturer why. Contact the convenor about the deadline, and them about the rest.