• Course Information
• Syllabus
• Assignments
• Homework
• CS Department
• College

Syllabus for Spring 2008

Topics and Reading Assignments

Textbooks

Grading

Attendance

You are expected to attend and actively participate in all lectures. You will benefit from what is presented and discussed in lecture, and I and your classmates will enjoy the pleasure of your company and benefit from your insights. Advance notice of a scheduled absence is appreciated but not necessary. Please do not skip class to work on homework or a project for this or another class.

Assignment & Homework Submission

The majority of assignments will be written homework, but we may have some programming assignments too. More about that as the semester progresses. Written homework may be either handwritten (provided it is organized and relatively legible) or typed (preferred) using LaTEX or other type setting/word processing software and is due at the start of class on the specified date. Homework submitted later than 10 minutes after the start of class will be considered late. Any programming assignments will be submitted electronically (exact method to be determined) and are due by 11:59 p.m. on the specified date unless otherwise indicated. Late assignments/homework are graded at my discretion, so start thinking about the problems early and budget your time accordingly. If I decide to grade late work, up to twenty percent may be deducted for each day late. Exceptions will be made in what I consider to be extraordinary situations (death, serious illness, etc.).

Collaboration Policy

I strongly encourage you to collaborate with each other both to learn the material we cover in class and to solve homework problems. You may freely discuss with each other what the homework problems are asking and how to solve them. However, you are each required to submit your own written solution that you prepare without assistance from your collaborators. You should clearly acknowledge with whom you worked on your solutions and any external resources utilized. At any time if you have any questions about this policy please do not hesitate to ask me.

Class Project

There will be no final exam for the course. Instead, you will complete a project on a topic of your choosing that you work on individually or as part of a two person team. Projects can involve implementing an algorithm/protocol, understanding and explaining some primitive/algorithm/protocol/standard, evaluating the effectiveness of an existing implementation/security tool or policy, and whatever else you can think of and get my approval for. Each project team will be expected to give a short presentation/demonstration and submit a written project report at the end of the semester. Click on the homework link in the left pane for project timeline information and topic ideas.

• 3/14-3/20: Initial proposal meeting
• 3/21: Submit short written proposal
• 4/16-4/18: Interim status update meeting #1
• 4/28-5/2: Interim status update meeting #2
• 5/5, 5/7: 15 minute in-class demo./presentations
• Mon. 5/12 noon: Final writeup due

Scott Russell © 2008