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

You are required to have a user account on the College of Engineering Computer Science and Construction Management (ECC) Unix server.

Program Files

For any credit, ALL source code must have your name in it. This includes project files, header files, script files, etc. that pertain to a Programming Assignment. Output from executable programs must display your name (as author of the program), course name and number, and semester.
Unless otherwise specified, any generated executables should have the name progn, where n is the program number.
All projects must run correctly in the operating environment it was designed for.

Electronic Submissions

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 specific procedures for electronic submissions. The preferred form for electronic submissions is copying all your programming assignment source code to /user/projects/juliano/your_userid on tiglon, our College of ECC Unix server.
Unless otherwise specified, you are responsible for creating and maintaining a folder/subdirectory for each programming assignment within your turn-in directory. The convention is to use the folder/subdirectory name Progn, where n is the program number.
Electronic submissions may require a Makefile to facilitate compilation of your Assignment. Do not include any binaries (executables, object files, a.out files, core dumps, etc.) in your electronic 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.

Documentation

Early at the beginning of the semester, every student is required to complete, sign, and date a Programming Assignments Contract and Pledge sheet. A student's programming assignments will not be graded if the student dodes not have a completed, signed, and dated Programming Assignments Contract and Pledge sheet on file.

All necessary external documentation for each programming project must be placed on the front desk of the classroom before the beginning of the lecture after the assignment due date. External documentation consists of at least 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.)

Check with your intructor(s) to verify if detailed external documentation consisting of the following is required:

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)
Brief statement and description of the problem (in your own words)
Solution/Algorithm used (including pseudocode, structure chart, object hierarchy, etc.)
Acknowledgements (optional) - a list of names of people that may have contributed to the successful completion of the assignment
List of references (on-line sources, manuals and/or books used as a reference)
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)
Sample runs showing ALL pertinent features of your program (optional)

Detailed external documentation must be securely bound using a neat and presentable folder. Please do not use letter-size envelops or ring binders.

Evaluation

All but one of the Programming Assignments must be submitted in working order to pass the course. Students are also expected to submit all Programming Assignments to earn a passing grade in the course. Otherwise, the instructor has the option of lowering the student's final grade by at least 1 letter grade.

E-Mail

Students are encouraged to 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@csuChico.edu.

Conduct

No collaboration policy: Students are expected to turn in their own individual work and not the work of another person nor a group of people, unless otherwise specifically allowed by the instructor. You may discuss problem sets with classmates, but you cannot share code. Typically, if you communicate in English with a classmate/friend, this is fine; if you are communicating in C/C++ (or any other programming language you are implementing your solutions in), you have crossed the line. It goes without saying that turning in someone else's work as your own is both unethical and a violation of university policies. For your reference, Chico State's Student Judicial Affairs office has the following documents: "Cheating" and "Unauthorized Collaboration."

Students in violation of this no collaboration policy will get a warning on the first offense. Additionally, the whole class will be informed and warned that a violation has been detected. Once a violation has been detected and the whole class has been informed and warned of the violation, succeeding offenders will automatically get the minimum penalty of a final grade of F in the course and a memo concerning this included in their academic folder. The Chair and Dean of the student's major may also be notified with the recommendation of expulsion from the University.

All cases of Academic Dishonesty are reported to Student Judicial Affairs. 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.