CSc
352 (Summer 03) Systems Programming and UNIX |
![]() |
Policies: |
Misc.
Policies:
|
|
Academic
Integrity:
|
I encourage you to talk with your friends about the work
you are doing for this class; both giving and taking advice will help
you to learn. Assignments require individual attention and effort to be
of any benefit. It is permissible to discuss problems with others in broad
terms, e.g., the structure or approach of a program. It is not permissible
to discuss concrete details of solutions to a particular assignment before
the due date/time for that assignment. A simple way to distinguish between
these two situations is to use Prof.
Stuart Reges' characterization: you can talk to each other in English,
but not in C/Unix. Unless otherwise stated on the assignment sheet, all
work is expected to be that of each student alone, and not the product
of team efforts or collaboration with others. It is permissible to use
"publicly visible" code -- code that is available in books or
magazines, or which has been distributed in class -- in programming assignments,
as long as the authorship of such code is adequately and explicitly acknowledged.
It is not permissible to solicit code from others, e.g., by posting requests
to Usenet newsgroups. Plagiarism or the incorporation of another student's
words, code, or ideas constitutes theft of intellectual property; at a
minimum you will receive a grade of `zero' for the assignment and a reduction
of one letter grade in your course grade. Helping another student cheat
will result in the same punishment -- I intend to interpret the phrase
``helping another student cheat'' broadly: for example, if another student
gains access to your code because you forgot to logout, or were careless
about listings that were dumped into the recycling bin, you have helped
that student cheat. I refer you to the University's Code
of Academic Integrity for further details.
|
|