As we work together to battle the coronavirus, we will continue to offer safe and secure online sessions . Even though our physical office is closed, in accordance with the guidelines recommended by CDC, we are working remotely and continuing to provide student, staff, and faculty assistance. We can be reached Monday-Friday 9am-4pm Mountain Standard Time at 520-621-3565 or by email – please refer to the iSchool Directory. Please allow up to 24 hours response time. Faculty and Adjuncts will respond as their schedules permit.
iSchool Extension of the Code of Academic Integrity Involving Programming
This document is addressed to all students enrolled in either undergraduate or graduate courses at the University of Arizona School of Information. Every student enrolled in our programs is expected to be aware of and adhere to the University's policies on academic honesty as described in the University’s Code of Academic Integrity in computer programming projects and exercises. The guidelines given in the current document are the official Departmental policy on academic dishonesty and plagiarism in programming projects and exercises. They represent an extension and clarification of the University's policy on academic dishonesty as it pertains to the special situations arising in computer programming projects and exercises.
For collaborative assignments, as an extension of the Code of Academic Integrity, one of the following policies will be adopted regarding how much cooperation and joint work is permitted in each of these classes:
A. Students are to work on their programming assignments without consulting with anyone that is not explicitly approved by the instructor (such as a grader or tutor). Default policy unless otherwise specified in writing by the instructor.
B. Students are allowed to discuss the meaning of programs or problems together but are expected to work totally independent of anyone that is not explicitly approved by the instructor when working on the solutions to a program or problem and when doing their coding.
C. Students are allowed to discuss the programs or problems or to work on the solution together, but are expected to work totally independent of anyone that is not explicitly approved by the instructor when doing their coding.
D. A clearly identified group of students may work together in developing solutions to a program or problem, and are to turn in their work as joint work with all their names included, indicating co-authorship.
E. The instructor distributes a written policy (possibly as a part of their syllabus) that specifies how much cooperation and joint work is permitted on their programming assignments.
Policy A is the default policy that will be used unless the instructor specifies otherwise in writing (e.g., in their syllabus or in assignment instructions) indicating that one of the other policies will be followed. Violation of this policy will result in reporting to the Dean of Students and activate regular reporting processes for academic integrity violations. Students are to clarify with their instructors any questions they may have about how much cooperation and joint work is permitted on programming assignments.
In cases involving cheating or plagiarism, a person who knowingly assists another person in cheating or plagiarism is considered as guilty as the person receiving help. Using solutions or code from a problem assigned in a previous semester without the explicit permission of the instructor is also considered to be cheating or plagiarism. It is each student's responsibility to place protection on their files containing assignments, avoid leaving their computer account open in the labs when they are not present, protect current and old printouts of their code, and take other reasonable precautions to ensure these files are not accessible to another student. A student who becomes aware of cheating is strongly encouraged to report this matter. It is important that the students and instructors work together to achieve an academic environment that is fair to all students.