| Welcome | Schedule | Lab Hours | Code Style Guide |
| Instructor | Teaching Assistants | When & Where |
|---|---|---|
| James Orr Office hours: by apointment |
Annika Petrikin (Head TA), Tobias Pristupin (Head TA), Julian Clark, Frank Liang, Evan Trabitz |
Lectures: 1:00pm-2:20pm OR 2:30pm-3:50pm Monday / Wednesday Lopata 101 Optional Recitation: Friday at 2:00pm in Urbauer 222 |
Course Objectives (or, What You Will Learn)
In this class, we aim to demystify how computer system works, and approach it
from the programmer's perspective. That is, as a programmer, what you need
to know about how the underlying system / hardware works so that you can
write correct / safe / efficient code. We will start out by learning
how your program is transformed into machine-level instructions that your
hardware understands, focusing on x86-64 architecture. Then we move onto
what your compiler can do and cannot do for you. We will also learn
how the hardware memory hierarchy works so that you know what to watch out
for when you need to write high-performing code. We will also discuss various
system-level facilities including linking, virtual memory, memory allocation,
processes, and signal handling. These facilities often work in the background
and makes writing programs much easier. We as programmers do not often think
about them, but understanding how they work provides a holistic view of how
the entire system works together to execute your program. Understanding these
concepts will enable you to become a power programmer!
By the end of this class, you will not only understand how computer
system works, you will also learn what to be mindful of in order to write
correct and efficient code. As additional benefits, you will become
proficient in programming tools such as text editors for coding, gdb
for debugging, Makefile (compilation framework), git, and
Linux command lines.
Piazza
piazza.com/wustl/fall2022/cse361/
All enrolled students will be automatically signed up for the Piazza site. Please register as soon as you get your invitation. All questions should be posted to Piazza. Questions of a personal nature can be submitted as a private message. All questions emailed directly to the instructors or the TAs will receive the response "Please repost to Piazza," where both the question and the answer will reach its full audience. It is in everyone's interest that we maintain this policy; this is absolutely the most effective way to communicate.
Course Description
Introduction to the hardware and software foundations of computer systems. This course provides a programmer's perspective of how computer systems execute programs, store information, and communicate. The course material aims to enables students to become more effective programmers, especially in dealing with issues of performance, portability and robustness. It also serves as a foundation for other system courses, such as compilers, networks, and operating systems, where a deeper understanding of systems-level issues is required. Topics covered include: machine-level code and its generation by optimizing compilers, performance evaluation and optimization, computer arithmetic, memory organization and management, and supporting concurrent computation.
Course Components
As indicated below, you will be graded based on participation (5%), project assignments (56%), a midterm exam (15%), and a final exam (24%).
Every week, we will have two in-person synchronous lectures during the scheduled time. These lectures will be recorded and posted on Canvas after the class period for review purposes and in the even that students need to isolate. We will also have a Canvas quiz posted every week by Wednesday, designed as a self-check on how much content you understood from the lectures this week. These quizzes need to be done by the end of the following Wednesday, but you are mainly graded based on participation, as the correct answers will be shown to you after the first attempt, and you can attempt the questions as many times as you like. Out of the eleven planned quizzes, you get to drop the lowest score.
The project assignments will be distributed / submitted via GitHub. If you don't have a GitHub account, it is time to create one. If you do have one, please remember to link it to your WUSTL email. For all project assignments, you have two-day grace period from the specified deadline to when you submit without incurring late penalty. However, consider these grace period as an automatic extension and you are unlikely to be granted more extensions beyond those two days. Also note that, the two-day grace period applies to projects only; it does not apply to the participation quizzes.
Prerequisites
CSE 131 and CSE 132
Suggested prerequisite: Having CSE 332 helps, but it's not required. CSE 260 or something that makes you think a little bit about hardware may also help. There is no single class that will serve as the perfect prerequisite, but certainly having a few computer science classes under your belt will be a helpful preparation.
Required Text
Bryant and O'Hallaron, Computer Systems: A Programmer's
Perspective, Third edition, Pearson, 2015.
(ISBN-10: 013409266X / ISBN-13: 978-0134092669)
Recommended Text:
Kernighan & Ritchie, The C Programming Language,
Second Edition, Prentice Hall, 1998.
(ISBN-10: 0131103628 / ISBN-13: 978-0131103627)
Other Material
Lecture notes, lab assignments, sample exams and their solutions will be posted on Piazza.
Grading Policy
Participation 5%Late Policy
You have two-day grace period per Lab assignment. It's automatically granted, so you don't even need to ask me or let me know that you want to use them. However, this also means that, beyond those two days, it will be very unlikely to get any more extension on the project. Please note this does not apply to Canvas Participation Quizzes which will not be accepted late.
Exams
The midterm exam will be conducted during class on Monday, October 24, 2022.
The final exam will be on
No alternate exam dates will be available.
Disability Resources
Students with disabilities or suspected disabilities are strongly encouraged to both bring any additional considerations to the attention of the instructor and make full use of the University's Disability Resource Center.
Academic Integrity
Short version: Do not cheat.
Medium version:
Violations of the Student Academic Integrity Policy
include, but are not limited to:
(0) Looking for solutions online,
(1) Plagiarism, (2) Cheating on an Examination, (3) Copying Or
Collaborating On Assignments Without Permission,
(4) Fabrication Or Falsification Of Data Or Records, (5) Other Forms
Of Deceit, Dishonesty, Or Inappropriate Conduct.
Long version:
see the
Undergraduate Student Academic Integrity Policy.
Anyone found to have cheated or to have
helped someone else cheat will face penalties that may include
receiving a negative score equal in magnitude to the value of the
assignment in question (e.g., cheating on an assignment worth 10% of
the course grade would result in -10% being assigned for a total loss
of 20% from the course grade, which is twice as large a loss as simply
not turning in the assignment).
COVID-19 Health and Safety Protocols
Exceptions to course attendance policies, expectations, and requirements because of a COVID-19
diagnosis, symptoms consistent with COVID-19, or exposure to a person with a confirmed or
suspected COVID-19 diagnosis that requires quarantine or isolation will be made in collaboration
between the student and instructor. In these cases, please notify your instructor as soon as possible
to discuss appropriate accommodations.
While on campus, it is imperative that students follow all public health guidelines established to
reduce the risk of COVID-19 transmission within our community. The full set of University
protocols can be found at
https://covid19.wustl.edu/health-safety/.
Title IX, Diversity, and Inclusion
Washington University is firmly committed to addressing and
preventing sexual misconduct on our campuses: please see the
Washington
University statement on new Title IX rules. If a student discusses
or discloses an instance of sexual assault, sex discrimination, sexual
harassment, dating violence, domestic violence or stalking, or if a
faculty member otherwise observes or becomes aware of such an
allegation, the faculty member will keep the information as private as
possible, but as a faculty member of Washington University, they are
required to report it immediately to their Department Chair or Dean or
directly to Ms. Jessica Kennedy, the University's
Title IX Director, at (314)
935-3118 or jwkennedy@wustl.edu.
Additionally, incidents or complaints can be reported to the
Office
of Student Conduct and Community Standards or by contacting WUPD
at (314) 935-5555 or contacting your local law enforcement
agency. To explore options for medical care, protections, or
reporting, free and confidential support resources and
professional counseling services are available through the
Relationship and Sexual Violence Prevention
(RSVP)
Center in Seigle Hall, Suite 435, which can be reached at
rsvpcenter@wustl.edu or
at (314) 935-3445. For after-hours emergency response services, call 314-935-6666 or
314-935-5555 and ask to speak with an RSVP Counselor on call.
Washington University's
Center for Diversity and
Inclusion supports and advocates for undergraduate, graduate, and
professional school students from underrepresented and/or marginalized
populations, collaborates with campus and community partners, and
promotes dialogue and social change to cultivate and foster a
supportive campus climate for students of all backgrounds, cultures,
and identities. The University has a process through which students,
faculty, staff, and community members who have experienced or
witnessed incidents of bias, prejudice, or discrimination against a
student can report their experiences to the University's Bias
Report and Support System team. For procedures and information on
reporting an instance of bias, please visit the
Bias
Report and Support System page on the
Center for Diversity and
Inclusion web site. In order to affirm each person's
gender identity and lived experiences, it is important that we each
ask and check in with others about pronouns. This simple effort can
make a profound difference in a person's experience of safety,
respect, and support. Please see the University's
Pronouns Information page and the Office of the Registrar's
Preferred
Name page for additional information and resources.