CMSC216 (Summer 2022) Introduction to Computer Systems

Syllabus

The goal of the course is to convey the fundamental concepts that enable programs to execute on real hardware. Those concepts include how the operating system virtualizes the hardware to provide basic services and abstractions to enable a user program to effectively use the available hardware resources. The course also addresses how different programming constructs and idioms work.

The basic abstraction of a program running as one or more threads of control in a single flat address space (a Unix process) is the key to the course. Emphasizing that abstraction as the underlying model for understanding how a program works, from both the user program and hardware perspective (with the OS in between), run as a theme through all topics in the course. Examples include C pointers (to data and functions), function calls and runtime stack management, dynamic memory management in the heap, and the fork/exec system calls.

Prerequisite → C- or better in CMSC132 and MATH 141
Credits → 4

Credits → 4

Nelson Padua-Perez, Office: IRB 2210

You don't need the recommended textbooks to be successful in this course. We believe we provide all the information you need in lecture and lab. In addition, there is ton of information about C/systems programming online. We provide these references as some students prefer to have a textbook.

• Unix Memory Model
• Moving from Java to C
• Pointers and dynamic data structures in C
• I/O
• Standard Libraries
• Testing
• Assembly Language
• Process control
• Systems programming
• Program measurement and optimization
• Multithreaded programming with pthreads
• Libraries and linking
• Dynamic memory management

It is your responsibility to submit regrade requests by a specified deadline; no regrade requests will be processed afterwards. If you don't address any grading concerns by the specified deadline, we are assuming you are satisfied with the grading. If you were sick by the specified deadline, contact your instructor once you are feeling better. Deadlines to address any grading concerns will be available at Grading Concerns.

• Deadlines - All assignments are due at 11:55 pm and you have until 11:55 pm of the next day to submit your work with a 12% penalty. You will not receive any credit for a submission after the late date. The submit server has 11:56 pm as the deadline, otherwise assignments submitted exactly at 11:55 pm will be considered late. As stated above, the deadline is 11:55 pm. A project that is a minute late will be considered a late project.
• Submit Server - You need to use the submit server to submit you work. We will not accept work submitted otherwise (e.g., email, etc.). It is your responsibility to verify your assignment solution works in the submit server, otherwise you may lose most or all of the credit. You will not get any credit for having a solution that works outside of the submit server environment, but not in the submit server. Make sure you do not wait until the last minute to verify your solution works in the submit server.
• Which Assignments Gets Graded - For programming assignments the one with public/release/secret tests that scores the highest in the submit server after a late penalty (if any) has been applied. We only use public/release/secret tests scores to select the submission to grade. Other assignment requirements (e.g., style, methods/functions you must implement, allowed classes, etc.) are not considered. We will evaluate those requirements on the selected submission. We cannot select a particular submission to grade. We will grade the highest scoring submission as described above. Keep in mind you may get a total score lower than expected if the highest scoring submission is missing requirements a lower scoring submission satisfies.
• Closed Assignments - All programming assignments in this course are to be written individually (unless explicitly indicated otherwise). You may discuss assignments only with TAs, instructor or via Piazza.
• No Pop Quizzes/Pop Lab Work - There are no pop quizzes nor pop lab exercises. We will announce in advance (at least one day) if there is any work you need to submit for a grade.
• Projects and exercises are posted by 6 pm on the day specified on the schedule.

• Posting of any assignment solution (even after the course is over) in a publicly available online location (e.g., github, Chegg) is prohibited under the Code of Academic Integrity (facilitation of academic dishonesty). Any student responsible for publicly posting assignments' solutions will be reported to the Office of Student Conduct and risks the sanction of an "XF" in the course.
• Posting of your assignments in a private repository where only selected people (e.g., potential employers) have access is OK.

Office hours get extremely busy the day before an assignment deadline and getting help is not guaranteed. Please start your assignments early so you can address any problems during office hours. We may have some online office hours, but there are no guarantees.

You are responsible for creating backups of your work using any approach (make sure your work is not accessible to others). You are required to submit your work to the submit server often, so you have a backup copy. No extensions will be granted if you lose your work and you had no submit server backups.

We will be using (Piazza) for class communication. You will not be able to register to Piazza yourself. Your instructor will register you using the email address you have in the school system. Posting of any kind of code in Piazza is not allowed.

You are responsible for checking announcements (at least twice a day) we post in the announcements Piazza folder. An oldannouncements Piazza folder will have old announcements.

See the section titled "Attendance and Missed Assignments" available at Course Related Policies.

See the section titled "Accessibility" available at Course Related Policies.

Please read this information carefully. We take academic integrity matters seriously.

1. Academic dishonesty includes not only cheating, fabrication, and plagiarism, but also includes helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. All submitted work must be your own. Cases of academic dishonesty will be pursued to the fullest extent possible as stipulated by the Office of Student Conduct.
2. Situations that often lead to academic integrity violations:
   • A student's friend/roommate shares an assignment's code. Once you provide your code to another student, you are a facilitator, even if you indicate to the student "not to copy-paste" any of it. Actually we had a case in which a student CS degree was revoked for this reason.
   • Students use online resources (github, Chegg, etc.) to find assignments' solutions. The solutions are found by several students and all will be involved in an academic case.
   • Students assume we don't take academic integrity matters seriously.
   • You may only receive assistance from instructors/TAs. We have seen cases in which the use of tutors have led to academic integrity violations (e.g., tutors looked for assignment's solutions online).
3. The Office of Student Conduct is responsible for handling academic integrity matters. After a report is submitted by an instructor, the case is evaluated by the office and it could result in an XF grade, degree revocation, or dismissal from the university.
4. Please read the section titled "Academic Integrity" available at Course Related Policies and the information available at Academic Integrity

If you or your parents have any class concerns, feel free to contact the instructor. If an issue arises with the instructor, report it using the form available at https://www.cs.umd.edu/classconcern.

Ignore this section if you don't know what an ADS student is. If you are an ADS student and you only require additional time, just schedule a location at ADS facilities ahead (several days as specified by ADS) of any exam/quiz. We do not need to meet for additional time (we can sign the ADS form after lecture).

• We only use ELMS for videos.
• At the end of the semester visit (www.courseevalum.umd.edu) to complete your course evaluations.
• Contact your instructor, the Counseling Center, or both, if you are experiencing difficulties that affect your performance in your courses.
• UMD Course related policies are available at http://www.ugst.umd.edu/courserelatedpolicies.html.
• We plan to record lectures and lab/discussion sessions, but technical problems may prevent us from creating a recording. You are still responsible for any material covered in lecture/lab.

All course materials are copyright UMCP, Department of Computer Science © 2022. All rights reserved. Students are permitted to use course materials for their own personal use only. Course materials may not be distributed publicly or provided to others (excepting other students in the course), in any way or format.

Web Accessibility