This course is a broad introduction to computer science that focuses on how a computer works and how programs run on computers. We examine the hardware and software components required to go from a program expressed in a high-level programming language like C or Python to the computer actually running the program. This course takes a bottom-up approach to discovering how a computer works, and introduces parallel and distributed computing with a specific focus on parallelism for multicore and other shared memory systems. Topics include theoretical models of computation, data representation, machine organization, assembly and machine code, memory, I/O, the stack, the operating system, compilers and interpreters, processes and threads, and synchronization. In addition to parallel programming, we will discuss parallel computers and system-level support for parallel computing. Prerequisite: Completion of CS21 or its equivalent.
Rather than requiring a textbook, we're going to try something a little
different this semester and use readings from the web as our introduction to
new material. The textbook we've used in the past for this course is: Computer
Systems: A Programmer's Perspective by Bryant and O'Hallaron (Second
edition: 2/E CS:APP2e). It's a great reference, and I recommend it as a
supplemental source of information, if you're interested. I will list
corresponding sections for this book, when applicable.
By the end of the course, we hope that you will have developed the skills to:
This is a tentative schedule; it may change as we go. You should read the assigned sections before class to prepare for the reading quiz. All section numbers refer to the Bryant and O'Hallaron textbook unless otherwise indicated.
This course features regular lab assignments that account for the largest component of your course grade. Lab attendance is required by all students, unless you have already completed and submitted the lab assignment for the week. Additionally, the cs labs are open 24 hours a day, 7 days a week for you to use for CS31 lab assignments. While you must attend the lab session for which you are registered, you may optionally attend additional lab sessions, provided space is available. In case of space constraints, students registered for the lab will have seating priority.
Lab assignments will typically be assigned during the lab sections on Wednesday will generally be due by midnight on Tuesday, one week later. You are strongly encouraged to start early!
Even if you do not fully complete an assignment, you should submit what you have done to receive partial credit.
|Weekly Lab Sessions|
|Section A||Wednesdays 8:50—10:20||Science Center 240|
|Section B||Wednesdays 1:15—2:45||Science Center 240|
|Section C||Wednesdays 3:00—4:30||Science Center 240|
Weekly Evening Ninja Session: Sundays, 7:00 PM - 11:00 PM
The CS 31 Ninjas: Amy, Charlie, Douglass, Jack, Martina, and Zoe
Ninja Coordinator: Lauri Courtenay (SCI 257)
|5%||Reading Quizzes (I will drop your three lowest quizzes.)|
For CS 31, we will drop your three lowest reading quizzes and participation grades. Dropping these scores is intended to help when you need to miss a class due to a minor illness or to travel for an interview. You are still responsible for the material, and you should review any missed materials via the class recordings as soon as you can.
If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition (e.g., extended illness, concussion, hospitalization) or family emergency, you must provide your instructors with official documentation from the dean's office or student health center. Their documentation will help us to provide the appropriate accommodations.
Academic honesty is required in all your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. 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, but is not limited to, obtaining solutions from students who previously took the course or code that can be found online. You may not share solutions after the due date of the assignment.
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. 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.
Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook: "Because plagiarism is considered to be so serious a transgression, it is the opinion of the faculty that for the first offense, failure in the course and, as appropriate, suspension for a semester or deprivation of the degree in that year is suitable; for a second offense, the penalty should normally be expulsion."
Please contact me if you have any questions about what is permissible in this course.
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.
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.