CS 23021 Programming Lab Policy
The programming labs for CS 23021 are a sequence of assignments. The assignments will be submitted to the subversion repository. Work outside the repository is not accepted or graded. The first in-class assignment describes the submission process. All programs should compile and run correctly on either loki.cs.kent.edu or hermes.cs.kent.edu Your program should produce correct results for any valid input. If it just compiles or produces correct results for one or two correct inputs does not mean it is correct. You should test your program thoroughly before submission.
Lab Assignments
An assignment is given every class session. A significant part should be completed within the class session, but
you can finish it outside of the lab. Normally in-class assignments are worth 10 points, but larger assignments
may carry additional points.
Attendance
Lab attendance is required. Two points are deducted from the assignment submission for a missed lab session. An
exception may be made in the case of the first lab, e.g. if the student enrolled late. In general, at the discretion
of the lab instructor, this deduction is waved in exceptional circumstances, such as documented illness. If you
missed a lab, contact the instructor at once.
Due Dates and Late Submissions
The assignments are due by 11:59 pm four days after your lab session, i.e. Saturday at 11:59 pm for Tuesday labs
and Monday at 11:59 pm for Thursday labs. Late assignments are accepted until the seventh day after the class session
they were assigned. That is, we stop accepting the assignments on the date of the next lab session. There is a
5 point deduction for late assignments. At the discretion of a lab instructor, extensions may be granted in exceptional
circumstances such as documented illness. If you need an extension, contact your lab instructor immediately. In
any event, all assignments have to be turned in before the last day of classes.
For longer programs, more time may be given to the class.
Grading
Grading assigns more points are to the project that is late but is correct than to the project that is submitted
on time but is not correct. However, some points may be given to the project that does not compile depending on
how close the submission is to the complete project. If you are submitting a project that does not work correctly,
submit a text file named explanation.txt. This file should contain a description of what does not work and how
you think it might be fixed. Your submission should adhere to the style requirements of the lab and to good programming
style. Points may be taken off the project that is correct but is written in poor programming style.
Working Outside Classroom
It is expected that part of the lab assignment is done outside the classroom. If you have an internet connection
you can download an ssh client and use it to login to loki or hermes and work in the same matter as you do in the
lab. A ssh client is available at http://www.kent.edu/is/ under downloads or you can use putty, available from http://www.chiark.greenend.org.uk/~sgtatham/putty/
Cheating and Plagiarism
Plagiarism of any time will not be tolerated. It will be dealt with in accordance to Kent State University's policy
on cheating and plagiarism described in the student handbook. You may discuss the programming assignments with
your classmates. However, you must write your own program yourself. If two similar assignments are discovered,
both students are considered guilty of plagiarism. Therefore, protect your code and do not let other students copy
it. Remove your projects from the local disk after you are done working on a public computer.