CS 2604 Programming Assignment Submission Format Guidelines

Submit assignments to:  http://eags.cs.vt.edu:8080/curator/

• Project Archive Format
• Project Archive Contents
• Design Documentation
• Demonstrations
• Partial Credit

Projects that are not auto-graded:

Any CS 2604 programming assignments which are auto-graded must be submitted to the Curator as a single, uncompressed source code file. This requirement will apply to the "minor" projects which will not be demonstrated for the GTAs.  Submitting a zip archive or other similar file will result in a score of zero.

Projects that are auto-graded:

Any CS 2604 programming assignments which are auto-graded must be submitted to the Curator in a compressed zip archive format. This requirement will apply to the "major" projects which will be demonstrated for the GTAs.  Unix users will submit a standard gzip'd tar file.  The general requirements for contents are listed below, but be sure to read the specification for each project in order to get the correct details.

The deliverables that the submitted archive file must contain will be listed in each project specification. Generally, this will  include (but is not limited to) the following:

• Specified design documentation (if any) in MS Word (.doc) or Adobe Acrobat (.pdf) format.
• Source files (.cpp and .h) See Code Quality. Each .cpp and .h file must begin with a header comment block containing the following:
• name and e-mail address of programmer
• date of last modification of file
• Unix makefile
• One sample set of input/output files
• ASCII README.TXT file containing
• Your name and e-mail address
• The section of the course you're enrolled in (example : MWF 11:00-11:50)
• Your instructor's name
• The project name
• The platform and compiler you're using (example: gcc 3.0.1 under Mandrake Linux 8.1)
• Any special execution instructions. (If your program is not fully functional, be sure to mention that here and follow the directions in Partial Credit below.)
• The following Honor Code Pledge must be included in the header comment of your main source file.

//    On my honor:

//   

//    - I have not discussed the C++ language code in my program with

//      anyone other than my instructor or the teaching assistants

//      assigned to this course.

//   

//    - I have not used C++ language code obtained from another student,

//      or any other unauthorized source, either modified or unmodified. 

//   

//    - If any C++ language code or documentation used in my program

//      was obtained from another source, such as a text book or course

//      notes, that has been clearly noted with a proper citation in

//      the comments of my program.

//   

//    - I have not designed this program in such a way as to defeat or

//      interfere with the normal operation of the Curator System.

//

//    <Student's Name>

Any design documentation required will be mentioned specifically in the particular assignment. Be sure to check the assignments web page and read the FAQ.

Some programming assignments may require you to demonstrate your program to one of the CS 2604 TAs during a scheduled demo time. Even if project demonstrations are not required for all students, in the case of  a nonfunctional program, the TAs may require you to demonstrate your program during their office hours in order to receive Partial Credit.

To receive partial credit for programs that are non-working, or are not fully functional, a brief one or two paragraph description of the problem(s) must be included in the assignment archive in a text file named "PARTIALx.TXT"), where 'x' is replaced by the number of the project. The location, routine minimum, of each suspected problem/error must be specified along with possible corrections that need to be made.