Date: Mon, 02 Dec 1996 14:26:41 GMT Server: NCSA/1.4.2 Content-type: text/html CSE 143 Turn-in Policy

CSE 143 Turn-in Policy


This document explains the turn-in policy that will be used for CSE 143 this quarter. On all programming projects, you will be required to turn in two things: a hard copy of your solution, and a copy on 3.5" disk. The hard copy will allow the TAs to scribble comments on your code and output, and write down your grade. The disk will be used to run your program and verify that it works. Each component is explained in more detail below.

Hard Copy

In general, the submitted hard copy should contain (i) a cover sheet, (ii) your code, and (iii) output showing the result of running your program on a few well-chosen test cases.

Disk

The disk you turn in should be labelled to indicate which of the four supported platforms it should be run on: Remember that if you develop on another platform, it is your responsibility to make sure that your source code works on one of the supported platforms before submitting it, and that you supply us with an executable for the supported platform.

The disk should contain the source code, test cases, output from the test cases, and executable that make up your program. In general, this will mean copying the folder or directory that you're working in onto the floppy disk. Since this will typically involve many files, you should place a README in the disk's top-level directory, explaining what all the files are. If we can't find them, we can't grade them. A sample README is located here, although any format is fine as long as it expresses the important information concisely.

In general, we should be able to just pop in your disk, consult your README file, and run the program. In addition, you should supply everything that is required to build the executable (although we shouldn't ever have to do so, since you've supplied a copy of it).

UNIX users: Since most UNIX machines don't have a floppy drive attached to them, your best bet is to tar up your working directories, ftp them to a Mac or PC, and save them to disk. Your README should make it obvious how to reverse the process. You should also specify what machine your executable was made on. If you'd like to discuss alternate turn-in arrangements, please consult with your TA.

Other Questions?

If you have other questions about the turn-in, procedure, please discuss the details with your TA.


cse143-webmaster@cs.washington.edu