Program Assignments
The purpose of this handout is to identify precisely what should be handed in
for programming assignments in this class. At a minimum, there should be two
or more items of information: the program source code (or listing), a program
output (when appropriate) and a program (file) that was the input (when approperiate).
The program listing should be the "list file" produced by the compiler
(if the compiler produces such a listing otherwise, a "printout" of
the program's source file is adequate). If these outputs are on fan-fold (continuous
feed) paper, do not burst (separate) the pages, but leave them as they came
from the printer. If a banner page is attached (the heading page that identifies
the owner of the printout), do not tear it off. (If necessary, fold the pages
so that the first page appears face-up.) Be sure to clearly label the "printout"
with your name, course, and program assignment number on the first page of the
program using the format below.
In the heading comment section surrounded by the multiple line comment delimiters
please include the following information:
/*
last name, first name
Course Number -- CSC 111
Program Number: #? (number of program that coincides with the assignment)
Grade:
Comments:
*/
Example for determining the grade of the program::
In addition to the information described above, for all programs handed in for
this class, the following evaluation information should be provided: the total
time expended working on the problem. This included design time and implementation
time [time spent away for the computer designing the program, as well as time
spent at the computer getting the program to work]. Any class time spent on
the program should also be included: this would include time devoted to the
program, whether in the classroom or the laboratory.
| Grade: the grade you feel is deserved for your efforts on this program. The grade is to be expressed on a scale of 100 points possible, according to the following criteria: | ||
| 100 | A+ |
This grade is only given by the instructor or grader for an exceptional program. |
| 99-91 | A |
Program follows correct program structuring guidelines and is produces a correct output. |
| 80-89 | B |
Program follows correct program structuring guidelines and as runtime errors, or is producing incorrect output. |
| 70-79 | C |
Program follows correct program structuring guidelines and as compiler-time errors OR the program is producing the desired (correct) output but DOES NOT adhere to proper structuring guidelines. |
| 60-69 | D |
Program exists in some written form (typed or handwritten) but has not been compiled. |
| 0 | F |
Only rough notes have been made or nothing exists. |
| Note: |
Working status provide a brief statement identifying the working status to the program. Are there compile-time errors? Runtime errors? Incorrect output? | |
Comments are optional. A comment is your opportunity to provide whatever additional input you feel should be made concerning the evaluation of your program. This is where you can highlight any special features of your solution for the problem, and/or to mention any problems encountered that you managed to overcome.
In addition to the comments relating to the program, there needs to be adequate comments throughout the program that explains the various sections, variables, classes, etc. These comments may be single line or attached to the end of a line using the // format or multiple lines using /* */delimiters.
If you have any questions, please contact either me or Joel Anderson.