Instructor: Aline Normoyle

  • Final Exam will be a scheduled exam May 4th, 9:30am (3 hours, open book/laptop) in Park 245

  • Check out the Final Study Guide

Course Info

Welcome to CS223: Systems Programming!

Systems programming provides a foundation for the implementation of programs and toolkits that serve as infrastructure for other software, such as compilers, operating systems, networking APIs, and graphics engines. Topics include pointers, bit representations of data, x86_64 assembly, memory management, processes, and threads. In this class, students will gain hands-on experience implementing low-level algorithms and data structures using C. Furthermore, students will build technical skills related to makefiles, interactive debugging, version control, and command-line shell interaction. C++ and STL will be introduced at the end of the course.

Meeting Times

Activity Location Time


Park 245

Monday and Wednesday 1:10 PM - 2:30 PM


Park 230

Monday 2:40 PM - 4:00 PM

Office Hours - Prof. Normoyle


Wednesdays, 2:30-3:30 PM, or by appointment

Office Hours - Jasmine

Park 231

Wednesdays, 7-8 PM

Office Hours - Synarah

Park 231

Tuesdays, 6-7 PM

Text and Tools

  • Dive into Systems by Suzanne J. Matthews, Tia Newhall, and Kevin C. Webb. Available free online from Dive into Systems

  • Github Account Please go to and register. You will be using github to submit assignments.

  • Slack Please go to Our workspace is BrynMawr-CS223-S23. You can ask questions and request one-on-one help over zoom using this course’s slack channel.


The syllabus may change during the semester. Please check here every week for updates on lecture content, worksheets, and assignments.

Week Date Agenda


Jan 18

Introductions, Hello C


Jan 23,25

More C, Introduction to Pointers


Jan 30, Feb 1

Pointers, malloc/free


Feb 6,8

Pointer-based data structures. Debugging.


Feb 13,15

Binary and Data Representation I


Feb 20,22

Binary and Data Representation II


Feb 27, March 1

Computer architecture, Assembly


March 6,8

Spring Break



March 13,15

The operating system, Processes


March 20, 22

Processes and Inter-process communication (IPC)


March 27,29

Threads I


April 3,5

Threads II


April 10,12



April 17

Memory, Code optimization


April 24,26


Grading Policies

All graded work will receive a grade, 4.0, 3.7, 3.3, 3.0, 2.7, 2.3, 2.0, 1.7, 1.3, 1.0, or 0.0. At the end of the semester, final grades will be calculated as a weighted average of all grades according to the following weights:


Final Exam




Lab work and Quizzes (Code Jams)



Labs and exams

In labs, we will have practice quizzes for the final exam, each structured like a mini-code jam where you work together in teams. Each quiz will have a study guide so you know what types of questions to expect. During lab, you will be randomly assigned a partner and given 40 minutes to complete the questions. The following week in lab, we will go over answers for the previous week.

If you cannot attend a lab, please let the instructor know in advance. There are no make-up opportunities for labs — the missing work will be re-weighted to be part of your final exam.

There will be one final exam for the semester. Details and dates will be released during the semester. Please read the section on accomodations if you are in need of extra time. You must inform us of accommodations or conflicts at least 2 weeks in advance of the exam.

Quizzes and exams will be open book. You will be given sample questions beforehand to help you study. Warning! Do not rely heavily on your notes for quizzes. You will need to have concepts memorized in order to finish within the time limit.

Homeworks and exercises

This course features weekly lab exercises and assignments which are an important component of the class.

Lab exercises will be passed out in lab. These exercises are intended to be short and will typically ask you to reproduce demos from class or tackle concepts you will need for your assignment. Lab execises should be handed in at the end of lab.

Class exercises will be passed out in class. These exercises are intended to be short and will typically ask you to practice concepts from lecture. Class execises should be handed in at the end of class.

Assignments will be posted Saturdays and due Friday before midnight. You are strongly encouraged to start early so that you can ask questions. See the syllabus for links to the assignments.

You will submit your assignments electronically using Dropbox.

Late Policy

Because practice is so important for learning how to program, we will do frequent exercises, assignments, and quizzes throughout the term.

The purpose of this work is to give you hands on experience with the topics from class. Most of this work will be due in lecture or labs. The weekly time commitment for this course is aimed to be approximately 10 hours per week.

Assignments will generally be due on Wednesdays. However, you may request up to one late days (until Thursday) if necessary. No submissions beyond Thursday will be accepted. This allows us time to grade assignments. And it helps prevent you from falling behind.

If you need to miss a code jam, let the instructor know and the missed credit for the code jam will be added to the final exam.

You may need to provide a doctor’s note if you need special accomodations due to a medical emergency.

Academic Integrity

At Bryn Mawr, we assume students are trustworthy and work with honesty and integrity. Look here for information about Bryn Mawr’s Honor Code.

As you progress in this course, you will see that programming is a creative process, similar to writing. The same problem can be solved in multiple ways. It’s essential that you develop your own skills for developing algorithms and implementing them through programs.

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 should be your own with the following permissible exceptions: code distributed in class, and code found in the course text book. 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.

  • Please don’t hesitate to ask the awesome teaching assistants (TAs) for help. They provide TA hours most week nights and are excellent mentors!

  • Please discuss the readings and associated topics with each other. Work together to understand the material. Reading groups to discuss the material are highly recommended — we will explore many ideas and it helps to have multiple people working together to understand them.

  • It is fine to discuss the topics covered in the homeworks, to discuss approaches to problems, and to sketch out general solutions. However, you MUST write up the homework answers, solutions, and programs individually without sharing specific details, mathematical results, program code, etc.

  • Under NO circumstances should you share computer code with another student. Similarly, you are not permitted to use code found on the internet for any of your assignments.

  • Exams, of course, must be your own individual work.

Academic Accommodations

All classes will be recorded and close-captioned. Links to lectures will be posted on the class syllabus.

Any student who has a disability-related need to record this class first must speak with the Director of Access Services, Deb Alder, as part of university policy. Class members need to be aware that this class may be recorded.

To receive an accommodation for a course activity (such as more time on quizzes and exams), you must have an Accommodation Letter from the Office of Student Disability Services and you need to contact us to work out the details of your accommodation at least two weeks prior to the activity. Forms can be emailed to me, the instructor.

You are also welcome to contact us privately to discuss your academic needs. However, all disability-related accommodations must be arranged, in advance, through Student Disability Services.

Students needing academic accommodations for a disability must first register with Access Services. Students can call 610-526-7516 to make an appointment with the Director of Access Services, Deb Alder, or email her at to begin this confidential process. Once registered, students should schedule an appointment with the professor as early in the semester as possible to share the verification form and make appropriate arrangements. Please note that accommodations are not retroactive and require advance notice to implement. More information can be obtained at the Access Services website. (

Academic support


Out of consideration of others, we ask that no one return to campus with COVID or any other easily communicable virus. If you are experiencing any symptoms, please self-test for COVID prior to your initial return to campus.

For a full outline of college policies, please read the documentation here.

Title IX

Bryn Mawr/Haverford College is committed to fostering a safe and inclusive living and learning environment where all can feel secure and free from harassment. All forms of sexual misconduct, including sexual assault, sexual harassment, stalking, domestic violence, and dating violence are violations of Bryn Mawr/Haverford’s policies, whether they occur on or off campus. Bryn Mawr/Haverford faculty are committed to helping to create a safe learning environment for all students and for the College community as a whole. If you have experienced any form of gender or sex-based discrimination, harassment, or violence, know that help and support are available. Staff members are trained to support students in navigating campus life, accessing health and counseling services, providing academic and housing accommodations, and more.

The College strongly encourages all students to report any incidents of sexual misconduct. Please be aware that all Bryn Mawr/Haverford employees (other than those designated as confidential resources such as counselors, clergy, and healthcare providers) are required to report information about such discrimination and harassment to the Bi-College Title IX Coordinator.

Information about the College’s Sexual Misconduct policy, reporting options, and a list of campus and local resources can be found on the College’s website:

Links that are related to the course may be posted here. If you have suggestions for links, let us know.