• Read my policy on collaboration. I will fail any student who cheats or plagiarizes in this class.
• You should read about the CS Department facilities.
• You will need an account on linux.cs.sonoma.edu for this class. If you do not yet have one, the Computer Science Department has instructions for obtaining one here.
• Create a directory in your linux.cs.sonoma.edu account for all your work in this class. In order to comply with Computer Science Department policy, set the permissions of this directory to 700 so nobody else can access it. (Consult your Linux reference manual to see how to create a new directory and change the permissions on it.)

Program Preparation and Submission

nnn_yourlastname_m.v

where:

nnn is the course number, e.g., 250

yourlastname is your last name

m is the project number, starting with 1

v is the version number starting with 0

Do all your work for the program inside this newly created directory. When you are ready to submit your program you will create an archive of the entire directory, compress the archive, and send it to me. So make sure that you keep all your work organized.

For example, all the files for Robin Smith's first assignment for CS 250 should be kept in a directory named 250_Smith_1.0. If Robin creates a second version of this program, Robin will create a duplicate of the directory, along with all the files in the directory, and name the duplicate directory 250_Smith_1.1.

1. A file named "README."
   This is a discussion of the program, including
   • a list of the files included in your submission.
   • the test data you will use to determine if the program is working correctly, and
   • a list of unimplemented features (as specified in the assignment) and other anomalies in the program.

   IMPORTANT: No credit will be given for any program submitted without a README file (unless noted in the assignment).

2. All the source, header, etc. files needed to create your program. (Except, of course, the system files.)
3. A makefile.
   I will start the test of your program by using the Linux commands

   	make clean
   	make
   

   So your makefile must be designed such that this produces the desired results.

1. Leave only the required files in the directory named nnn_yourlastname_m.v. Delete any other files (e.g., application, .o) before you submit your project folder.
2. From the directory immediately above this one use the commands:

   	tar cvfz nnn_yourlastname_m.v.tar.gz nnn_yourlastname_m.v
   

   (Read the man pages for tar and gzip to learn what is being done here -- and to learn how to read man pages!)

   The resulting compressed archive (.tar.gz file) is known as a "tarball."

Creating and submitting an updated version

1. If the revision does not work, you still have the previous version.
2. When I extract your program from the archive, the directory is created with all the files in it. If you do not use a different name, this process will write over the previous version. This makes it difficult for me to keep track of the programs.

Required documentation

1. the name of the file,
2. a very brief description of the contents of the file,
3. the author's name, and
4. a dated history of the major modifications made to the file.
   Most of the time this will be one date -- the date that you complete the file.

Approximate Program Grading Criteria:

Solutions

I generally will not post solutions to programming projects. If you are unable to complete a program by the time it is due, submit what you have completed. But you are still responsible for figuring out how to complete the project.

The point is to learn how to solve the problem, not how to copy someone else's (my) solution to the problem. You can, of course, ask me questions about how to solve it.

Useful Information

• If you have never worked in a Unix environment, look at Some Basic Unix for the minimum Unix commands you need to know.
• C++ to C provides very brief discussion of C programming for C++ programmers.
• makefile describes the basics of the Unix make facility.