Computer Systems CS 3650

Course Information

• Course Number: CS 3650
• Semester: Fall 2019
• Piazza: Forum Board (For both sections)
  Use piazza instead of e-mail for all course related matters
  • This way all course staff can answer questions
  • Class as a whole can participate and learn in discussions
  • Code also formats better nicely pasted in
  • (Linking your github is also easy for private posts)
• Section 1: Computer Systems - 13008 - CS 3650
• Schedule: MR 11:45am-1:25pm
• Location: Robinson Hall 411
• Section 2: Computer Systems - 14054 - CS 3650
• Schedule: MW 2:50pm-4:30pm
• Location: Behrakis Health Sciences Cntr 310

Instructor

• Instructor: Mike Shah
• E-mail: mikeshah( a t )Northeastern{dot}edu
Use e-mail primarily for personal matters
• e.g. I have a co-op interview and need to reschedule XYZ
• e.g. I am away for a conference on date X to date Y
• e.g. I am away for a doctors visit.
• (Read How to send an e-mail)
• Office: Nightingale 132A
• Student Hours: In West Village F 114 (In African American Institute) Review course material with me and ask questions Mon: 4:30-5:30pm, Wed 4:30-5:30pm or 15 minute appointments arranged by e-mail.
• Note that Nat Tuck and Aanjhan Ranganathan are running other sections which may be structured slightly differently.

Course Description

In short, we will be diving into many low level components of computer systems to think like a systems programmer. This course is very applied, meaning we will be writing code.

Registrar Description: Introduces the basic design of computing systems, computer operating systems, and assembly language using a RISC architecture. Describes caches and virtual memory. Covers the interface between assembly language and high-level languages, including call frames and pointers. Covers the use of system calls and systems programming to show the interaction with the operating system. Covers the basic structures of an operating system, including application interfaces, processes, threads, synchronization, interprocess communication, deadlock, memory management, file systems, and input/output control.

Course Objectives

By the end of this course, you will:

• Have a working knowledge of C.
• Be comfortable working in the terminal in a Unix environment.
• Build and use tools for inspecting and debugging programs at a low level.
• Be comfortable with concepts like concurrency and parallelism
• Better understand operating systems
• Get some experience working on a large scale codebase.
• Position yourself for jobs as a systems programmer

Resources

There will be no required textbook for this course. However, these resources are recommended.

• (free) Operating Systems: Three Easy Pieces
• (Strongly Recommended) Computer Systems A Programmer's Perspective (3rd Edition)
• Low Level Programming
• (free) xv6 Text Revision 10
• (for fun) Code (Best appreciated after this course)

Prerequisites

• CS 1500, CS 2510, or EECE 2560.
• You should be comfortable using a text editor of your choice
• You should be willing to work with others, share your thoughts, and ask questions
• You should have basic knowledge in github, using any text-based editor, and how to compile, run, and debug programs.

Assessment/Course Polices

Please find below the grading distribution that will be used for this course. You will find the grade you earn in this course on blackboard.

• In-Class Activity: (5%)
• In-Class Labs:     (20%)
  • Labs are due before class of the following week.
• Exam/Quiz:         (10%)
• Assignments:       (Each worth remaining % / # of Assignments)

• The grade system follows the University Grading System.
• A  = 95 – 100
• A- = 91 – 94
• B+ = 87 – 90
• B  = 83 – 86
• B- = 80 – 82
• C+ = 77 – 79
• C  = 73 – 76
• D+ = 67 – 69
• D  = 63 – 66
• F  =  0 – 62

• In the event of a sick/snow day (i.e. we miss a lab or in-class activity) the weight of each assignment increases (There may also be shuffling of course material if we are interrupted).
• The expectation is that the assignments are fair but difficult, so you should start early!
• Late Submissions of Assignments receive 10% off per day submitted late (up to 3 days max, then 0% received)
  • Unfortunately, with 100+ students I cannot make individual exceptions fairly to your classmates who are likely making other personal sacrifices to complete work on time.
  • Come speak to me about your wellness if something is otherwise impeding your progress so we can provide you available resources to succeed.
• Assignments that do not compile/open receive no credit Simply put, programs that do not compile do not do anything.
• There are no "re-grades" or points awarded one week after your grade is posted. "re-grades" may result in a higher, equal, or lower score.
  • There are no "re-grades" after the semester is over.
  • Do not ask multiple members of the course staff for "re-grades"
• If you are currently waitlisted, you must submit your homework on time. That is the gamble! If you do not have blackboard access, you will submit by e-mail or other course mechanism (e.g. github).
• There are no extra credit assignments just for you. I reserve the right to add points to assignments that do go above and beyond however. I reserve the right to give an extra credit assignment to the entire class, though this is highly unlikely.
• I reserve the right to modify the grading scale in your favor if you show exemplary proficiency in any of the catagories. I will never modify the scale to lower a students grade.
• In class work cannot be made up at a later date unless otherwise arranged with the instructor well in advance.
  • Course work completed after the date cannot be graded, as solutions will have been discussed (this includes if taking this course for an Incomplete).
  • Once again, "in-class" work must be completed in-class unless there is a documented emergency or you have prearranged with the instructor a make-up well in advance.
• Lab time is meant for helping students with the lab, not completing homework. I have to prioritize lab first, then can answer homework questions.
• No Facebook, no cell phones. Not only does it distract you, it distracts others!
• Everyone needs to come see me in office hours (or by appointment) at least one time during the semester to introduce yourself. The purpose is so that you:
• Know where my office is.
• Get used to coming to office hours.
• Let me know how I can help you achieve your goals.