(Latest Revision: 05/16/2002 ) prog_3_ResultsByCode

prog_3_ResultsByCode


This file shows grades on program #3, along with indications of the problems and point deductions.

Find your code number below.

Look at the the codes, scores, and comments below your code number.

Next see the "Legend" near the bottom of the page to determine the meaning of the codes.

See me if you have any questions, if you find an error, or if you want further explanation of your grade.

0197: 0570: 2305: 2727: 7015: 7169 7422: 7883: 8786: 8991: 9317:

======================================================
Legend
======================================================
Generic Types of Problems
--------------------------

G01. Program was late (Level Two Due 03/28) (Level Three Due
     04/16) (Final Level Due 04/23) (-10% per day)
G02. Program was too late to be accepted (-100 pts)
G03. The correct subject line was not used. (-2 each message)
     "CS2500,prog3.2", "CS2500,prog3.3", and "CS2500.prog3.f".
G04. Program does not compile (up to -100 points)
G05. The program does not use functions appropriately. (-10)
G06. The program uses a global variable inappropriately (-5)
G07. The program does not make proper use of parameters. (up to -20)
G08. The program does not make proper use of return values. (up to -10)
     (-1 for each function that should be void but is not)
     (-3 for each function that fails to return a value and thus
     creates a logical error)
     (-1 each for extra return statements in functions)
G09. Function or variable does not have a mnemonic name (-2 each)
G10. Header comment before main program missing. (-3)
G11. Header comments before functions missing or have the wrong
     kind of content. (up to -5)
G12. There are no header comments (or almost none). (-10)
G13. Code is not indented properly (For each line that is not
     indented from its enclosing brace by two or more spaces, -1
     point, up to a max of -5.  A point is taken off also when
     there are two lines that should have the same level of
     indentation, but do not.  The "{" and matching "}" should be
     at the same level of indentation.)
G14. Program and output does not fit into a field width of 78
     characters. (this tends to make it harder to check and
     test -- and print too.) (-3)
G15. No test script was received. (-15)
G16. Script does not evince an effort to achieve good code
     coverage. (up to -10)
G17. Script does not evince an effort to cover boundary values
     adequately. (up to -4)

======================================================
Assignment-Specific Problems
--------------------------

S01. The program does not recognize non-taxable items (-5)
S02. The program does not print a pre-tax sub-total. (-2)
S03. The program does not catch the dup-num-in-invent-file error. (-3)
S04. The program does not catch the product-does-not-exist error. (-3)
S05. The program does not catch the quantity-out-of-range error (-3)
S06. The program uses an incorrect name for the invent, transac,
     or receipts file. (-3)
S07. The program does not compute the tax correctly. (-3)
S08. The program does not compute the total correctly. (-3)
S09. The program outputs to cout instead of the receipts file. (-3)
S09. There is a problem with the format of the output. (-3)
======================================================