CS 2073 Engineering Programming
Submitting Programs, Fall 2005

Rules:
  1. Each program must be submitted to me by email to the account:

    Use this special email address only for submission of programs for this course. For all other business or questions, use my "ordinary" email address:

  2. The subject header for the email should be the following for Program 1, and with 2, 3, etc. for later programs:

  3. Be sure to put the following at the start of your submission file:

  4. Each emailed submission should be a single text file (.txt or .text).   Absolutely no WORD, HTML, PostScript, or PDF files (no .doc or .html or .ps or .pdf files), or any other formatted or binary file. (It is just too confusing to try to cope with all the different forms that documents can take.)

  5. Each program has a full credit due date and time (usually Friday at midnight during the week after the program is listed on the calendar). After that there is a 75% credit due date and time (usually Monday at midnight during the week after the program is listed on the calendar). After that the program is not good for any credit.

    I intend to be strict about these deadlines. If some special problem comes up, that is what the 75% fallback credit is for, and if a special problem keeps you from meeting the second deadline, you just shouldn't have cut it that close, and it is only one out of 12 programs. In the end, you should send something to meet the deadlines even if it is not complete.

  6. Unless explicitly stated otherwise, programs must always be followed by the results of a run.

  7. Grading comments will be inserted using ALL CAPS, so you should not use these in your submission.

  8. Submissions for a program should not contain extraneous or excessive material, but should be limited to the program requirements.

  9. It is permissible to submit the program in time for the first deadline, and then to submit a better version in time for the second deadline. Your grade in this case will be the better of the two grades for the two submissions. In case of multiple submissions for the same deadline, only the latest will be graded, although all will be archived.

  10. Each program must be your own individual work. It is permissible to talk over programs with other students, or to get help from the instructor, but you must not supply code or answers to other students. It is completely unacceptable to exchange machine-readable portions of programs. Anyone providing such material is just as much at fault as a person using it. There will be significant penalties for submitting work that has been copied from someone else, and the same penalties for allowing someone else to copy your work. You should realize that the program files will remain indefinitely and can be examined at any future time, even after the semester is over. (See Plagiarism by Student Programmers for a discussion of copying by students.)

Revision date: 2005-08-29. (Please use ISO 8601, the International Standard.)