Agenda for Teaching Committee Meeting 9 November 2001


Special Meeting on Plagiarism Policy

Preamble: Following the meeting of the TC on 12 October 2001, where, following failure to make progress on plagiarism policy, this issue was referred to the Head of School for advice. He recommended that the TC should consider, in a meeting with discussion limited to one contribution per person (and if necesssary with a time limit) a series of motions more clearly formulated than is normally the case in many CSE meetings.

The motions below are intended to fill this role. Suggestions for improvements are welcome.


  1. That the School of Computer Science and Engineering shall use laboratory programming examinations in first and second year programming courses, where feasible, as hurdles to prevent people without appropriate programming skills from passing those courses.

    Where this is not feasible, examination questions shall be included that test understanding of assignment material.


  2. That the School of Computer Science and Engineering shall provide a clear definition of plagiarism as opposed to acceptable cooperation. This definition should be available

    1. as part of the yellow form,
    2. separately as a School Plagiarism Policy web page, and
    3. linked to each course web page

    Where aspects of the School Policy are inappropriate (as might occur in course with group project rules or other cooperation rules), the course web page and introductory handout shall detail the differences.

    The language used in communicating plagiarism rules to students shall be "matter-of-fact" rather than threatening.


  3. That the School should establish a plagiarism working group, including interested staff, postgraduate students, and COMPSOC representation, to try to ensure that the plagiarism detection methods in use in the School are as strong as possible.


  4. That the School of Computer Science and Engineering shall implement a standard plagiarism penalty of 0 FL for any recipient of a substantially copied assignment and a standard penalty of loss of all marks for the assignment for any originator. Lecturers shall have discretion as to whether to apply the full penalty. If they do not apply the full penalty, they may apply a lesser penalty, or they may reprimand the student.

    The term "substantially copied" is defined, for the purpose of this resolution, to mean that a significant proportion of the assignment is copied. It would not apply to copying of a single, small function, unless in the lecturer's judgment that function was the core of the assignment. It would certainly apply to an assignment of which 80% or more was copied. Intermediate cases lie within the lecturer's discretion.

    The basis of the School's Plagiarism Policy is that the intention of assignments and other set works is to ensure that the student learns certain facts and skills. The penalisation of plagiarism is to be seen against this background, and cases where students copy but understand the material that they copied are to be seen as less serious than cases where the student does not understand the copied material. It is likely however that an "understanding" copier will not have fully learned the skills involved in producing the copied code.


  5. That the School of Computer Science and Engineering shall implement a central database of persons penalised or reprimanded for plagiarism. The database shall record details of course, session, lecturer, originator(s) and recipient(s), record of the proceedings that determined that plagiarism had occurred, what factors were considered if the full penalty was not applied, and notes on the similarities. Machine-readable copies of the original a copied programs shall be kept where available, otherwise hard copies shall be kept. This database shall not be available to academic staff, but shall be managed by the School Student Office. The protocol for its use shall be that when a new, complete record of plagiarism for a student is entered into the database, previous records for the same student(s) shall be retrieved. Multiple offences discovered in this way shall normally be reported to the Deputy Registrar.

    Students shall have access to their own record (if any) in such a database, on request, and a right to have proven errors of fact in their record corrected. If such errors of fact meant that a previously applied penalty was inappropriate, then the penalty shall be reviewed. If errors of fact meant that there was no plagiarism, then the record shall be expunged.


  6. That the School of Computer Science and Engineering shall not normally employ as a casual academic, a person who has been recorded in the School plagiarism database as having been penalised as the originator or recipient of an assignment. Note that students reprimanded rather than penalised may be employed.

    This rule may be set aside in an individual case by the Associate Head of School or another person designated by the Head of School. This might occur, for example, if a student who was convicted once in first year and who subsequently had a superlative academic record with no further breaches of plagiarism rules, applied to tutor in their fourth year.


  7. That members of the School of Computer Science and Engineering shall apply the following constraints when investigating suspected plagiarism offences:

    1. If students are interviewed, there shall be more than one staff member present at the interview, and a record of the interview shall be made, and a copy provided to the student. The student must sign to acknowledge that they have received the copy. If they refuse to accept a copy or to sign, the staff members attending the interview shall state this in the record of interview. The staff members attending the interview shall sign the record of interview.

    2. In conducting an interview with a suspected plagiarist, members of the interview panel shall not use intimidatory techniques or intimidatory language. It is legitimate to confront students with conflicting statements that they have made, or with a conflict between their statement(s) and their submitted material, or with a conflict between statement(s) that they have made and statement(s) that another involved student has made.


  8. That the School of Computer Science and Engineering shall permit students found to have committed a plagiarism offence to appeal against the conviction or the severity of the penalty, under the following conditions:

    1. The student shall appeal in writing, stating the nature of the appeal (conviction or severity of penalty) and the grounds of the appeal.

    2. The initial avenue of appeal shall be to the lecturer-in-charge of the course. If the matter is not satisfactorily resolved, the student may appeal to the School Grievance Officer.

    3. If the appeal is upheld, the plagiarism penalty and the plagiarism record shall be amended.

    4. An appeal shall be deemed frivolous if no relevant extra material is produced in connection with the appeal document, or if the relevant extra material could reasonably have been produced in the original consideration of the plagiarism offence. Neither the fact of conviction nor the severity of the penalty shall be varied in the case of a frivolous appeal.

    5. Appeals shall be recorded in the record in the plagiarism database together with the outcome of the appeal, factors relevant to the outcome, and in particular whether or not the appeal was deemed frivolous.

    6. An academic, being the Lecturer-in-Charge, the student's Program Director, School Grievance Officer, or Head of School, may instigate a review of a plagiarism case on becoming aware of new facts in relation to that case. The review would be conducted by the original panel, supplemented by the academic instigating the review if s/he wishes to be involved.


School of Computer Science & Engineering
The University of New South Wales
Sydney 2052, AUSTRALIA
Phone:  +61 2 9385 6876
Fax:    +61 2 9385 4071