CompSci 6: Program Design & Analysis I(Fall 2009) | |||||||||||||||||||||||||||||||||||||||||
|
Schedule
Starter CodeMost assignments will include code to get you started. This may consist
of completed classes that you will utilize but not modify or
classes in which some methods have been completed and others
are left for you to fill in. In either case, comments will
clearly indicate which sections of the code you may edit and
which must not be modified (you can go to these sections
directly by using the http://www.cs.duke.edu/courses/cps006/fall09/snarf/ Assignment SubmissionAll assignments must be turned in on the due date given; if your assignment is received after midnight (i.e., the next day), it is considered late. You are responsible for ensuring that all files are turned in on time, if a program is turned in late there is a penalty detailed online here. When you are done with your project and are confident it is satisfactory, you should submit it electronically using the directions available here. You may submit an assignment as many times as necessary, but only the files included in the last submission will be graded. Thus, you should always submit all your project's files -- even if they have not changed since a previous submission. Note, the official time of submission for your project will be the time of your last submission. An assignment will be considered late if any submission is late, even if your first submission is on time. You may lose points on your assignment if your final submission is incomplete or late. README GuidelinesEvery assignment submission must include a plain text file, named README or README.txt (please use all capital letters in naming the file), that includes the following information:
You may lose points on your assignment if it does not include a proper README file. Within Eclipse, you can create plain text file by choosing Code StyleFinally, note that a significant portion of your assignment grade is based on the readability of your program. This readability grade includes style, comments, and the naming of variables and methods. You must include a comment at the top of each source file you modify that includes your name, course and purpose of the class specified. For example: // Name: YOUR NAME HERE // Course: CompSci 6 // // Purpose: // PURPOSE OF CLASS HERE |
||||||||||||||||||||||||||||||||||||||||
| Last updated Wed Nov 18 22:37:54 EST 2009 | |||||||||||||||||||||||||||||||||||||||||