COP-3402 Systems Software
Syllabus

All assignments are individual assignments. Please see Core Policy Statements for policies about academic integrity.

• Due before the following lecture at 11:59 AM (in the morning before the noon lecture).
  • If an exam or exam review is the next class, then the due date is the following regular lecture.
  • For example, if homework 15 (hw15) is assigned in lecture 17 on 10/15 then it would be due the following lecture (18) on 10/17 by 11:59 AM.
• Submit via webcourses.
• Graded for genuine effort, not 100% accuracy.
• Homework answers are reviewed in the following lecture, so late homework receives 0pt.

• Due on the date in the schedule by the end of day Orlando time, i.e., 11:59 PM
• Must make an initial submission by the due date
  • No submission by the due date results in 0pt with no opportunity for resubmission
• Submitted projects can also be resubmitted any time up until the final exam 12/09 for a one-time late penalty of 0.5pt deduction per project
• Examples:
  • A student submits the myls project on 10/03, after the due date. The project receives a 0 with no opportunity to resubmit
  • A students submits the myls project on 10/01 by the due date. The projects recieves only 2 out of 6pt. The student resubmits a fully-working project on 11/19 and gets 5.5 out of 6pt, full credit minus the 0.5pt late penalty.
  • A student submits a fully-working myls project by the due date on 10/01 and gets 6 out of 6pt with no late penalty.
• Submit via git on eustis

• Material from homework, projects, and lectures
  • Final is cumulative but focused on 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
• Mid-term held during class
• Final held during finals week

• Examples of participation
  • Showing up to class
  • Asking or answering questions during class
  • Participating in class discussions on edstem
  • Seeking help during office hours

• 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 6pt
• See instructor for more details

A >= 90%, B+ >= 87%, B >= 80%, C+ >= 77%, C >= 70%, D >= 60%, F < 60%. (minuses may be used in some cases)

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.

https://webcourses.ucf.edu

Please see Webcourses@UCF Support for help.

• Connect to eustis via ssh:

  ssh NID@eustis.eecs.ucf.edu
  

  where NID is your UCF NID, e.g., ab123456.

• Enter your NID password. Alternatively, setup an ssh key.

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.

https://edstem.org

You will receive an invitation to join the class discussion board in the second week of classes.

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.

• (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.

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.

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 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

Receiving a work product (e.g., a homework paper or code submitted in response to an assignment) from other individuals (other students in the course, former students, tutors, etc.) is considered "Unauthorized assistance". Giving such a work product to other individuals, either willfully or through negligence, is considered "Helping another violate academic behavior standards." Copying a work product from submissions from past semesters, or copying from an online repository is considered "Plagiarism." You are allowed to discuss class materials and high level concepts related to the assignment with others. However, you must work individually when creating the work product. For programming assignments, you must design algorithms, data structures, and develop code individually. Any violation to the above is considered Academic Integrity Violation. Students found to be in violation of academic integrity will be reported to the Office of Integrity and Ethical Development, in addition to receiving a zero grade on their assignments. Following the report, The Office may conduct hearing, and if found in violation, a student may receive penalties, up to and including dismissal from the university. Unless stated explicitly as team/group assignments, students should assume that assignments are to be performed individually, or ask the instructor for explicit clarification.

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.

1. Integrity: I will practice and defend academic and personal honesty.
2. Scholarship: I will cherish and honor learning as a fundamental purpose of my membership in the UCF community.
3. Community: I will promote an open and supportive campus environment by respecting the rights and contributions of every individual.
4. Creativity: I will use my talents to enrich the human experience.
5. 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.

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.

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.

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.