Course Policies

[Nadeem Abdul Hamid]

Attendance Policy

Please see the Berry College Viking Code for "Class Attendance Policies" (pp 10-11, 2004-2005 edition). Missing three (3) or more classes without justifiable reason (and appropriate documentation) will be considered excessive absences.

Attendance records will be kept by the instructor. Sign-in sheets will be circulated every class period and attendance records will be kept from the sign-in sheet. If your name is not readable on the list, you will be marked absent. Signing for someone else will be considered a serious breach of academic integrity.

 

Academic Integrity

Students are expected to have read carefully and understood the rules governing breaches of academic integrity that are to be found in the Viking Code (pp 16-17) and the Course Catalog (pp 27-28, 2003-2005 edition). Be aware that, unless otherwise specified, all assignments, labs, and examinations in this course are expected to be done on an individual basis. When it comes to learning and understanding the general material covered in class or practice problems, you may certainly use other references and/or have discussion with other students or people outside this class. However, when it comes to work that is submitted for evaluation in this course, all such work must be entirely your own. The only exception to this is that you are very welcome to consult the instructor for assistance.

Furthermore, exercise extreme care that discussion of programming techniques does not result in collaborative efforts. If you discuss general programming techniques for solving a problem with other students or individuals, do not start writing any code of your own until you have engaged in at least half an hour of totally unrelated, non-computer work, to ensure that the code you write is entirely your own, and that you comprehend it completely. Program source code that is submitted for assignments and projects will be actively checked for being "too similar" to other students' submissions and to any other existing code. Copying programs and code from other sources and trying to just make minor changes therein will be detected and can result in severe penalties, up to and including an F in the course.

Here are some examples of acceptable collaboration:

As a general rule, if you do not understand what you are handing in, you are probably cheating. If you have given somebody some code simply so that it can be used in that person's project, you are probably cheating. In order to help you draw the line, here are some examples of clear cases of cheating:

When in doubt, ask the instructor.

 

Late Work

All exams must be taken at the announced date and time. Similarly, labs are to be completed and submitted at the scheduled time in order to receive credit. Homework or other assignments that are submitted late will be assessed a penalty of 5% per day late up to 5 days. These policies will be waived only in an "emergency situation" with appropriate documentation and/or prior arrangement with the instructor.

 

Disabilities

Students with disabilities who believe that they may need accommodations in this course are encouraged to contact the Academic Support Center in Krannert Room 326 (Ext. 4080) as soon as possible to ensure that such accommodations are implemented in a timely fashion. Failure to contact the Academic Support Center will constitute acknowledgement that no disability exists and that no accommodations are needed.

 



Last modified: Wed Sep 22 22:07:16 EDT 2004