|Course CS 136 Fall 2011|
Williams College Department of Computer Science
|Instructor:||Prof. Morgan McGuire|
|Office Hours:||Su 3-5pm TCL 217, Wed 4:10-5pm TCL 308|
|TAs:||April Shen, Carson Eisenach, Mike Mara, Chuan Ji (Schedule)|
|Lecture:||MWF 9-9:50 am TCL 206|
|Lab:||Wed 1-4 pm TCL 217|
What makes for a good computer program? How should one go about writing one? In this course we will investigate some of the features of quality software construction: the careful analysis of a problem to determine the appropriate data structures, the design of efficient algorithms for manipulating these structures, and the organization of the program as a number of small, easily constructed and reusable classes. Work on program design, analysis, and verification will be combined with an extended introduction to data structures; all are important in the construction of sophisticated computer programs.
Fulfills the Quantitative Reasoning requirement.
Format: Lectures/labs. Evaluation will be based on programming assignments and examinations.
Prerequisites: Computer Science 134 or equivalent programming experience.
The textbook for the course is
D. Bailey, Java Structures, √7 Edition, 2007.
It is available for free online as a PDF. An electronic book saves you money, takes no room in your backpack, and is easy to navigate using hyperlinks. You may print it on a non-CS printer or through Office Services if you want a hard copy; I prefer to read it on lab computers and e-book readers.
* Lowest grade dropped
Participation 10% 9 Lab Programs* 60% 2 Exams 30%
Participate in discussions during lecture, asking and answering questions in lecture and lab, and e-mailing the me and the class with corrections and observations. It is important to engage both your peers and the material.
I will not grade or debug programs that are poorly documented, and neither will the TAs. Comments, whitespace, and variable names are effective means of documentation. This is for your own good, an issue of respecting the TAs' time, and a practical matter: If the author can't explain how a program was supposed to work, how could someone else possibly know?
CS136 is a typical 100-level science course. Most students will receive some kind of A or B, depending on their aptitute. The easiest way to succeed is to work steadily and ask questions.
Regardless of numerical grades and aptitude, students who work in good faith on all assignments and exams and attend all lectures and labs can expect not only to pass but to receive at least a C+ grade. Likewise, repeated absence from lecture or lab, and not handing in programs are grounds for failing the course, even for students who score well on submitted work.
Assignments and exams are due at or before their deadlines. Late work will not be graded. This keeps you from overextending yourself and means that everyone in the class has the same amount of time. If you know that you'll be on a trip, then just start and turn in your work early. Don't worry if you have an emergency or bad week--that's why I drop the lowest lab grade. If you have two emergencies, then please let me know what is going on and talk to the dean's office for support.
Students are bound by the CS Department Honor Code and Usage Policy and the College Honor Code. In short: all work should be your own. Remember, failing an assignment may lower your grade, but cheating will ruin your career! The labs with partners contain explicit honor code instructions.