The Student Conduct Code is published each term in the Schedule of Classes, and desribes the procedure your instructor will follow in handling possible incidents of academic dishonesty.
You may work alone on the projects or with one partner (in a "programmer team"). Groups of three or more are not an option.
If you work as a team, turn in one copy of the project with both your names on the coverpage. (NOTE: do not work as a team and then turn in two copies, each with one name.)
If you work as a team, you must each understand the solution you are turning in. Exams will cover much of the same material as the programming projects, so both people on a team should understand the material.
To turn in another's work under your name is plagiarism, and qualifies as academic dishonesty. The results can be quite serious.
No program you turn in should contain sections identical to another student's (or team's) program.
Basing your assignment on work done in a previous year is also prohibited, as is using the work of students not presently enrolled in the course.
EXAMPLE: Imagine you are in a philosophy class.
If you submit a paper that contains a paragraph (or paragraphs) written by someone else, that would clearly be plagiarism. The same situation holds in computer science-- if you submit a block (or blocks) of code written by someone else, that is plagiarism.
Also, do not hand your work over to another student to read. If you allow anyone to copy your work, in part or in whole, you are liable as well.
Academic dishonesty (e.g., plagiarism, cheating on exams, etc.) is a serious violation of the rules of fair play; the consequences can be both severe and permanent. Cases of academic dishonesty in this class will be dealt with as specified in the Student Conduct Code; please refer to "Academic Dishonesty Cases" in the Student Conduct Code, published each term in the Schedule of Classes, for details.
If this sounds complicated and you are ever in doubt about plagiarism, please consult your instructor prior to submitting the work in question.
When you turn in, o A source file (.C, .java, etc.) o An input file (.in) o An output file (.out)you are stating, "When my program executes on this input file, it produces the attached output file."
IF you turn in an output file that could not have been generated by the source file submitted with it, you appear to be falsifying your results.
Falsifying results qualifies as academic dishonesty (cheating).
Therefore, when you are attaching your printouts to a coverpage, please double-check that the .C, .in, and .out files all belong together.
Remember: the output files you submit must be generated by your program, otherwise you are submitting falsified results.
The Student Conduct Code is published each term in the Schedule of Classes, and desribes the procedure your instructor will follow in handling possible incidents of academic dishonesty.