plagiarism
assessment
registry
papers
software
links
discussion

Reassessing the Right Students Peter Tischer

We need to distinguish between detecting plagiarism and detecting when students do not deserve credit for work they have submitted. We ask students to do practical work because we want them to learn something. The mark they receive should be related to what they learned from the exercise. A student can defeat a plagiarism detector by getting someone from outside the system to produce a one-off assignment.

The only way to defeat students who submit work which gets a high mark but who have not learned anything in producing this work is to interview the student to see what they have learned. We do not have the resources to interview every student but we can interview some students. Instead of taking a random sample we can try to concentrate on students who are most likely to have learned far less than the assessment mark would indicate.

There are two main ways we can identify these students. One way is via plagiarism checking. The other way if from the history of the student. The student may have infringed in the past and is under probation. Another history approach is that a student's performance in examinations might be very much worse than their assessment for practical work. The students often show that they may have got a high mark for practical work but that they also have not learned what they were expected to learn from doing the practical work.

These two approaches involve maintaining information across subject boundaries. If a student gets 90%+ for prac work and then gets a substantially lower mark in the exam, the student can be marked as someone who is more likely to be asked in for an interview for subsequent prac work. If it appears that we are targetting specific groups of students we can still interview some students at random. The good students might actually appreciate the higher degree of feedback.

Plagiarism Prevention and Deterrence Heinz Schmidt

While plagiarism detection can be deterrent and is welcome by many students to level the playing field, it is always advisable to test knowledge of submitted work in other contexts. For example, if students are asked to apply particular programming templates or idioms used in pracs, then internet sources are less likely to serve as solutions. If students are asked to present key points of their assignment in class and respond to questions by peer students and tutors, they are more likely to learn and come prepared. If students know that they are expected to address key points of an assignment in the final exam, one would also hope they are more likely to invest the time in the assignment in the first place.

Despite a culture of learning and assessment for learning, there always has been and will be some plagiarists. With the ease of plagiarism supported by the internet, unfortunately, professors, who ignore such plagiarism in work assessed for final grading, play into the hands of plagiarists. More importantly, they may also send the wrong signals to other students. However, without tools, detecting such plagiarism is very time consuming.

Systematic plagiarism detection is a deterrent for plagiarism, if students are aware that it is routinely performed on assignments submitted for marking. Especially, if assignments are not just compared within a class or year but against large databases holding many assignments over many years, assignments are much less likely to be recycled from one year to the next and passed on from one university to another.

The deterrence grows with the accuracy of detection and the variety and spread of material in the databases. Modifications capable of beating plagiarism detectors eventually require too much creativity, understanding or simply become too time consuming compared to actually learning. For example the algorithms used by the plagiarism.org service are claimed to increase the likelihood of detecting plagiarism when work from two or more texts are mixed and merged:

Interviews Martin Dick

In 1996, it became bleedingly obvious, that wholesale cheating was going on in one of our subjects, partly due to students setting up their Unix accounts as world readable and thus allowing other students to roam directories looking for good assignments to copy, partly due to students looking in the Windows recycle bin for assignment copies etc.

To counter this we instituted assessment by interview. This has been done since. These are subjects with approx. 300 students and a corresponding number of tutors allocated to the subjects. The interviews are performed by tutors. Initial tutor training is part of package and parcel. It has in our opinion significantly dropped the amount of cheating and in most cases where cheating occurs results in a very much reduced mark or a fail for the student.

Two interviews are conducted which take on average between 30 and 40 minutes. Each tutor is allocated 2 hours of marking time per week or 26 hours in total for the subject for the semester. If we dropped interviews and did normal marking on the assignments, it would seem reasonable from my experience that to give the students appropriate written feedback, that the times would be roughly equivalent. Assessment by interview helps us in a number of ways

  • reduces cheating by drastically reducing the advantage of cheating
  • provides immediate and verbal feedback to students on their work
  • helps the student to understand where they have gone wrong
  • reduces the number of disputes over marks
Where practical programming assignments are involved there are numerous tools available which are quite sophisticated in detecting plagiarism. Such tools can help target and prepare for interviews.

Random Interviews David Squire

Random sampling is a perfectly feasible ways to handle assessment by random or targeted interview where the effort of interviewing all the respective students cannot be justified.

Some universities use random interviews scheduled at a fixed time each week. Let's say there is an all-day prac. each Thursday. Friday morning at 9:00am a list goes up of all the groups who will be interviewed that morning. The idea is that since you never know whether or not you will be interviewed, you always have to be prepared for it.

Passing such prac. interviews can be used as a hurdle requirement rather than making a numerical contribution to the final mark.


 

Copyright © 2000-2002 Monash University - Credits: All Rights Reserved - Disclaimer: No warranty of integrity of these pages.
Please contact Heinz Schmidt, to submit any errors or improvement suggestions for this page.
$Id: assessment.shtml,v 1.7 2002/02/09 03:42:34 hws Exp $