Computer Science 182: Pen Based Computing (Spring 2008)

Mon/Wed, 1:15-2:30pm, Beckman B100
Christine's office hours (Olin 1241): Tu 4-5pm, W 3:30-4:30pm and by appointment
alvarado@cs.hmc.edu
Schedule * Syllabus * Reading List * Assignments * Resources
Reading Notes *  Presentations * Programming Assignments

Reading Notes

To help you get more out of your readings, I ask you to make notes on the papers as you read them.  You may make these notes on a separate piece of paper, or directly on the papers themselves (I recommend this approach).  You should look for important or confusing points in the text, and then write down why you believe a certain passage is interesting, or what you find confusing (and what you need to know in order to understand the passage).  There is no "right answer" for these notes.  Just write what helps you understand the text as well as you can.  Take a look at the example on Sakai (but feel free to use your own format if you want).

We will begin every class with a short discussion time during which you share your thoughts that you wrote in your notes, so it is essential that you complete your reading and your notes *before* class and upload them onto the Sakai site.

To submit your reading notes, log on to the Sakai site and look under the "Discussion" section.  Find the topic pertaining to that day's reading, listed by author.  If the topic does not yet exist (i.e. you are the first one to post), add it using the author's last name and the date the reading is due (e.g., Herot 1/23).  Then, post your reading notes by replying to the topic, either as text directly in the discussion field and/or an attachment to your reply.  For example, if your reading notes are handwritten annotations directly on the PDF file, simply create a reply and then attach the PDF to your reply.

I will grade select reading notes on a check/check-plus/no-credit scale.  If it seems that you have put a reasonable amout of thought into your reading you will receive a check-plus.  If you submit something that indicates you have some at least a little thinking, you will get at least a check.  Late or missing notes will not receive credit.  

Presentations

Once during the first part of the semester you will be responsible for presenting the chosen paper, including the technical material in it and the context of the paper in the field of pen-based computing.  Your presentation should be between 30-40 minutes.   You should be sure to include the following:
You do not have to do all the talking, and you should feel free to make your presentation interactive, asking for feedback and participation from the rest of the class.  You should meet with me at least the day before your presentation to make sure that you have the correct focus and so that I can help you with any issues you have run into.

Presentations will be graded according to this rubric.

Programming Assignments

This section gives you information on the programming assignments, the main component of this class.  Please read all of the information below.
The Assignments
Submission Instructions
We will use Sakai for all homework submission.  I know, Sakai is a big pain, but when it works it's the easiest submission out there.  Please try to be understanding with its terrible interface.  I didn't design it.  I hate it too.  But we're going to use it for lack of something better (that's just as easy for me).

To help me better understand the impact of each assignment, for every assignment you submit through Sakai, you should also complete the corresponding "assignment info survey". BEFORE you submit your assignment, click on Tests & Quizzes and fill out the appropriate survey.  EVERYONE SHOULD COMPLETE AN INDIVIDUAL SURVEY, regardless of whether or not your worked in pairs.  This is required.  Failure to submit your survey on time will result in a loss of points on the assignment.  

You should submit your assignment files through the ASSIGNMENTS PAGE on Sakai.  It's not hard, but it has some quirks.  If you watch out for these quirks, it will make your life easier.
Extensions
You have 2 48-hour extensions that you may use on any assignment EXCEPT the project.  If the assignment is a pair assignment and you both have an extension left, you will both be charged an extension.  If only one of you has an extension, you can have a 24-hour extension.   One person cannot use more than one extension on any one assignment.  
Working in Pairs
You should get in the habit of telling me who you discussed an assignment with.  I am also interested in some statistics to help me get feedback on individual assignments.  

You may discuss any of the assignments with anyone else in the class.  You may do any of the assignments except the first in pairs but I will ask you to switch who you work with from assignment to assignment.  I may allow a group of 3, depending on how the numbers work out (and who wants to work individually or together).  If you work in a pair or a group, I expect your assignmet to reflect the fact that you had more people on the project (that is, my expectations for the work you complete will be higher).  

Your work in this class should be in conformance with the Harvey Mudd honor code.  For any assignment, you may discuss (verbally) your work with anyone in the class.  When specified on an assignment, you may work with one other person, but it must be a true collaborative effort.  I encourage pair programming (i.e., you are both seated at the keyboard together when coding) whenever possible, but your design and your writeups should always be done as a team (i.e. discussed together).  

If you discuss an assignment with anyone else (which, again, is encouraged!) you must list that person's name on your survey. If you have any questions as to what is considered acceptable collaboration, please ask.