Computer Science CS 33011-001 Speed Programming Techniques
Call Number 12474
SYLLABUS
Fall, 2016

Time and Place:

Monday,	3:45 - 6:45,	in lab 243 MSB
Wednesday,	3:45 - 5:00	in 106 MSB.

Description:

This course is different from many other courses: to begin with, though there is homework, it is voluntary (though credit will be given if you do it), in addition, it will only meet until mid-November, after the field trip to the ACM Programming Contest, which will take place some time on October 28-29.

We will leave on Friday October 28 in the afternoon for Youngstown, and return the following day, after the contest, which concludes at 6:30 or so. Only six people will get to go, those six people to be determined by mid-October.

Since I am shortchanging you on the contact hours by cutting the course short on October 31, I will hold longer sessions Mondays starting October 3 until 8:45, to simulate the 5 hours of a real contest. To alleviate hunger pangs, food will be made available during these longer class periods, starting October 3.

Instructor:

Michael Rothstein, 251 MSB, phone TBA

Email address:

rothstei at cs.kent.edu or mrothste at kent.edu address, (replace ``at'' by ``@''). Note that both go to the same address, so don't send the same message to both places; it doesn't do any good

Web address:

http://www.cs.kent.edu/~rothstei

Office Hours:

Monday, Wednesday 2:00-3:30.

Also, you can always send email with questions and/or to set up an appointment. Usual turnaround for email addressed to the cs address will often be a few hours during the day. Email use is to be preferred over voicemail, which will not be checked as often.

Suggested Bibliography:

Skiena, Steven S. and Revilla, Miguel A. Programming Challenges, The Programming Contest Training Manual Springer, 2003, ISBN 0-387-00163-8
Any decent C++ reference
An Algorithms textbook.

Course Goals:

The goal of this course is to train for the ACM Programming Contest of October 31 and participate in it: participants will get the trip paid, an Attendance Certificate, a one year student membership in ACM, and, of course, a T-shirt.

Course Description:

The idea of this course is preparation for the programming contest. The suggested bibliography is designed to be read independently; in this course, and used as a reference. I expect you to read the bibliography and ask me questions; class time will be devoted to solving exercises similar to the ones in the book, corresponding to the chapters read.

Prerequisite:

Though the main prerequisite for this course is a C in CS 23001, Data Structures, we will use (and cover some) material from other courses; having taken CS III or algorithms is a definite plus.

Attendance policy

By initiative of the Provost of the University, I have been charged with keeping full attendance records, at least for the first ten weeks of the semester. As far as this course is concerned, that is the whole course period; attendance and effort will be a major component of the final grade. The method of taking attendance will be different from other courses; instead of calling the roll on Mondays, you will have to submit at least one solution to one of the posed problems (I will call the roll on Wednesdays). Note that the solution posed does not have to be correct (though it is better if it is correct.

Grading:

Your grade in this course will depend both on effort and on results; since there will be very little homework after the first few weeks, attendance will be an integral part of the grade; so is class participation; if you have a bad attendance record, you will get an ``F''; otherwise: in order to get an ``A'', you need to be the person who gets the most problems solved (or closed to that); the less problems you actually get solved, the lower your grade, though I guarantee that somebody with ``perfect attendance'' (i.e. tried honestly to solve at least one problem each week), will get at least a ``C''. If your attendance is not perfect and you have not solved many problems, your grade will slip below that. I cannot over-emphasize the importance of attendance in the grade in this course.

This syllabus may be changed during the semester if necesary: changes will be announced in class; they will also show up on the instructor's website.

Special accommodations for Students with Disabilities:

University policy 3342-3-01.3 requires that students with disabilities be provided reasonable accommodations to ensure their equal access to course content. If you have a documented disability and require accommodations, please contact the instructor at the beginning of the semester to make arrangements for necessary classroom adjustments. Please note, you must first verify your eligibility for these through Student Disability Services (contact 330-672-3391 or visit:
http://www.kent.edu/sas for more information on registration procedures).
Note that, since this is an elective course, that is preparation for a contest, ``additional time for tests'' cannot be considered.

(Think of requiring additional time for programming like a runner who needs additional time for the run in a competition.)

Registration Requirement:

The official registration deadline for this course is September 4, 2016 for adds, September 11 for drops. University policy requires all students to be officially registered in each class they are attending. Students who are not officially registered for a course by published deadlines should not be attending classes and will not receive credit or a grade for the course. Each student must confirm enrollment by checking his/her class schedule (using Student Tools in FlashFast) prior to the deadline indicated. Registration errors must be corrected prior to the deadline.

The last day to withdraw is November 6, 2016.

On cheating, plagiarism and other unethical behavior

For this course, cheating consists in subverting system security to obtain gain in either the training or the contest. I will also consider cheating in cases of non-declared code sharing or submissions of programs downloaded from the web. For information on the University's cheating policy, see the University policy register on cheating:.

Notes:

1. By default, the penalty for cheating in this course is an ``F'' in the course.
2. University regulations require me to notify Student Conduct in case of violations.
3. Any attempt at cracking one of the judging systems may end up with a disciplinary action, and an F in the course.