CS 2420 - Fall 2006

Eagle_System
(grading)

Requirements:

Grading:

You may be given an F if either your overall average is below 50%.  Remember, you cannot receive higher than a D+ if you haven't turned in all the programming assignments or don't have over 60% of the possible points on the programming assignments. 

If you haven't already, activate your computer account on the cluster.  All communication with you is done through this account.  Current scores can be checked at any time by going to the Eagle system.  Special announcements about the class are e-mailed to you, so it is suggested that you check your e-mail daily.

Course Outline:

Regrading: If you feel that a program, written assignment, or exam has been graded incorrectly, submit a concise written summary of your concerns to me.  These requests should be submitted within a week of the return of the assignment or exam.

Code Reuse: For this course, it is almost never appropriate to copy code from the book or another source.  When you graduate, you will often pull code from another source, but at this stage in your development, you need to write it!  I try to make the assignments different from what you can find in books or on the web, but sometimes that makes the assignments harder than I would like.  When I ask you to write code that has been written by thousands of others before you, you still need to write it so you appreciate it, so you learn the lessons contained therein.  You learn next to nothing by copying it from elsewhere. 

In English, if you are to write a paper, you are not allowed to find a good one on the web and turn it in.  In CS, it is a little different, because you are encouraged not to reinvent the wheel.  However, in this class, I want you to "invent the wheel.''  If you don't know how the wheel was build, you can't improve upon it.  Learning must be done in layers.  I can't teach you how to code exotic programs unless you have done the simpler things.  Writing the simpler things yourself - independently of the book - is necessary to form the correct foundation for what you need for later algorithms. 

In any course, you should never use someone else's product without clearly stating where it came from.  To use someone else's creation without giving them credit is cheating.  Here's the approach I would try.   Study the book.  When an assignment is given, try to do it without looking at anything.  If you can't, study the book again - but before you start coding, shut the book.  Then, you know that you have retained the most critical parts of the design. 

Cheating: Although you may collaborate on problem solving, each person must write, debug, and test his/her own work.  Some students feel that if they worked with the other person for a long period of time (as opposed to just copying another's work without any personal effort), they haven't cheated.  That is not true.  Note, you don't have to feel guilty for what you have done to have it be cheating. There are degrees of cheating.  Copying another person's code (with or without their knowledge) is cheating.  However, if another person helps you so much that the result isn't your work, then it is still cheating, regardless of how many hours you spent in the process.  Some think that because the course is demanding, it gives them license to cheat.  Nope!  Cheating is cheating.  There is no set of circumstances that justifies it. 

Submitting projects which include part or all of code/text that is obtained from sources such as a text book or a site on the Internet, without properly acknowledging the source(s) of the code/text in your submission is considered cheating.  In most cases, such "borrowing'' is not permitted, with or without proper acknowledgement.  In case of doubt, talk to me about your intention to include such code before using it. 

I do not recommend designing the code with others because it is difficult to pull yourself away from the group and do your own work.  For every problem you encounter, you want to know how others in your group solved that problem.  Copying code from the text or other sources (including tutors and consultants) is not allowed unless specifically indicated.  Do not allow someone else to write the code for you no matter how helpful it would be.  Cheating will be dealt with severely.  The penalty given is worse than not having done the assignment, written the program, or taken the exam (i.e., the least penalty possible is negative points).  When cheating occurs, a letter to that effect is placed in your file and a copy is sent to the dean's office.  Some excuse their cheating by saying "I was under so much pressure and just ran out of time.''  This is like saying, "I am honest until it is inconvenient.''  Cheating is not tolerated. 

Flagrant cheating involves turning in another's work as your own (even if that work was done by a tutor).  However, there are many other forms for dishonesty that are also considered cheating. Allowing others to copy from your work is considered cheating, and both of you will be penalized. Do not put your friends in an awkward position by asking them to help you cheat. If there are any questions, please refer to the departmental cheating policy.

Incompletes: According to university policy, incompletes are not to be given for poor performance. There will be no incompletes given except for conditions beyond the student's control. Such conditions have to have written documentation.  The term "conditions beyond the student's control" includes (1) incapacitating illnesses that prevent a student from attending  classes for a period of at least two weeks; (2) a death in the immediate family; (3) financial responsibilities requiring a student to alter course schedule to secure employment; (4) change in work schedule as required by an employer; or (5) other emergencies of this nature.  When an incomplete is given, it is anticipated that the remaining work will be finished within two or three weeks. If the course must be retaken to make up the work, an incomplete is not appropriate.  There are provisions in case of emergency to permit a student to withdraw (grade of W) from a course after the regular drop period when it is not feasible to give an I.

ADA Statement: If a student has a disability that will likely require some accommodation by the instructor, the student must contact the instructor and document the disability through the Disability Resource Center, preferably during the first week of the course.  Any requests for special considerations relating to attendance, pedagogy, taking of examinations, etc., must be discussed with and approved by the instructor.  In cooperation with the Disability Resource Center, course materials, can be provided in alternative formats - large print, audio, diskette or Braille.

Class Fees: Associated with this class is a fee of $25. The purpose of this fee is to supplement the department's operating budget to allow it to staff facilities and maintain the associated hardware and software that is necessary for this class.  While the student computer fee does cover a portion of the costs to operate some of the department's laboratories, the specialized requirements of this and other computer science classes require this additional funding.

Important Dates:
July 7 - last day to add
July 11 - last day to drop with a "W" notation
July 15 - last day to drop with "WF" on transcript

For problems or questions regarding this web contact the class lackey.
Last updated: August 28, 2006.