Grading Standards for CSC 2/454

Most programming assignments will have two due dates.  The first will be a trivial “pre-assignment” whose purpose is to force you to start thinking about things.  The second will be the main due date.  There will also be frequent in-class quizes.  These will resemble the “Check Your Understanding” exercises in the textbook; doing those questions as part of your class prep should ensure that you get a good score.  Finally, there will be an in-class midterm exam and a cumulative final during exam week.  Several past exams (with suggested answers) are available on-line as study aids. 

End-of-semester numeric scores will be weighted roughly as follows: 

Letter grades will be assigned by subjectively identifying brackets in the numeric scores.  There is no pre-determined grade distribution.  In particular, I have no objection to giving all high grades (or all low grades) if it seems appropriate.  As noted on the policies page, extra credit will be available on many of the assignments and the exams; it you do enough, it may move you up a grade.  Five students (out of 81) benefitted from this in 2016; three (out of 63) in 2015. 

Programming assignments will be handed in electronically using the script ~cs254/bin/TURN_IN on the CSUG network.  You should run the script in a directory containing: 

  1. A copy of (all files of) your source code. 
  2. A listing of the output of your code on your own test data, and on any official test data provided by the TAs.  You may find the script program useful for capturing output; read the man page. 
  3. A README.txt or README.pdf file (see below). 

Be sure to remember the no late assignments policy.  If you don’t manage to complete the assignment on time, turn in what you have.  I will be very generous with partial credit.  If you don’t turn in anything by the due date, you will get a zero. 

Be sure to check Blackboard frequently for any additional instructions from the TAs or instructor. 

We will strive to grade assignments within one week of the due date, at which point grades will be available to you via Blackboard.  Additional information may be sent to your official University email account.  If you have any questions about your grades, please consult the Grad TAs.  If they are unable to resolve the issue, come see me.

README files

Your README file for each assignment should contain whatever information you think is necessary for a typical user to run your program and for a software maintainer (or grader!) to understand (and evaluate) your code.  Much of this information may be included on the original assignment web page; you only have to fill in the parts we didn’t provide for you already.  Information for the prospective user includes details on calling conventions, input and output data formats, limitations, bugs, and special features.  Explain both the negative aspects of your program (limitations, known bugs) and the positive aspects (extensions, special features).  If you don’t include the former, we will assume you didn’t realize the limitations were there.  If you don’t include the latter, you may not get extra credit.  For the person who has to understand the insides of your code, you may need to describe your choice of modularization (abstractions), data structures, and algorithms.  Be sure to explain anything you did that is likely to be different from what other students may have done, and justify any design decisions for which the rationale isn’t immediately clear.  Your write-up should be clearly written, using full sentences and paragraphs.  This writeup need not necessarily be long, but it is important.  All writeups must be in plain text (README.txt) or Adobe PDF (README.pdf) format.  Other formats (e.g., Word, Open Office, or postscript) will not be accepted. 

Grading scale

For each programming project, points will be divided roughly 80/20 between the code itself and the external documentation (README file).  A more detailed breakdown follows: 

You are encouraged to share ideas with fellow students, but only one person or team can get credit for actual code (see the course rules for academic honesty). 

Last Change:  05 December 2019 / Michael Scott's email address