Dr. J's Programming Assignment Policies for Upper Division Courses

1. All source code must have your name in it. This includes project files, header files, script files, etc. that pertain to a Programming Assignment.
2. Unless otherwise specified, any generated executables should have the name progn, where n is the program number.
3. All projects must run correctly in the environment it was designed for (e.g. PC platform or Unix).

Disk Submissions (for PC platform only)

• All source code connected to a programming assignment will be submitted in either a 3.5" diskette or CD. Your name must also be clearly written on the disk label. (Large programs that will not fit in a diskette have to be submitted in a CD.)
• Successfully completed Assignments should come with an executable file and anything necessary for the code to run (e.g help files and other text files, sample data, etc.). Your programs will still be recompiled during the evaluation process.
• It is your responsibility to guarantee that your disk is virus-free.
• Disks must be housed in a secure pocket or compartment as part of the Documentation (see below)

Electronic Submissions (for UNIX platform only)

• All source code connected to a programming assignment must be submitted electronically to the (lab) instructor by the due date and time in order to receive any credit points. Check with your (lab) instructor for procedures for electronic submissions (which could be done either through electronic copying to a shared public directory, or via e-mail).
• Electronic submissions should include a make file to facilitate compilation of your Assignment. Do not include any binaries (executables, object files, a.out files, core dumps, etc.) in your e-mail submissions.
• It is your responsibility to guarantee that your electronic submission is complete and includes all the necessary files to successfully compile and run/test your programs.

1. Cover page (indicating the course name and number, programming assignment number, due date, your name, etc.; be sure to also indicate the platform the assignment was designed for and the compiler (and version used)
2. A signed and dated copy of the Programming Assignments Contract and Pledge sheet
3. Brief statement and description of the problem (in your own words)
4. Solution/Algorithm used (including pseudocode, structure chart, object hierarchy, etc.)
5. Acknowledgements (optional) - a list of names of people that may have contributed to the successful completion of the assignment
6. List of references (on-line sources, manuals and/or books used as a reference)
7. User manual (at least 1-page of instructions on how to run your program, explanations of any additional features, recommendations, etc.; assume this is being written for readers that may be computer illiterate)
8. Printouts of all related source code and sample data files (whenever possible, print two pages on a sheet in landscape mode to reduce the number of pages of code)
9. Sample runs showing ALL pertinent features of your program (optional)

Dr. J reserves the right to determine the format that the documentation described above will be used. There are two formats - be sure to check which one(s) is/are required by your instructor:

1. Printed documentation. Your documentation must be securely bound using a neat and presentable folder. Please do not use letter-size envelops or ring binders. Continuous-feed printouts must be separated into individual sheets with the tractor guide on both sides removed.
   
2. Online documentation. Your documentation must be accessible through the Web via a Web browser. All parts listed above must be made available. Additionally, program design/structure must be detailed through the use of a documentation generation system such as javadoc, Doxygen, or DOC++.

All students are responsible for maintaining copies of all files submitted. This guarantees the existence and availability of back-ups in case some or all of these files get accidentally modified or deleted during the evaluation process.

Students must adhere to the level of professionalism characterized by the requirements above. At this stage in their academic program, students are also expected to turn in programs that compile successfully. Programs that do not compile will automatically get a maximum of 50% credit and the Instructor is at liberty to decide not to go through any of the accompanying documentation. Programs that crash during testing will get a maximum of 75% credit.

Alternately, students may use e-mail when trying to get in touch with the Instructor concerning matters related to class work. You can send e-mail to Dr. J at Juliano@ecst.csuChico.edu.

Do not cheat! Do not copy others work! Learn the material. The benefit and enjoyment you will receive will be much more valuable than any consequences of cheating. The instructor will use electronic means to detect plagiarism/collaboration (e.g. MOSS), and to check for cheaters on every assignment! Individuals who misrepresent work as being their own or who have assisted another will receive, on the first offense, a minimum penalty of a grade of zero on that assignment and a decrease of one letter grade on their final course grade. On succeeding offenses, students will get the minimum penalty of an F in the course and a memo concerning this included in their academic folder. The Dean of the student's major may also be notified with the recommendation of expulsion from the University.

Please refer to the University Policies and Academic Policies and Regulations, as written in the University Catalog, for more information regarding CSU Chico's Student Code of Conduct and Academic Responsibility. Students are also expected to be aware of CSU Chico's Policy on Use of Computing and Communications Technology. Ignorance of these Guidelines is no excuse!