Welcome to CS 3, "Introduction to Symbolic Programming". This course will introduce you to computer programming, using the Scheme programming language (a dialect of Lisp). Examples and programming assignments will be drawn from nonnumeric ("symbolic") applications.
The only prerequisite to CS 3 is high school algebra, specifically familiarity with variables and simple functions. We don't assume that you have had any previous computing experience. If you have done some programming, specifically involving the technique of recursion, you should seriously consider taking CS 61A instead of CS 3.
You learn programming by doing it rather than by listening to us talk about it. Thus CS 3 is organized to maximize your time designing and writing programs and experimenting with the programming environment. You'll work hard, but learn a lot. The lab sections and online activities are designed to help you get feedback at the time you need it; we hope to ensure that you're working productively rather than flailing around.
The instructor is Nathaniel Titterton (email@example.com, 643-4685). His administrative assistants are Cindy Palwick and Sue DeVries in 385 Soda.
The TAs are Clint Ryan, Paul Hale, Raymond Chetty, Irina Lib, and Jason Waddle; they will run the lab sessions. There are also several readers who grade your homework and lab assistants who work with you during the lab sections. Contact information for the staff will be posted on the class web site shortly.
There are two required books for the course: Simply Scheme, by Brian Harvey and Matt Wright (second edition, MIT Press, 1999), is available at local bookstores; CS 3 Readings is available at Copy Central, 2483 Hearst Avenue.
There is a single lecture each week. It meets in Room 100 GBH on Mondays, from 5pm to 6pm. There will be no video streams of lectures available on the internet (feel free to complain about this, since we need feedback to plead our case for these services in the future).
You are each assigned to a lab section that meets twice a week for three hours each meeting. That's right, 6 hours a week.
You must attend the section to which you are assigned; if you want to move to another lab section, you must get the approval of the T.A.s in charge of both the section you wish to leave and the one you wish to transfer to.
All sections will meet in room C30 Hearst Field Annex, between Barrows Hall and Bancroft Street.
For most of the semester, the typical lab period will involve a variety of activities, all provided online. It will start with a short quiz based on topics covered on the homework or in the preceding class; each start-of-period quiz will count toward your course grade, and you have to take (the majority of these) in the lab classroom. Following this, you'll be reading, experimenting, brainstorming, evaluating each other's ideas, and sometimes working with partners. In the Thursday and Friday sections, T.A.s may set up impromptu discussion sections to clarify student confusion they've seen earlier in the week; please tell us what you would prefer on this issue, since we will respond to feedback. There will be three "mini-projects" during the semester, to which some of the lab meetings will be devoted. The last several weeks of the semester will be less structured, as you'll be working on a project program.
A short set of homework exercises will be typically be assigned at the end of each lab. The exercises will involve writing or analyzing programs and contributing to online discussions about typical programming misconceptions. Answers to the programming exercises and contributions to the discussions will be submitted online. You should expect to put in four or five hours of work per week outside of class. If you finish the online exercises early, you may leave early or work on your homework. Some of the work later in the course, along with the project, may be done in partnership with other students in your section. (Cross-section partnerships will not be allowed.)
Lectures will introduce and motivate new material or review confusion noticed during the previous week's lab sections.
There will also be three exams. Two midterms will be during the normal lecture slot, from 5-6pm, on Monday, October 4 and Monday, November 15. The other will be the final exam, on Saturday, Dec 18, from 12:30 until 3:30.
In CS 3, you will be using programming tools and course material devised by a research group of computer science and education researchers. To determine the effectiveness of these tools and material, we are gathering data on your background and performance, via questionnaires, interviews, and analysis of your work. You will be expected to take part in an hour-long interview with a staff member, and to complete several surveys through the course of the semester.
Most of your work for this course will be done in class in C30 Hearst Field Annex. Outside of class, you may work in any EECS lab room in which a lab section is not meeting. You may also work at home, of course! You may obtain a card key to work in C30 on weekends or late at night. If you have a "newer" student ID that can double as a card key, there is no charge; otherwise, there is a $25 fee ($15 of which is refundable at the end of the semester) To do work for this course on your own computer, you will need to use a recent Mozilla browser, with a plugin that supports Java 1.3. Earlier versions of Netscape and any version of Internet Explorer will not work (or at least work well). If you use a Macintosh, it has to be running OS X.
The various course activities will contribute points to your grade as follows.
|activity||course points||percent of total grade|
|all mini-projects||24 (8 each)||12% (4% each)|
|all other homework||scaled to 24||12%|
|all on-line quizzes||scaled to 16||8%|
|random on-line step||10||5%|
|midterm exams||56 (28 each)||28% (14% each)|
You are expected to keep up with the classwork! There will occasionally be time devoted in lab to helping you catch up or solidify your understanding of the material. Homeworks assigned on Tuesday/Wednesday are due at the start of the Thursday/Friday lab section; homework assigned on Thursday/Friday are due at the start of the Tuesday/Wednesday lab section. You will at most earn half-credit for homework turned in after the due date but before the next lab meeting; you will not earn any credit for any homework exercise submitted more than one class meeting after it is due
There will be more than 24 points worth of scaled homework points to earn; your homework score, however, will be capped at 24. As such, you can miss some homework assignments and still earn the full amount that homework can count towards your final grade.
Quizzes are online, and while they may be taken outside of the lab room, you will receive credit for at most four quizzes taken outside of your lab section. You will not receive any credit for quizzes taken after the lab-section in which they were assigned, whether or not you take them in the lab room or out of the lab room.
As with homework assignments, there will be more than 16 points worth of scaled quiz points to earn, but at most 16 will count toward your course grade.
Each week one of the steps in the on-line materials will count towards your grade. Which step this is won't be known to you (or to us, beforehand), but will generally be a step for which you are asked to answer a question or create a file, although it may be a simple reading step for which we will log requests from the UCWISE server. The purpose of grading this is to encourage you to keep up-to-date on the lab materials; generally, the grades for these steps will consider whether you attempted it, rather than whether you did it well.
Your letter grade will be determined by total course points, as shown in the following table:
In other words, there is no curve; your grade will depend only on how well you do, not on how well everyone else does.
Incomplete grades will be granted only for dire medical or personal emergencies that cause you to miss the final exam, and only if your work up to that point is satisfactory.
Copying and presenting another person's work as your own constitutes cheating. It will be penalized at least by a 0 on the work in question and notification of the incident to the Office of Student Conduct.
Coverage will proceed roughly as follows. (Case studies are included in CS 3 Readings.) Make sure to check regularly the announcemtns calendar on the UCWISE course portal for the latest information, as topics and sequences may change somewhat.
|week of ...||lecture topics/activities||lab topics||reading|
|August 30||Introduction to CS 3, UC-WISE, and early Scheme concepts (functions, words, and sentences)||elementary Scheme programming||Simply Scheme chapters 3-5|
|Sept 6||(holiday, no lecture)||elementary Scheme programming with conditionals||Simply Scheme chapter 6|
|Sept 13||conditional expressions; understanding large programs; introduction to case studies||working with the "Difference Between Dates" program||"Difference Between Dates" case study, part I|
|Sept 20||good programming habits; a problem solving example||working on the "Difference Between Dates" miniproject||"Difference Between Dates" case study, part I|
|Sept 27||Q&A; Introduction to recursion||elementary recursive programming||Simply Scheme chapters 11-13|
|Oct 4||midterm exam 1||more recursive programming||"Difference Between Dates" case study, part II|
|Oct 11||examples of problem solving with recursion||more recursive programming||Simply Scheme chapter 14; "Roman Numerals" case study|
|Oct 18||examples of problem solving with recursion||working on the "Number Spelling" miniproject||Simply Scheme pages 233-234|
|Oct 25||introduction to higher-order procedures||working with higher-order procedures||Simply Scheme chapters 8-9|
|Nov 1||extending sentences to lists||more working with higher-order procedures; working with lists||Simply Scheme chapters 10, 17, and 19|
|Nov 8||examples with generalized lists and higher-order list procedures||working with complicated recursive code||Simply Scheme chapters 15, 16, and 18|
|Nov 15||midterm exam 2||working on the "Doctor" miniproject||Simply Scheme chapters 15, 16, and 18|
|Nov 22||background for projects||start on project||Simply Scheme chapter 20|
|Nov 29||to be announced (please make recommendations)||work on project|
|Dec 6||to be announced (please make recommendations)|
|..Dec 18||Final Exam! (Saturday, 12:30-3:30)|
Other courses in which you can learn to program include CS 3S, CS 4, IDS 110, and CS 61A.
CS 3S is the self-paced version of CS 3. Students may enroll for fewer than four units of CS 3S, in order to take only a portion of the course or to spread the complete course over more than one semester. (You need only three units of CS 3S to prepare for CS 61A, and two units would probably suffice.) The textbooks used in CS 3S differ from those we'll use, so if there's a chance you might want to switch, you should think about switching sooner rather than later. For further information, contact the Self-Paced Center, 642-9920, in room C10 Hearst Field Annex.
CS 4 is an introductory course for science and engineering students, although it is only in its earliest, experimental stages. Programming exercises and class examples are drawn mostly from numeric applications (as opposed to the nonnumeric applications covered in CS 3). The programming language used is Java.
CS 61A is the first of a sequence of courses aimed at students with a particular interest in computer science. Its prerequisite is computing experience roughly equivalent to the first half of CS 3; thus students with no previous experience often take CS 3 or 3S to prepare for CS 61A. Scheme is also used for programming in CS 61A. If you've done more than a little programming, particularly if your experience includes significant exposure to recursion, you should take CS 61A rather than CS 3.