CS21: Spr 2012

This syllabus is a living document; please be aware that many elements on this page will change throughout the semester, including the course schedule. It is the student's responsibility to review this page periodically for updates.

Class Info

Section 1: MWF 9:30–10:20am, Science Center 240
Professor: Richard Wicentowski
email: richardw at cs.swarthmore.edu
Office: Science Center 251
Phone: x5643
Office hours: 10:30-noon Thursday and by appointment

This course will introduce fundamental ideas in computer science while also teaching you how to write computer programs. We will study algorithms for solving problems and implement solutions in the Python programming language. Python is an interpreted language that is known for its ease of use. We also introduce object-oriented programming and data structures. A deeper coverage of these topics will be presented in CS35.

This course is appropriate for all students who want to learn how to write computer programs and think like computer scientists. It is the usual first course for computer science majors and minors. Students with advanced placement credit or extensive programming experience should place out of this course and instead begin with CS33 or CS35.

Required Textbook:

Python Programming: an Introduction to Computer Science by John Zelle
ISBN: 978-1-887902-99-1
(a copy is on reserve at Cornell Library)

Goals for the course:

By the end of the course, we hope that you will have developed the following skills:

Given a program, be able to simulate on paper how a computer would execute the program, and show the results that would be produced.
Given a problem, be able to design a clear, concise, and correct pseudo-code algorithm to solve it.
Given a pseudo-code algorithm, be able to successfully implement it in Python.
Be able to use top-down design to sub-divide a large problem into reasonably-sized modular sub-problems.
Given several algorithms for solving the same problem, be able to analyze which algorithm would be more efficient in terms of running time.
Develop debugging and unit testing skills. Consistently use these skills while implementing programs.
Learn to work as part of a team to solve problems starting from design and continuing through to implementation.

Schedule

This is a tentative schedule; it may change as we go.

WEEK	DAY	ANNOUNCEMENTS	TOPIC & REFERENCES	INCLASS & ASSIGNMENTS
1	Jan 16	Using Unix (SC240): Tue., 4-5pm Wed., 8-9pm	Introduction to Python and Unix Zelle Ch 1-2 Useful Unix commands Getting started with python and Unix	Lab 0: Unix and emacs Lab 1: First programs
	Jan 18
	Jan 20
2	Jan 23		Numbers and Strings Ch 3; Ch 4 (only Sect 4.1, 4.2, 4.3)	Lab 2: Numbers and strings
	Jan 25	Quiz 1 Study Info
	Jan 27	add/drop ends Quiz 1
3	Jan 30		if/else, Booleans Sect 7.1, 7.2, 7.3 and 8.4.1	Lab 3: Conditionals and Randomness
	Feb 01
	Feb 03
4	Feb 06		Graphics, Objects Ch 5 (skip 5.5, 5.6) Notes on the Graphics Library	Lab 4: Graphics
	Feb 08	Quiz 2 Study Info
	Feb 10	Quiz 2
5	Feb 13		Functions, Objects Ch 6 (skip 6.3) Stack frame example Stack frame homework	Lab 5: Off to the Races
	Feb 15
	Feb 17
6	Feb 20		while Loops, More Functions Sect 8.1, 8.2, 8.3, 4.4 strings and lists as objects	Lab 6: Population Genetics
	Feb 22	Quiz 3 Study Info
	Feb 24	Quiz 3
7	Feb 27		Top Down Design, File I/O Sect 9.1, 9.2, 9.3, 4.6
	Feb 29
	Mar 02
	Mar 05	Spring Break
	Mar 07
	Mar 09
8	Mar 12		More Top Down Design Sect 9.1, 9.2, 9.3, 4.6	Lab 7: G-H-O-S-T
	Mar 14
	Mar 16
9	Mar 19		Searching, Analysis of Algorithms Sect 13.1	Lab 8: Wordle
	Mar 21	Quiz 4 Study Info
	Mar 23	Quiz 4
10	Mar 26		Sorting, Analysis of Algorithms Sect 13.3	Lab 9: 19081
	Mar 28
	Mar 30
11	Apr 02		Recursion Sect 13.2	Lab 10: L systems
	Apr 04	Quiz 5 Study Info
	Apr 06	Quiz 5
12	Apr 09		Defining New Classes Sect 10.1, 10.3, 10.4	Lab 11: The Swindle
	Apr 11
	Apr 13
13	Apr 16		Linked lists	Lab 12: Summmer reading
	Apr 18	Quiz 6 Study Info
	Apr 20	Quiz 6
14	Apr 23		Advanced Topics, Wrap-up
	Apr 25
	Apr 27	study guide
	May 03	Final exam Thursday May 3, 7:00 pm -10:00 pm (SCI 101) (Study sessions: Tuesday May 1, 1-4pm; Wednesday May 2, 7-9pm)

Student Support

Student Support Coordinator: Frances Ruiz (Office: Sci Ctr 257; phone: x6062)

CS21 Ninjas: Mark Serrano, Sophie Libkind, Brandon Snuggs and Samantha Goldstein
Mark and Sophie will be specifically assigned to our class, but all four will be able to help you with class concepts, quizzes and labs.

CS21B Ninjas: Sarah Chasins and Leah Foster
Sarah and Leah will be helping out in CS21B. They can help can help you with the class material and quizzes but will be less able to provide assistance with the labs.

Study sessions

The CS Ninjas will assist me in class and run study sessions in the main CS lab (Science Center 240) on the following evenings:

Day	Time	Location
Sundays	7-10pm	Sci Center 240
Wednesdays	7-9pm	Sci Center 240

You are encouraged to participate in these study sessions to prepare for quizzes, to discuss concepts, and to get friendly assistance in working on lab assignments. Our CS mentoring team is dedicated to helping students, who have no prior knowledge of computer science, learn to program in Python while keeping their senses of humor intact. As an added bonus, free food will be provided at the sessions.

Lab Sessions

The CS lab is open 24 hours a day, 7 days a week for you to use for CS21 lab assignments. In addition, the CS21 professors will be in the CS labs at the times listed below to help CS21 students with lab assignments. You are not required to attend any of these sessions, but you should take advantage of them to get assistance with your lab assignments. Any CS21 student is welcome to attend any/all session.

Time	Professor	Location
Monday 1:00-2:30	Rich Wicentowski	Science Center 240
Friday 2:00-3:30	Jeff Knerr	Science Center 240

Accessing the CS labs after hours

You can use your ID to gain access to the computer labs at nights and on the weekends. Just wave your ID over the microprox reader next to the lab doors. When the green light goes on, just push on the door handle to get in (the door knob will not turn). If the green light doesn't go on, then we need to enter your microprox number into the system. email local-staff@cs.swarthmore.edu if you have problems with this. If the building is locked, you can use your ID to enter the door between Martin and Cornell library. For this class, your ID will give you access to the labs in rooms 238 and 240.

How to Succeed in this class

Attend class.
The primary introduction to course material is through class lecture. Additionally, we often do lab exercises during class. This is an important part of the learning process, as these exercises give you immediate experience with the material we are covering.
Read the material before you come to class.
Don't worry about total comprehension, but at least get a feel for what we will be covering that week. If you have some understanding of the material coming into class, it will be easier for you to ask questions during class, rather than later when help may not be available.
Ask questions if you don't understand.
This means both during class and while doing lab assignments . This class continually builds on previous material, so if you don't understand something one week, it will continue to be a problem the next week, and the week after that, and so on. If you need help, ask your classmates (make sure you have read the "Academic Integrity" section below first), attend the lab and study sessions, come talk with me during my office hours, or email me your question.
Start the lab assignments early.
I realize this one is not always easy to do, but if you can get in the habit of doing this, you will be much better off. If you get stuck early (i.e., not two hours before it is due), there will be time to look for help. In addition, if you start early enough, you can take a break, go do something else, and come back later. Most people find that they have at least a few new ideas when they come back to a problem after a break. If you wait until the last minute, you can't do this.
Practice, practice, practice.
The only effective way to learn the material and pass the quizes and exams is to consistently do the labs. Finish all of the assigned programs (and do some extras, for fun!). Even if you don't get them done on time, they will still help you learn the material.
Seek help early and often.
Because course material builds on previous material, it is essential to your success in this class that you keep up with the course material. If you are having difficulty with a programming assignment, if you didn't follow something covered in lecture, if you feel you need some extra help understanding or practicing some of the course material, or if you just want to discuss something from a lecture, an assignment, or the text, please come to my office hours.
Attend CS21 Labs and Study Sessions.
The student Ninjas hold evening study sessions each week. You are encouraged to participate in these sessions. The Ninjas will help you prepare for quizzes, will provide additional instruction in programming concepts, and will provide friendly assistance on your lab assignments.
Take hand written lecture notes.
In lecture the professor often draws diagrams on the board, some of which you will need to reproduce. Taking notes with paper and pen (vs. on the computer) will allow you to copy these diagrams.

Academic Accommodations

If you believe that you need accommodations for a disability, please contact Leslie Hempling in the Office of Student Disability Services, located in Parrish 130, or e-mail lhempli1 to set up an appointment to discuss your needs and the process for requesting accommodations. Leslie Hempling is responsible for reviewing and approving disability-related accommodation requests and, as appropriate, she will issue students with documented disabilities an Accommodation Authorization Letter. Since accommodations may require early planning and are not retroactive, please contact her as soon as possible. For details about the Student Disabilities Service and the accomodations process, visit the Office of Student Disability Services.

You are also welcome to contact me privately to discuss your academic needs. However, all disability-related accommodations must be arranged through Leslie Hempling in the Office Of Student Disability Services.

To receive an accommodation for a course activity, you must have an Accomodation Authorization letter from Leslie Hempling and you need to meet with me to work out the details of your accommodation at least one week prior to the activity.

Grading

Grades will be weighted as follows:

40%	Labs
30%	Quizzes
25%	Final Exam
5%	Class Participation

Quiz policy

Quizzes will be given at the beginning of class on the days posted in the Announcements section of the Schedule. Please look over these dates carefully and contact the professor in advance if you cannot be in class for a quiz.

If you are not present at the start of class on the day of a quiz, but make it to class before the end, then you may take the quiz. Otherwise you will receive a zero for that quiz.

Lab policy

Lab assignments will be posted on the Schedule in the middle of the week and will be due before midnight the following Tuesday night. You are strongly encouraged to start early and to attend the study sessions for extra practice.

You will submit you assignments electronically using the handin21 program. You may submit your assignment multiple times, but each submission overwrites the previous one and only the final submission will be graded.

Late assignments will not be accepted except in extreme situations and only if you contact me at least a day before the deadline with a legitimate reason for needing extra time, such as an illness.

Even if you do not fully complete an assignment, you should submit what you have done to receive partial credit. Unless otherwise stated, labs are to be completed individually. Please carefully read the statement on academic integrity for more information.

Programming Style

Programming is not a dry mechanical process, but a form of art. Well written code has an aesthetic appeal while poor form can make other programmers and instructors cringe. Programming assignments will be graded based on style and correctness. Good programming practices usually include many of the following principles:

A comment at the top of the program that includes
- Program authors
- Date or Dates
- A brief description of what the program does
Concise comments that summarize major sections of your code
Meaningful variable and function names
Function comments that include: (1) description of what function does; (2) description of input values (parameter values); (3) description of return value(s)
Well organized code
White space or comments to improve legibility
Avoidance of large blocks of copy-pasted code

Also, look over the Python Code Style Guide for more details and some examples of good code style.

Academic Integrity

Academic honesty is required in all work you submit to be graded. You may not submit work done with (or by) someone else, or examine or use work done by others to complete your own work. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes sharing solutions after the due date of the assignment.

All code you submit must be your own with the following permissible exceptions: code distributed in class, code found in the course text book, and code worked on with an assigned partner. In these cases, you should always include detailed comments that indicates on which parts of the assignment you received help, and what your sources were.

Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else's code or let anyone else read your code. You may discuss assignment specifications and requirements with others in the class to be sure you understand the problem. In addition, you are allowed to work with others to help learn the course material. However, with the exception of your lab partner, you may not work with others on your assignments in any capacity.

"It is the opinion of the faculty as a whole that for an intentional first offense failure in the course normally is appropriate. Suspension for a semester or deprivation of the degree in that year may also be appropriate when warranted by the seriousness of the offense." - Swarthmore Student Handbook

Please see me if there are any questions about what is permissible.