Systems Programming

Instructor: Prof. Sibin Mohan, The George Washington University

CSCI 3410 | Spring 2023 | TR 03:45PM - 05:00PM ET | 1957 E B12

This course will focus on teaching the fundamentals of systems programming, using C.

On completion of this class, students will,

• Design and implement C programs and use the associated development tools
• Understand the basic means of constructing applications from libraries and communication with services
• Demonstrate an understanding of composition as a fundamental design concept for advanced functionalities
• Understand representations of programs and processes
• Apply UNIX abstractions for processes, process control, IPC, and file systems

Structure - This class is broken into two main activities: lectures and labs:

• Lectures will discuss the main concepts in systems with many references to implementation details
• Labs will help you jump into the details, learn details about homeworks, and practice key mechanisms

• A series of homeworks (all in C) will test student's ability to apply the courses concepts in a set of projects
• Quizzes throughout the class, and the final exam test student's understanding of the lecture's concepts

Prerequisites: Computer Architecture I, Software Engineering.
Assignments for this class will be done in C, and we assume basic C expertise. If you are not comfortable with C, at least go through Essential C and the exercises in the Course Material Section.

Course Staff

• Instructor: Prof. Sibin Mohan
• Teaching Assistants:
  • Marshall Thompson
  • Jonathan Lee
  • Aisha Mohammed
• Learning Assistants:
  • Josie Libbon
  • Jonathan Nguyen

Course Details

• Time: TUE/THUR 03:45 PM -- 05:00 PM ET
• Location: 1957 E Room B12
• Prof. Mohan office Hours: THUR 1:00 -- 1:00 PM ET [SEH 5th Floor]
• TA Office Hours:: see shared calendar on Blackboard
• Contact: please message on Blackboard

Communication

Target Audience

Covid

Grading Criteria

In Class Participation

Course Materials

Required reading.

You must read through the material at the repo for class resources.

This includes some intuition as to how to develop C, how to think about debugging and testing, and how to think about generating good code.

Lecture material

Textbook and Other Resources

The required text book is Computer Systems: A Programmer's Perspective, by Randal E. Bryant and David R. O'Hallaron.

Though other editions should be OK, we'll reference chapters in the 3rd edition.

Optional, but strongly encouraged resources:

• Advanced Programming in the Unix Environment by Richard Stevens, as it will give you all of the examples you'll need to understand UNIX APIs.
• Nick Parlante's introduction to C including an overview in Essential C, memory and pointers, linked lists, and linked list problems. These are reproduced from here. The Linked List problem sets are especially useful.

A few additional resources:

• If you're having trouble understanding what a specific declaration is in C, use the `cdecl` command, or, if it isn't installed, you can use the `cdecl` webpage.
• For those of you who know C, but want to learn how to write better C, one source is the Composite Style Guide.

Schedule

Policies

Expectations and Responsibilites

Each semester, you're expected to spend at least:

• 70 hours in class, and in lab for direct instruction
• 150 hours out of class watching lectures, and working on your class assignments

Student Responsibilites: Students must,

• Conduct your online behavior in accordance with the class' Online Social Contract
• Attend all classes and labs unless you are sick or there is an emergency in which cases you must contact the professor via email before class
• Interact, ask questions, and generally participate in class discussions
• Do group exercises assigned in lectures and labs
• Be respectful when working in a group, and make sure that everyone's ideas are heard and taken seriously
• Complete all work in accordance with the academic honesty rules for the university and for the class
• Work to digest and process all provided material including Blackboard and Discord discussions (you cannot ignore Blackboard)
• Contact the Professor if you are worried about completing any responsibilities

We also need your feedback for parts of the class that aren't working for you. We do our best in running the class, but certainly make mistakes, or overlook different aspects. Class evaluations are of limited use since they only are given at the end of the class. Please provide feedback using the linked feedback form on Piazza.

Professor and Instructional Staff Responsibilities

You should depend on the instructional staff (including Gabe) for the class to:

• be clear about student's responsibilities in the class
• convey the course's materials on this webpage, on Blackboard, in class, and in lab in a manner that is approachable and understandable to every single student
• provide an environment in which everyone feels open to ask questions, and seek to remedy any misunderstandings or confusions
• provide additional material on demand if anyone is curious about knowledge beyond the scope of the class

Further, it is our intent that students from all diverse backgrounds and perspectives be well-served by this course, that students’ learning needs be addressed both in and out of class, and that the diversity that the students bring to this class be viewed as a resource, strength and benefit.

It is our intent to present materials and activities that are respectful of: gender identity, sexuality, disability, age, socioeconomic status, ethnicity, race, nationality, religion, and culture.

Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally, or for other students or student groups.

Late Policies

Submission/due dates are announced along with the Homeworks descriptions.

The late policy for this class is strict. This is for two reasons:

• We aim to be fair. Once we get into the business of making exceptions, we lose the ability to be fair, and can (sometimes rightfully) get accused of bias. Uniform policies, applied to everyone is our means of ensuring fairness.
• Falling behind in this class is a slippery slope. As deadlines fall every week in the class, missing a deadline means that you have more work in the following week, which makes it less likely that you'll be able to do it all. To succeed in the class, the number one optimization is to not fall behind. Please talk to Sibin if you're concerned.

As such, the only acceptable excuses for late submissions are medical and family issues. I will strongly encourage you to use your module that will be counted as extra-credit if you miss a deadline so that you don't fall behind on the coming deadlines.

Generally unacceptable excuses include:

• your computer failing (we're using github for a reason)
• lots of midterms/other assignments
• forgetting to `git add` necessary files, or forgetting to `git push` (proper `git` usage is a requirement for the class)
• you worked very hard and put a lot of time and effort in, but still aren't quite there yet.

You get 0 credit for late work that is unexcused.

However, once the grades are released, you can resubmit your code within seven days, rounded up to the closest midnight.

For example, if the grades are released at 2:30pm on the 8th, resubmissions are due at midnight on the 15th (i.e. $8 + 7 = 15$).

You will get 0 credit for submissions after this date.

We will grade the last commit before the resubmission deadline, and you will receive 50% of the credit on top of the original grade, rounded up to the nearest percent.

For example, if you got a 43% on the initial deadline, and resubmit and get a 68%, your final grade ($g$) will be $g = \lceil 43 + \frac{(68 - 43)}{2} \rceil = 56$.

Do not come to rely on the resubmission process.

Homeworks are due every week or every other week, so it is very harmful to get behind on them, or to add more work to your schedule. Thus, our late policy is quite strict to discourage procrastination.

Testing your implementation

You are required to test your own code. Our tests will attempt to test every edge case in the implementation. If you do not write code to test the edge-cases of the specifications, then you will lose credit. This is the largest reason why students get lower grades than they believe they deserve.

If you believe that an error was made in grading, then please explicitly address why you believe your test cases are sufficient to test all cases. See the discussion about testing and debugging below.

Style and Code Craftsmanship

You must adhere to the class style spelled out in the lecture notes.

It is very important that you not only get your code working, but view your work as fine code craftspersonship.

If you want to understand a more complete set of style guidelines, see the Composite Style.

Collaboration and the Honor Code

You are encouraged to work together. You may discuss the MPs with other people to understand the problem and reach a solution. However, each student/group must write down the solution independently, without referring to written notes from others. Hence, you must understand the solution well enough to discuss it yourself. In addition, each student/group must explicitly mention the names of the people with whom they collaborated. If I suspect cheating, I might have the student(s) come and answer questions in my office. If my suspicions are confirmed, I will refer the student to the disciplinary committee.

The purpose of problem sets in this class is to help you think about the material, not just give us the right answers. You are encouraged to use online resources for learning more about the material covered in class; however, you should not look for or use found solutions to questions in the problem sets. Specifically, you must not look at any code that has been created to solve the assignment, including solutions found on the internet to questions in the problem sets, code created by a student in a previous class or code created by a current classmate. (Though frankly, I seriously doubt you'll find anything, I regularly change the assignments).

Academic Integrity

Familiarize yourself with the standards set forth in the GWU Code of Student Conduct and specifically the University’s “Guide of Academic Integrity in Online Learning Environments". If there is any question about whether an act constitutes academic misconduct, it is your responsibility to seek clarification and approval from the instructor prior to acting. When in doubt, ask, or don't do it.

• rights@gwu.edu
• 202-994-6757

Absence Policy

If you miss a class, for whatever reason, you are still responsible for that class' material. Go through the lectures, consult the scribe notes, come to office hours (in that order), and talk to your fellow students, to learn the material.

Grade Review Policy

You have one week after a grade is released to ask me questions about it and seek a correction. After the week has passed, the grade is finalized.

In case you are seeking a correction to the grade, you need a specific reason: e.g., your implementation on HW1 was essentially correct but some errors in our test cases resulted in a lower grade. I cannot accommodate general requests that are a variation on "I think my grade was too low". Why do you think that? Based on our discussion, I might increase the grade, decrease it, or leave it as is.

Of course, you can stop by anytime during the term to ask questions about any part of the material. The one-week deadline applies to grade-specific questions.

Use of Electronic Course Materials and Class Recordings

Students are encouraged to use electronic course materials, including recorded class sessions, for private personal use in connection with their academic program of study. Electronic course materials and recorded class sessions must not be shared and must not be used for non-course related purposes unless express permission has been granted by the instructor. Students who impermissibly share any electronic course materials are subject to discipline under the Student Code of Conduct. Please contact the instructor if you have questions regarding what constitutes permissible or impermissible use of electronic course materials and/or recorded class sessions. Please contact Disability Support Services if you have questions or need assistance in accessing electronic course materials.

Academic support

Writing Center

GW’s Writing Center cultivates confident writers in the University community by facilitating collaborative, critical, and inclusive conversations at all stages of the writing process. Working alongside peer mentors, writers develop strategies to write independently in academic and public settings.  Appointments can be booked online at: gwu.mywconline.

Academic Commons

Academic Commons provides tutoring and other academic support resources to students in many courses. Students can schedule virtual one-on-one appointments or attend virtual drop-in sessions. Students may schedule an appointment, review the tutoring schedule, access other academic support resources, or obtain assistance at academiccommons.gwu.ed.

COVID-Related Topics

The university's COVID-19 Safety and Success website serves as the primary communication channel for the GWU regarding COVID-19 logistics and classroom guidelines.

Face Coverings

The university has a requirement to use a face covering when in indoor spaces in order to contribute to the health and safety of the GWU community during the ongoing COVID-19 pandemic. Accordingly, you are expected to use a face covering when attending class, including when you speak. I will do the same.

Acceptable face coverings include:

• Cloth garments that cover the nose and mouth
• Medical-grade disposable masks

If you don't have your own, face coverings are available at various campus locations.

Requests for exemption from wearing a face covering in indoor spaces require prior approval. Please follow this link for more information.

Students with Disabiities [202-994-8250]

Accommodations for students with disabilities are determined and approved by Disability Support Services(DSS). If you, as a student, feel that you need accommodations but have not obtained approval please contact DSS immediately at 202-994-8250 or at https://disabilitysupport.gwu.edu. DSS notifies students and faculty members of approved academic accommodations and coordinates implementation of those accommodations. While not required, students and faculty members are encouraged to discuss details of the implementation of individual accommodations.

Ethical and Respectful Behavior

We expect all students to act in an respectful and ethical way, both with respect to the treatment of their peers in the classroom during discussion but also in the design and execution of their course projects. Actions should meet the expectations of ethical research and follow the norms and proper behavior of the George Washington University community. We strive for an inclusive classroom, which includes but is not limited to anti-racism, anti-sexism, accessibility, LGBTQ+ inclusivity. If you feel like you are unable to use inclusive language and behave in a non-discriminatory way, please drop the class.

University policy on observance of religious holidays

In accordance with University policy, students should notify faculty during the first week of the semester of their intention to be absent from class on their day(s) of religious observance. For details and policy, see “Religious Holidays”.

Reach Out for Success/Wellness

University students encounter setbacks from time to time. If you encounter difficulties and need assistance, it's important to reach out. Consider discussing the situation with an instructor or academic advisor. Learn about resources that assist with wellness and academic success at Health and Wellness Center. If you or someone you know are in immediate crisis, please contact one of the following resources immediately:

• Student Counseling : 202-994-5300
• National Suicide Prevention Lifeline: 1-800-273-8255

Safety and Security

• In an emergency: call GWPD 202-994-6111 or 911
• For situation-specific actions: review the Emergency Response Handbook at: safety.gwu.edu/emergency-response-handbook
• In an active violence situation: Get Out, Hide Out, or Take Out. See go.gwu.edu/shooterpret
• Stay informed: safety.gwu.edu/stay-informed