CS110: Principles of Computer Systems

Announcements

• Tuesday March 27, 2012
  Grades have been posted to Axess. Your exam and assignment grades can be viewed on the CourseWork's gradebook. Let us know if anything looks amiss. The stats for the final exam:
  • Mean: 147.7
  • Median: 151
  • StdDev: 17.41
  • High: 174
  • Low: 68
  • Histogram
  Your final exam can be picked up from Gates 303 during normal business hours.
• Thursday, March 22, 2012
  Homework 4 has been graded and returned. Class stats:
  • Mean: 91.4
  • Median: 93
  • StdDev: 13.8
  • High: 120
  • Low: 10
• Friday, March 16, 2012
  Finals week schedule:
  • Review Session: Tuesday (3/20) 7:00-9:00PM in Hewlett 200
  
  
  • Exam: Thursday (3/22) 8:30-11:30AM in Cemex Aud
  
  
  • No section this week but regular office hours will be held Mon-Wed.
• Monday, March 12, 2012
  Homework 3 has been graded and returned. Class stats:
  • Mean: 90.8
  • Median: 95
  • StdDev: 14.7
  • High: 110
  • Low: 40
• Friday, March 2, 2012
  Homework 2 has been graded and returned. Class stats:
  • Mean: 81.8
  • Median: 84.5
  • StdDev: 14.9
  • High: 102
  • Low: 26
• Wednesday, February 22, 2011
  The midterm has been graded. If you missed it in class today, your exam can be picked up from Gates 303 during normal business hours. Solutions can be found here. Class stats:
  • Mean: 32.8
  • Median: 33
  • StdDev: 7.6
  • High: 48
  • Low: 8
• Tuesday, February 21, 2012
  The location of CS110 Final Exam has been set. It will be in Cemex Auditorium in the Zambrano Hall/North Building of the Knight Management Center. Click here for a map.
• Thursday, February 16, 2012
  The CS110 Midterm Exam will be tomorrow (Friday, 2/17) from 11:00-11:50AM in Annenberg Auditorium in the Cummings Art Building. Click here for a map.
• Friday, February 10, 2012
  Homework 1 has been graded and returned. Class stats:
  • Mean: 91.2
  • Median: 93.5
  • StdDev: 10.4
  • High: 105
  • Low: 25
• Tuesday, January 10, 2012
  Discussion section signup is now available via CourseWork. A direct link to the signup page is here.
• Thursday, January 5, 2012
  Welcome to CS110! Some logistics for the course:

  Prerequisites

  CS110 formally requires CS107 and either CS103 or CS103B. Practically, the course assumes you have exposure to basic computer architecture material at the level it is presented in CS107. The course involves some systems programming so experience in C with low-level programming (especially pointers and strings) will be helpful.

  Exams

  There will be an in-class midterm exam on Feburary 17th and a final in the normal final exam slot, Thursday, March 22nd at 8:30-11:30 a.m. The final exam will emphasize material not tested on the midterm, although it is technically cumulative and everything is fair game.

  Grading

  The course grading is divided between homework (programming and discussion assignments), one midterm, and a final exam. The approximate grade breakdown is:

  Homework 50%

  Midterm Exam 15%

  Final Exam 35%

  Late Policy

  The class material builds on itself and getting behind is taboo, since it tends to impede progress on the following assignments. Late submissions will be assessed a penalty of 10% per day (24-hour period). Assignments will not be accepted more than five days after the original assignment due date. You get three free "late days" (24-hour periods) that you may use to extend the due dates of any assignment without penalty. Once all your free late days are gone, you can still hand work in late, but with the 10% penalty.

  Honor Code

  Students are expected to follow the letter and spirit of Stanford's Honor Code.

Syllabus

Introduction to Computer Systems

Complexity, abstractions

Modularization, Naming and Layering

Memory, interpreters, communication links

Client-Server Architecture

RPC, indirection, peer to peer

Client-Server within a Machine (Virtualization)

Bounded buffers, threads, concurrency, virtual memory

Performance

Design approaches, multi-level memories, scheduling

Networking

Layers, sockets

Protection and Security

Authentication, access control, cryptography

Review of systems concepts using case studies

Staff