CMPS 220 – Computer Programming I
Collaboration Policy

Spring 2001



You must write your programs alone, but you may discuss assignments and possible solutions with classmates.   If you discuss the assignment with others, you must report this accurately.  Not doing so is an honor offense.


You are taking this course to acquire knowledge, techniques, skills, and experience in the field of

Computer Science and software development.  Discussing the course content and completing the assignments facilitate these objectives.  Copying someone else's code hinders these objectives. 


Each student is responsible for his/her own learning.  The instructor provides a supportive and intellectually nourishing environment for learning to occur.  The instructor also assesses each student’s learning progress through assignments, in-class exercises, and tests.

General Policies:

All the rules of CofC's standard Student Honor Code are in effect. This document includes guidelines on how they apply in this course.

·         If you claim that you did some work, you must have actually done the work.

·         You can discuss the meaning of an assignment with others, both students and non-students. You can discuss how to accomplish the assignment. But, you have to perform the work yourself.

·         If you copy or adapt someone else's work, you have to acknowledge this. This includes, for example, a program someone gives you, a program from a book, and a program you find on the Internet.


Examples of Things You Can Do:

·         Ask the meaning of a term or concept.

·         Ask about the use of a software package.

·         Ask about the features and use of a programming language.

·         Ask "what do you think is wrong with this program?"

·         Receive advice from instructors, teaching assistants, or staff members involved in the course.

·         Share knowledge with other students about syntax errors, coding tricks, or other language-specific information that makes programming easier.

·         Engage, with other students, in a general discussion of the nature of an assignment, the requirements for an assignment, or general implementation strategies.

·         Compare, with other students, independent solutions to an assignment in order to better understand the nature of the assignment.

·         Engage, with other students, in discussion of course concepts or programming strategies in preparation for an assignment or examination.

·         Copy code and cite its source on assignments IF the instructor allows inclusion of code other than your own. 


Examples of Things You Are Not Allowed To Do:

·         Turn in the work of any other person(s) (former students, friends, textbook authors, people on the Internet, etc.) and represent it as your own work.

·         Knowingly permit another person to turn in your work as his or her own work.

·         Copy material (code, documentation, etc.) from the work of another student.

·         Deliberately transform borrowed sections of code or other material in order to disguise their origin.

·         Collaborate with other persons on an assignment and fail to acknowledge it.  Note: Past experience suggests that when students collaborate at the coding level, they learn less, and usually fail the tests.  So collaboration at the coding level is strongly discouraged.  However, if you choose to do so, you have to acknowledge it.


How to Report Collaboration:

Every assignment must include the following comment at the beginning:

Certification of Authenticity (include one of the following):

                   I certify that this assignment is entirely my own work. 

                   I certify that this assignment is my own work, but I received some assistance from:

                               <Name(s) of person(s) you worked with>

                               <Describe nature of collaboration – be specific!>



This policy has been adapted from similar policies at Worchester Polytechnic Institute and George Washington University as they appeared in the ACM SIGCSE discussion forum in Dec. 2000.