Differences between revisions 2 and 7 (spanning 5 versions)
Revision 2 as of 2010-08-24 13:00:57
Size: 2202
Editor: KeH
Comment:
Revision 7 as of 2015-01-11 00:19:59
Size: 989
Editor: khellman
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
''Introduction to Computer Science'' is taught in an active learning style, as such we try to nurture and encourage collaboration within and between '''active learning groups'''. However, none of the problems, work, or assignments distributed to active learning groups is turned in for a grade. ''Introduction to Computer Science'' is taught in an active learning style, as such we try to nurture and encourage collaboration within and between '''active learning groups'''. However, none of the problems, work, or assignments distributed to active learning groups are turned in for a grade.
Line 7: Line 7:
'''<<Color2(red,For all graded work)>>''' in CSCI 101 the following ''CSCI 101 Collaboration Policy'' applies; it is essentially the collaboration policy for all courses in the MCS department.

 1. If the project is an individual effort project,<<FootNote('''Unless otherwise specified in writing, all CSCI 101 labs and assignments are to be individual efforts''')>> '''<<Color2(red,you are not allowed to give code you have developed to another student or use code provided by another student.)>>''' If the project is a group project, you are only allowed to share code with your group members.
 2. '''<<Color2(green,You are encouraged to discuss programming projects with other students in the class,)>>''' as long as the following rules are followed:
   1. You view another student's code only for the purpose of offering/receiving debugging assistance. Students can only give advice on what problems to look for; they cannot debug your code for you. '''<<Color2(red,All changes to your code must be made by you.)>>'''
   2. Your discussion is subject to the '''<<Color2(red,empty hands policy)>>''', which means you leave the discussion without '''<<Color2(red,any record)>>''' [electronic, mechanical or otherwise] of the discussion.
 3. Any material from any outside source such as books, projects, and in particular, from the Web, should be properly referenced and should only be used if specifically allowed for the assignment.
 4. If you are aware of students violating this policy, you are encouraged to inform the professor of the course. Violating this policy will be treated as an academic misconduct for all students involved. See the Student Handbook for details on academic dishonesty.
'''<<Color2(red,For all graded work)>>''' in CSCI 101 the following ''CSCI 101 Collaboration Policy'' applies; it is essentially the collaboration policy for all CSCI courses in the EECS department.
Line 17: Line 10:
Violations of this policy result in a course letter grade drop '''<<Color2(red,for all students involved.)>>''' Violations of this policy result in one of a range of punitive measures, from a zero score for an assignment, up to and including a course letter grade drop '''<<Color2(red,for all students involved.)>>'''

All issues of misconduct are reported to the Dean of Students.

Academic misconduct associated with an exam grade will likely result in course failure.
Line 19: Line 16:

----

<<Include(CollabDeptPolicy)>>

Working Together in CSCI 101

Introduction to Computer Science is taught in an active learning style, as such we try to nurture and encourage collaboration within and between active learning groups. However, none of the problems, work, or assignments distributed to active learning groups are turned in for a grade.

For all graded work

in CSCI 101 the following CSCI 101 Collaboration Policy applies; it is essentially the collaboration policy for all CSCI courses in the EECS department.

Violations of this policy result in one of a range of punitive measures, from a zero score for an assignment, up to and including a course letter grade drop for all students involved.

All issues of misconduct are reported to the Dean of Students.

Academic misconduct associated with an exam grade will likely result in course failure.


CSM Computer Science Collaboration Policy

The following policy exists for all CS courses in the EECS department. This policy is a minimum standard; your instructor may decide to augment this policy.

  1. If the project is an individual effort project, you are not allowed to give code you have developed to another student or use code provided by another student. If the project is a group project, you are only allowed to share code with your group members.

  2. You are encouraged to discuss programming projects with other students in the class, as long as the following rules are followed:

    1. You view another student's code only for the purpose of offering/receiving debugging assistance. Students can only give advice on what problems to look for; they cannot debug your code for you. All changes to your code must be made by you.

    2. Your discussion is subject to the empty hands policy, which means you leave the discussion without any record (electronic, mechanical or otherwise) of the discussion.

  3. Any material from any outside source such as books, projects, and in particular, from the Web, should be properly referenced and should only be used if specifically allowed for the assignment.
  4. To prevent unintended sharing, any code stored in a hosted repository (e.g., on github) must be private. For group projects, your team members may, of course, be collaborators.

  5. If you are aware of students violating this policy, you are encouraged to inform the professor of the course. Violating this policy will be treated as an academic misconduct for all students involved. See the Student Handbook for details on academic dishonesty.

Mines Umbrella Policy on Academic Integrity and Misconduct

The Colorado School of Mines affirms the principle that all individuals associated with the Mines academic community have a responsibility for establishing, maintaining an fostering an understanding and appreciation for academic integrity. In broad terms, this implies protecting the environment of mutual trust within which scholarly exchange occurs, supporting the ability of the faculty to fairly and effectively evaluate every student’s academic achievements, and giving credence to the university’s educational mission, its scholarly objectives and the substance of the degrees it awards. The protection of academic integrity requires there to be clear and consistent standards, as well as confrontation and sanctions when individuals violate those standards. The Colorado School of Mines desires an environment free of any and all forms of academic misconduct and expects students to act with integrity at all times.

Academic misconduct is the intentional act of fraud, in which an individual seeks to claim credit for the work and efforts of another without authorization, or uses unauthorized materials or fabricated information in any academic exercise. Student Academic Misconduct arises when a student violates the principle of academic integrity. Such behavior erodes mutual trust, distorts the fair evaluation of academic achievements, violates the ethical code of behavior upon which education and scholarship rest, and undermines the credibility of the university. Because of the serious institutional and individual ramifications, student misconduct arising from violations of academic integrity is not tolerated at Mines. If a student is found to have engaged in such misconduct sanctions such as change of a grade, loss of institutional privileges, or academic suspension or dismissal may be imposed.

The complete campus wide policy is available in the Student Handbook.

CollabPolicy (last edited 2015-01-11 00:19:59 by khellman)