{'fraction_non_alphanumeric': 0.014145810663764961, 'fraction_numerical': 0.0, 'mean_word_length': 5.258503401360544, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Plagiarism Prevention is Discipline Specific: a view from Computer Science

Many of the good practice guidelines on tackling plagiarism and collusion are appropriate primarily for essays and research projects. Within Computer Science, particularly in undergraduate first year modules, much assessment is on understanding principles and techniques and applying these to example systems. This is true also of Engineering and Mathematical disciplines where there is a foundation of laws and theories that must be mastered and in general only one right answer to a problem. When assessing such knowledge and its application collusion is as much a problem as plagiarism. We suggest guidelines for the design of in-course assessments and the procedures that accompany them, all within the constraints of staff time and large student numbers. The use of discipline-specific examples will help in the adoption of good-practice.