CS 13011/13012 Programming Labs
Policy
The programming labs for CS 13011/13012 is a sequence of assignments.
The assignments shall 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 on the CS department computers.
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. Each assignment contains a part
called milestone. Milestone is expected to be completed in
class.
Each assignment is worth 10 points.
Attendance
Lab attendance is required. Attendance is taken after the completion
of the milestone or at the end of the lab session. Two points are
deducted from the assignment submission for the missed lab session.
The only exception is the fist lab. At the discretion of the lab
instructor, this deduction is waived in exceptional circumstances,
such as documented illness. If you missed a lab, contact the
instructor at once.
Due Dates and Late Submission
The assignments are due by midnight the third day after the class
session they were assigned. Late assignments are accepted until the
seventh day after the class session they were assigned. That is, we
stop accepting the assignments the midnight before the date of your
next lab session. There is a 2 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.
Code Review
As part of the grading process, during the lab
session, you may be required to explain your code operation. Be
prepared describe your coding decisions and design.
Grading
Grading is going to be such that more points are given to the project
that is late but is correct than to the project that is submitted on
time but does not compile. 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 compile, submit a text file named explanation.txt. This
file should contain a description 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. You can do it in CS labs. However, we encourage you to set
up Micrsofot Visual Studio C++ and TortoiseSVN at home and work from
there. The setup instructions for home installation
are here.
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.
Do not download code from the Internet or otherwise try to obtain lab
solutions without coding them. Do not use Artificial Intelligence
chatbots, such as ChatGPT or Bard, for help with your programming
projects.