COP-3402 Systems Software
Syllabus
Table of Contents
Course Details
Course | COP-3402 Systems Software |
School | University of Central Florida |
Semester | Spring 2025 (01/06–04/29) |
Section | 002 |
Prerequisites | CDA 3103C and COP 3502C each with a grade of C (2.0) or better |
Lectures | Mondays and Wednesday, 0900–1020, 01/06–04/21 (inclusive) |
Location | HEC-0125 |
Final | Wednesday, April 21st, 0700–0950 |
Instructor | Paul Gazzillo paul.gazzillo@ucf.edu |
TAs | Brent Pappas, Sanan Hasanov |
Graders | TBD |
Labs
Dates | Personnel | Day | Time | Location |
---|---|---|---|---|
01/17–04/18 | Sanan | Friday | 0930–1020 | HEC-0103 |
01/17–04/18 | Brent | Friday | 1330–1420 | HEC-0118 |
01/17–04/18 | Brent | Friday | 1430–1520 | HEC-0118 |
01/17–04/18 | Brent | Friday | 1530–1620 | HEC-0118 |
01/17–04/18 | Brent | Friday | 1630–1720 | ENG-0302 |
Office hours
Dates | Personnel | Day | Time | Location |
---|---|---|---|---|
01/13–04/25 | Paul | Monday | 1030–1130 | HEC-239 |
01/13–04/25 | Sanan | Tuesday | 1030–1130 | ENG2-237 |
01/13–04/25 | Paul | Wednesday | 1030–1130 | HEC-239 |
01/13–04/25 | Sanan | Friday | 1030–1130 | ENG2-237 |
Office hours will not be held on days on when there are no classes or campus is closed.
Schedule
# | Date | Topic | Video | Board | Reading | HW | Exercise | Project | Project Due |
---|---|---|---|---|---|---|---|---|---|
1 | 01/06 | Introduction | video | none | emacs | hw1 | |||
Tools | |||||||||
2 | 01/08 | Command-line | video | board | lpi sec 1.1–1.2, 2.1–2.7 | hw2 | |||
3 | 01/13 | Version control | 21st ch 4 | hw3 | git | ||||
4 | 01/15 | Build automation | 21st ch 3 | hw4 | hello | ||||
Holiday | 01/20 | (no class) | |||||||
Files | |||||||||
5 | 01/22 | File basics | unix sec 1–9 | hw5 | git (1wk) | ||||
6 | 01/27 | Syscalls | lpi sec 3.1–3.4, 4.1–4.9 | hw6 | |||||
7 | 01/29 | Syscalls | lpi sec 18.1–18.4 | hw7 | fs | hello (2wk) | |||
Processes | |||||||||
8 | 02/03 | Process basics | lpi sec 6.1–6.6 | hw8 | |||||
9 | 02/05 | Fork | lpi sec 24.1–24.2 | hw9 | |||||
10 | 02/10 | Exec | lpi sec 27.1–27.4 | hw10 | |||||
11 | 02/12 | Redirection | lpi sec 5.1–5.5 | hw11 | |||||
12 | 02/17 | Pipes | lpi sec 44.1–44.4 | hw12 | |||||
13 | 02/19 | Shells | 21st ch 2 | hw13 | proc | fs (3wk) | |||
Midterm exam | |||||||||
14 | 02/24 | Review | none | ||||||
Midterm | 02/26 | Exam | |||||||
Compilers | |||||||||
15 | 03/03 | Compiler basics | antlr preface, sec 2.1–2.3 | hw15 | in2post | ||||
16 | 03/05 | Compiler basics | antlr 3.3–3.4 | hw16 | |||||
17 | 03/10 | Linking, runtime | hw17 | in2post (1wk) | |||||
18 | 03/12 | Compiler project | hw18 | proc (3wk) | |||||
Break | 03/17 | (no class) | |||||||
Break | 03/19 | (no class) | |||||||
19 | 03/24 | Functions | hw19 | codegen1 | |||||
20 | 03/26 | Functions | hw20 | ||||||
21 | 03/31 | Variables | hw21 | ||||||
22 | 04/02 | Arithmetic | hw22 | codegen2 | |||||
23 | 04/07 | Branching | hw23 | codegen1 (2wk) | |||||
24 | 04/09 | Pointers | hw24 | ||||||
25 | 04/14 | Pointers | hw25 | codegen3 | |||||
26 | 04/16 | Pointers | none | codegen2 (2wk) | |||||
Final exam | |||||||||
27 | 04/21 | Review | none | ||||||
Final | 04/23 | Exam (0700–0950) | |||||||
Project | 04/28 | codegen3 (2wk) |
Notes:
- All readings (Reading), homework (HW), exercises (Exercise), and projects (Project) are assigned on the date of the row in which they appear. For instance, emacs and hw1 appear in the lecture 1 row with date 01/06, so they are assigned on 01/06. Readings and homework are due the following numbered lectured. Homeworks and readings are due by the next lecture class. The Due column shows exercise and project due dates. See the assignment section for specific rules on due dates and times as well as late policies.
- "hw" means "Homework", e.g., hw1 means Homework 1.
- "none" means there is no homework for that lecture
- "emacs" means the emacs Tutorial.
- "lpi" means The Linux Programming Interface.
- "21st" means 21st Century C.
- The "unix" reading means The UNIX Time-Sharing System.
- The "antlr" reading means Definitive ANTLR 4 Reference.
- Chapter, section, and page ranges are inclusive, e.g., 1.1–1.2 means read both 1.1 and 1.3.
- "ch" means Chapter(s), e.g, ch1 means Chapter 1.
- "sec" means Section(s), e.g., sec 1.1 means Section 1.1.
- "pg" means Page(s), e.g., pg ix–x means Pages ix to x (inclusive)
- "wk" means Week(s), e.g., 1wk means 1 Week.
Assignments
Categories
Category | Number | Points (pt) per Assignment | Total Points (pt) per Category |
---|---|---|---|
Homework | 20x | 1pt | 20pt |
Exercises | 2x | 4pt | 8pt |
Projects | 6x | 8pt | 48pt |
Midterm | 1x | 8pt | 8pt |
Final | 1x | 12pt | 12pt |
Attendance | 1x | 4pt | 4pt |
TOTAL | 100pt |
All assignments are individual assignments. Please see Core Policy Statements for policies about academic integrity.
Late policy summary
Category | (Unexcused) Late Policy |
---|---|
Homework | None |
Exercises | Resubmissions only after initial submission up to two lecture days late |
Projects | (Re)submissions permitted until last Project deadline with 1pt deduction |
Midterm | None |
Final | None |
Attendance | None |
"None" means no late submission accepted except per UCF policy on excused absences and missed coursework.
Homework
- Due before the following lecture at 8:59 AM (just before lecture).
- If an exam or exam review is the next class, then the due date is the following regular lecture.
- Submit via webcourses.
- Graded for genuine effort, not 100% accuracy.
- Homework answers are reviewed in the following lecture, so late homework receives 0pt.
- 20 out of all homeworks count. The rest are dropped.
Exercises
- Due on the date in the schedule by the end of day Orlando time, i.e., 11:59 PM
- Exercises are simple tasks that illustrate tooling and concepts needed for class
- Exercises can be resubmitted up to two lecture days late only if students made an initial submission by the original deadline as these provide core competencies needed for the class after the exercise
- Two lecture days typically means one week, since there are two lectures per week and all assignments are due on lecture days.
- When following days are a break, skip to the next lecture days. For instance, in2post can be turned in late two lecture days later, which would be 03/24, since there is no lecture on 03/17.
- Submit via git on eustis
Projects
- Due on the date in the schedule by the end of day Orlando time, i.e., 11:59 PM
- Projects can be submitted or resubmitted any time up until the final project deadline 04/28 for a one-time late penalty of 1pt deduction per project
- Projects submitted by the due date will have their test cases released
- Projects (re)submitted after the due date will be graded with an alternative, unpublished set of (similar) test cases
- Examples:
- A students submits the fs project on 02/19 by the due date. The projects recieves only 2 out of 8pt. The student resubmits a fully-working project on 03/01 and gets 7 out of 8pt, full credit minus the 1pt late penalty.
- A student submits a fully-working fs project by the due date on 02/19 and gets 8 out of 8pt with no late penalty.
- Submit via git on eustis
Midterm and Final
- In-person exams
- Taken via webcourses or paper per the student's choice
- Material from homework, projects, and lectures
- Final is cumulative but with proportionately more second-half material
- In-class review the lecture before the exam
- Eight double-sided pages (16 total sides, 8 total pages) of reasonably-sized notes for the midterm; 12 for the final.
- Midterm held during class
- Final held during finals week
Attendance
- Taken with UCF Here
- 3pt bonus for >80% attendance
- Notify instructor for excused absences
Bonus project
- Listen for project opportunities during lectures or propose a bonus project idea
- Must demonstrate code and running examples during office hours before the final exam.
- Up to 3pt
- Talk to instructor for more details
Letter Grades
A >= 90%, B+ >= 87%, B >= 80%, C+ >= 77%, C >= 70%, D >= 60%, F < 60%. (minuses may be used in some cases)
Logistics
What | Where |
---|---|
Syllabus | Website |
Lecture notes, videos | Website |
Homework assignments | Website |
Project descriptions | Website |
Project implementation | eustis |
Project submission | git server |
Homework submission | Webcourses |
Exams | Webcourses |
Questions and discussion | Ed Discussion |
Attendance | UCF Here |
Computing Requirements
All students will need access to a computer that can connect to eustis to complete course assignments. For students without their own device, UCF provides both computer labs and loaner devices at no additional cost.
Inexpensive laptops (less than $100) can run a Linux-based OS efficiently. Chromebooks are often very cheap and can use the Chrome Secure Shell Extension to connect to eustis.
eustis
SSH Server | Username | Password |
---|---|---|
eustis.eecs.ucf.edu | Your NID (ab123456) | Your NID password |
Connect to eustis via ssh:
ssh NID@eustis.eecs.ucf.edu
where NID is your UCF NID, e.g., ab123456.
Do not use eustis3 as you won't be able to access the git server.
- Enter your NID password. Alternatively, setup an ssh key.
Off Campus Access
Eustis is only accessible on campus or via VPN.
Please visit https://secure.vpn.ucf.edu to get started.
External guides
(Links are for informational purposes only and their inclusion is not an endorsement of their content.)
- Guides to connecting to an SSH server:
- Guides to connecting to eustis:
- Setting up an SSH key
git server
Programming projects will be submitted as git repositories to gitolite3@eustis3.eecs.ucf.edu. Detailed usage instructions will be provided as part of the course.
Webcourses
Please see Webcourses@UCF Support for help.
Ed Discussion
You will receive an invitation to join the class discussion board by the second week of classes.
UCF Here
The UCF Here mobile app will be used to check-in for attendance using your smartphone.
Web App: https://here.cdl.ucf.edu/
Learn more about setting up and using UCF Here at the following student guide:
https://cdl.ucf.edu/support/webcourses/guides/ucf-here-student-guide/
If you have any questions or problems downloading the app, please contact Webcourses@UCF Support or visit the student guide.
Textbooks
Book | eTextbook Link | Abbreviation | Chapters to Download |
---|---|---|---|
21st Century C | 21st | Preface, 1, 2, 3, 4, 5 | |
The Linux Programming Interface | lpi | 1, 2, 3, 4, 5, 6, 18, 24, 25, 26, 27, 44 |
Download Instructions from UCF Libraries
The digital versions of the course textbooks are available for free through the UCF Libraries. Accessing the textbook requires that you authenticate (log in) with your NID. You are permitted to read the textbook online and/or download content to read offline. If PDF downloads are available for your book, this method is recommended to ensure uninterrupted access to the content. Any unauthorized sharing of the textbook content is in violation of the license agreement between the publisher and university. The license permits access to this textbook for current UCF students, staff, and faculty only. Contact your librarian if you have any questions.
Notice in the first circle that it tells you how many PDF pages can be downloaded per day. It starts at 164 per day, then resets after 24 hours.
Scroll down and see the next circled area. This is where you find the Download PDF links. Do those. Do NOT do the "Read Online" or "Download Book" options on the left (as these options prevent other students from using the eBook).
Thanks to Lily Dubach for getting students book access and providing the instructions above.
Optional recommended texts
- (Dragon Book) Compilers: Principles, Techniques, & Tools, Second Edition by Alfred V. Aho, Monica S. Lam, Ravi Sethi, and Jeffrey D. Ullman. Addison Wesley, 2007
- The Practice of Programming by Brian W. Kernighan and Rob Pike.
- The Definitive ANTLR 4 Reference Second Edition by Terence Parr, 2013.
- Advanced Compiler Design and Implementation by Steven Muchnich. Morgan Kaufman, 1997
- Modern Compiler Implementation in C by Andrew Appel. Cambridge University Press, 1998
- Compiler Construction: Principles and Practice by Kenneth C. Louden, PWS, 1997
- Concepts of Programming Languages, 8th Edition by Robert W. Sebesta. Addison Wesley, 2010.
emacs Tutorial
Go through the complete tutorial emacs, which takes about 30 minutes.
ssh into eustis, replacing
NID
with your UCF NID.ssh NID@eustis.eecs.ucf.edu
Start the emacs tutorial.
emacs -f help-with-tutorial
- Exit the tutorial once finished by pressing
Ctrl-x
thenCtrl-c
.Ctrl
is the "Control" key. Hold it down, then tap the key (x
orc
in this case) and release.
Notes
(Links are for informational purposes only and their inclusion is not an endorsement of their content.)
- Windows Users
In Windows Terminal, Ctrl-v and Ctrl-c may be bound to paste and copy, which will interfere with emacs. Try going to settings, the "Actions" and delete the bindings to Ctrl-v and Ctrl-c. Paste and copy may be still useable with Ctrl-Shift-v and Ctrl-Shift-c. See here and here for others with the same issues.
- Mac Users
In MacOS Terminal, the alt key may not work as expected. Try going to preferences then "Settings" and check the "Use option as meta key". See here for more info.
References
(Links are for informational purposes only and their inclusion is not an endorsement of their content.)
Course Information
Description
This course overviews the use and creation of systems software: file systems; the command-line interface; use of processes and files; the programming environment; use of build systems, editors, and version control; systems programming; compilers.
Learning Outcomes
This course will provide students an understanding of how systems software is used, design, and built. By the end of the course, students should undertand the file system, be conversant in the command-line, learn the unix philosophy of systems programming, be familiar with GNU/Linux development toolchain, and have first-hand experience building systems software, including a shell and a compiler.
Labs
- Labs provide additional support and content to ensure student success this semester and will provide
- Further detail about concepts covered in lecture
- Introduction to some content not shown in lecture
- Lecture Review
- Additional time for Q&A at the end of lab
Core Policy Statements
Academic Integrity
The Center for Academic Integrity (CAI) defines academic integrity as a commitment, even in the face of adversity, to five fundamental values: honesty, trust, fairness, respect, and responsibility. From these values flow principles of behavior that enable academic communities to translate ideals into action. http://academicintegrity.org/
UCF Creed: Integrity, scholarship, community, creativity, and excellence are the core values that guide our conduct, performance, and decisions.
- Integrity: I will practice and defend academic and personal honesty.
- Scholarship: I will cherish and honor learning as a fundamental purpose of my membership in the UCF community.
- Community: I will promote an open and supportive campus environment by respecting the rights and contributions of every individual.
- Creativity: I will use my talents to enrich the human experience.
- Excellence: I will strive toward the highest standards of performance in any endeavor I undertake.
The following definitions of plagiarism and misuse of sources come from the Council of Writing Program Administrators http://wpacouncil.org/node/9 and have been adopted by UCF's Department of Writing & Rhetoric.
Plagiarism
In an instructional setting, plagiarism occurs when a writer deliberately uses someone else's language, ideas, or other original (not common-knowledge) material without acknowledging its source. This definition applies to texts published in print or on-line, to manuscripts, and to the work of other student writers.
Misuse of Sources
A student who attempts (even if clumsily) to identify and credit his or her source, but who misuses a specific citation format or incorrectly uses quotation marks or other forms of identifying material taken from other sources, has not plagiarized. Instead, such a student should be considered to have failed to cite and document sources appropriately.
Responses to Academic Dishonesty, Plagiarism, or Cheating
UCF faculty members have a responsibility for your education and the value of a UCF degree, and so seek to prevent unethical behavior and when necessary respond to infringements of academic integrity. Penalties can include a failing grade in an assignment or in the course, suspension or expulsion from the university, and/or a "Z Designation" on a student's official transcript indicating academic dishonesty, where the final grade for this course will be preceded by the letter Z. For more information about the Z Designation, see http://goldenrule.sdes.ucf.edu/zgrade.
For more information about UCF's Rules of Conduct, see http://www.osc.sdes.ucf.edu/.
In-Class Recording Policy
Outside of the notetaking and recording services offered by Student Accessibility Services, the creation of an audio or video recording of all or part of a class for personal use is allowed only with the advance and explicit written consent of the instructor. Such recordings are only acceptable in the context of personal, private studying and notetaking and are not authorized to be shared with anyone without the separate written approval of the instructor.
Course Accessibility Statement
The University of Central Florida is committed to providing access and inclusion for all persons with disabilities. This syllabus is available in alternate formats upon request. Students with disabilities who need specific access in this course, such as accommodations, should contact the professor as soon as possible to discuss various access options. Students should also connect with Student Accessibility Services (Ferrell Commons, 7F, Room 185, sas@ucf.edu, phone (407) 823-2371). Through Student Accessibility Services, a Course Accessibility Letter may be created and sent to professors, which informs faculty of potential access and accommodations that might be reasonable.
Campus Safety Statement
Emergencies on campus are rare, but if one should arise in our class, we will all need to work together. Everyone should be aware of the surroundings and familiar with some basic safety and security concepts.
- In case of an emergency, dial 911 for assistance.
- Every UCF classroom contains an emergency procedure guide posted on a wall near the door. Please make a note of the guide's physical location and consider reviewing the online version at http://emergency.ucf.edu/emergency_guide.html.
- Familiarize yourself with evacuation routes from each of your classrooms and have a plan for finding safety in case of an emergency. (Insert class-specific details if appropriate)
- If there is a medical emergency during class, we may need to access a first aid kit or AED (Automated External Defibrillator). To learn where those items are located in this building, see http://www.ehs.ucf.edu/AEDlocations-UCF (click on link from menu on left). (insert class specific information if appropriate)
- To stay informed about emergency situations, sign up to receive UCF text alerts by going to my.ucf.edu and logging in. Click on "Student Self Service" located on the left side of the screen in the tool bar, scroll down to the blue "Personal Information" heading on your Student Center screen, click on "UCF Alert", fill out the information, including your e-mail address, cell phone number, and cell phone provider, click "Apply" to save the changes, and then click "OK."
- If you have a special need related to emergency situations, please speak with me during office hours.
- Consider viewing this video (https://youtu.be/NIKYajEx4pk) about how to manage an active shooter situation on campus or elsewhere.
Deployed Active Duty Military Students
If you are a deployed active duty military student and feel that you may need a special accommodation due to that unique status, please contact your instructor to discuss your circumstances.