COP-3402 Systems Software

• Fridays 10:00-12:50 08/28/2020–12/04/2020 (inclusive)
• No class 11/27/2020 (Thanksgiving weekend)

• Friday, 12/11/2020 10:00AM–12:50PM

• Section 0014 Fridays 2:00PM–2:50PM
• Section 0015 Fridays 4:30PM–5:20PM

An overview of system tools and compilers.

• 08/28 Course intro and setup
• 09/04 System tools
• 09/11 Compiler overview, toy compiler implementation
• 09/18 Compiler-compilers, SimpleC overview

The SimpleC language and language analysis in the compiler

• 09/25 Semantic actions, abstract syntax trees
• 10/02 Regular expressions and finite state automata
• 10/09 Grammars and parsing
• 10/16 Type-checking and the symbol table

Generating Intel assembly for a SimpleC program.

• 10/23 Code generation: globals, functions
• 10/30 Code generation: variables, assignment, and expressions
• 11/06 Code generation: arrays and pointers, type-casting
• 11/13 Code generation: control-flow

• 11/20 Program analysis and security

• 12/04 Final exam review

• Due 08/28: git classrooms signup (necessary to grade your project)
• Due 09/11: Virtual machine setup (needed for rest of course)
• End of semester: Participation and course engagement

• Due 09/25: Toy compiler
• Due 10/02: Regular expressions and finite statement automata
• Due 10/09: Grammars and parsing homework

Deadline: 12/04 (12/11 for late submissions)

• Due 10/16: Project 1: Parsing and abstract syntax trees
• Due 10/30: Project 2: Type-checking
• Due 11/13: Project 3: Code generation, functions, variables, and expressions
• Due 12/04: Project 4: Code generation, arrays, pointers, and control-flow

• 1% git classrooms signup
• 1% Virtual machine setup
• 3% Participation and course engagement

• 10% Follow-along implementation of toy compiler
• 5% Regular expressions and finite state automata
• 5% Grammars and parsing
• Effort taken into account in grading

• Four programming projects, 15% each
  • Graded via a test suite
• 2% bonus for a complete compiler

• Content from lectures, homework, and projects

• Homework and projects are considered late after 11:59pm ET on their due date
• Homework assignments may be turned in up to two weeks late and will receive half off
• Programming projects may be turned in or resubmitted
  • after their deadline any time until 11:59pm ET on 12/11
  • with a loss of 2% of your total grade for each project that is late

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

Design and development of compilers, assemblers, linkers, and loaders. Basic operating systems will be covered as well as brief introductions to advanced topics such as optimization, software security, and program analysis.

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.

To protect members of our community, everyone is required to wear a facial covering inside all common spaces including classrooms (https://policies.ucf.edu/documents/PolicyEmergencyCOVIDReturnPolicy.pdf. Students who choose not to wear facial coverings will be asked to leave the classroom by the instructor. If they refuse to leave the classroom or put on a facial covering, they may be considered disruptive (please see the Golden Rule for student behavior expectations). Faculty have the right to cancel class if the safety and well-being of class members are in jeopardy. Students will be responsible for the material that would have been covered in class as provided by the instructor.

Depending on the course of the pandemic during the semester, the university may make changes to the way classes are offered. If that happens, please look for announcements or messages in Webcourses@UCF or Knights email about changes specific to this course.

Students who believe they may have a COVID-19 diagnosis should contact UCF Student Health Services (407-823-2509) so proper contact tracing procedures can take place.

Students should not come to campus if they are ill, are experiencing any symptoms of COVID-19, have tested positive for COVID, or if anyone living in their residence has tested positive or is sick with COVID-19 symptoms. CDC guidance for COVID-19 symptoms is located here: (https://www.cdc.gov/coronavirus/2019-ncov/symptoms-testing/symptoms.html)

Students should contact their instructor(s) as soon as possible if they miss class for any illness reason to discuss reasonable adjustments that might need to be made. When possible, students should contact their instructor(s) before missing class.

If the instructor falls ill during the semester, there may be changes to this course, including having a backup instructor take over the course. Please look for announcements or mail in Webcourses@UCF or Knights email for any alterations to this course.

Accommodations may need to be added or adjusted should this course shift from an on-campus to a remote format. Students with disabilities should speak with their instructor and should contact sas@ucf.edu to discuss specific accommodations for this or other courses.