Operating Systems (Fall 2021) Course Outline
- Course Number: COMP 3000
- Term: Fall 2021
- Title: Operating Systems
- Institution: Carleton University, School of Computer Science
- Instructor: Anil Somayaji (anil.somayaji at carleton.ca): by appointment via Teams and Tue. and Thu. 11:30-12:30 via zoom (see cuLearn for link)
- Teaching Assistants: (office hours via Teams chat)
- Braeden Brooking (braedenbrooking at cmail.carleton.ca): Mon. 4-6 PM
- Braeden Hall (braedenhall at cmail.carleton.ca): Thu. 1:30-3:30 PM
- Cameron O'Leary (cameronoleary at cmail.carleton.ca): Wed. 10-12
- Heli Alpeshkumar Patel (helialpeshkumarpatel at cmail.carleton.ca): Fri. 8-10 AM
- Jade Li (lisali4 at cmail.carleton.ca): Wed. 12-2 PM
- Jake Jazokas (jakejazokas at cmail.carleton.ca): Fri. 11-1 PM
- Josh Babu George (joshbabugeorge at cmail.carleton.ca): Mon. 9-11 AM
- Nilofar Mansourzadeh (nilofarmansourzadeh at cmail.carleton.ca): Tue. & Fri. 2:30-3:30 PM
- Lectures: Tue. and Thu. 10:05-11:25 AM via Zoom
- Tutorials (Online): Asynchonous
(Official times: A1: Mon. 8:35-9:55 AM, A2: Fri. 2:35-3:55 PM, A3: Fri. 8:35-9:55 AM)
- Course Website: https://homeostasis.scs.carleton.ca/wiki/index.php/Operating_Systems_%28Fall_2021%29
Official Course Description
Operating system implementation course stressing fundamental issues in design and how they relate to modern computer architectures. Assignments involve the modification and extension of a multitasking operating system.
Includes: Experiential Learning Activity
Prerequisites: COMP 2401 with a minimum grade of C- and (COMP 2402 or SYSC 2100).
By the end of this course, students should:
- be able to write C code that uses low-level Linux services and should be able to implement simple Linux kernel extensions (modules),
- have a strong conceptual model of how an operating system works that allows them to determine the relative role of application and operating system code when debugging software, and
- understand the basic use and architecture of virtual-machine based cloud architectures.
Note that in order to achieve these objectives students should have come into this course with a strong background in C programming and general application development.
The marking scheme for this course is:
- 4% for lecture participation
- 18% for tutorial participation
- 18% for the assignments
- 25% for the Midterm, Oct. 19th during class
- 35% for the Final Exam (during the final exam period)
I also calculate grades using alternative marking schemes at the end of the semester, assigning the highest grade for each student from any of the marking schemes. Thus your final grade may be higher than might be suggested by strict following of the above scheme.
The midterm and final will not be proctored but I will conduct selected and randomized post-exam interviews. See Collaboration, below.
Communication and Lectures
The course website page listed above is the canonical source of information on this course. Please refer to it for updates. When significant changes are made to this document it will be either announced in lecture and/or posted in the course discussion forum.
Course discussions will be on Microsoft Teams. While you may discuss assignments there, do not post outright answers to them (unless the solutions have been posted). You may discuss tutorials freely.
Tutorial, assignment, and exam submissions will be through Brightspace. Grades will also be posted there.
All lectures will be conducted via Zoom. Lectures will be recorded and links posted to the course wiki. Lecture participation is based on interactions during lecture, such as questions asked and participation in online polls. You do not need to participate in every lecture to get full marks for this; the grade is based on the quality and quantity of your interactions. Note that grades will be calculated so that participation can only improve your grade.
Collaboration on all work is allowed except for the midterm and final. Collaboration, however, should be clearly acknowledged. See below for further details.
The midterm and final exams will be open book, open note, open Internet, because they will not be actively proctored. Those outside resources will not be of much use, however, if you have not prepared by completing the tutorials and assignments. Your answers should be your own and you are not allowed to collaborate during the exams.
Random and selected exams will be chosen for 10-15 minute interviews. You may also volunteer to be interviewed. These interviews are to verify grading quality and to make sure that the work is your own. The Dean will be contacted if during an interview it becomes clear that a student is not the sole author of any exam.
For assignments, while you may get help from others and even collaboratively solve technical problems, the code and answers submitted should all be your own work. For example, you may not divide an assignment into parts, give a part to another student or anyone else to solve, and then submit that work as your own. You have to have participated in the creation of every part of your submitted work. An easy way to make sure this happens is never share files regarding coursework or copy and paste answers into email. Instead, meet together (virtually) to work on an assignment and then separate to write up your solutions.
Similarity between submitted assignments and projects that has not been appropriately documented will be treated as plagiarism - the same as copying on a midterm or a final - and will be submitted to the Dean for disciplinary action.
Video from lectures will be available via the lecture pages on the main course website within a day after lectures are delivered. These same pages will also contain code and notes given in class.
Do not rely upon the lectures and notes to cover all material related to this class. Mastery of the tutorial material is essential for doing well on the assignments and exams. Textbook and other outside readings should be used as supplements to help you understand concepts covered in lecture and tutorial.
The course will be using the textbook Operating Systems: Three Easy Pieces. The chapters of this textbook are available for free online; you can also buy a full epub, PDF, or paper copy if you wish.
Individual chapters will be linked with the lectures associated with them. You should plan on reading the assigned chapters before coming to class, as the material in lectures will be easier to understand then. The lectures are designed to supplement the textbook, not replace them.
This course focuses much more on reading code rather than writing code. Thus, John Aycock's book, Reading and Modifying Code, is worth reading to better understand how reading code differs from writing code.
In this course we will be working with the Ubuntu Linux distribution. You may use other Linux distributions in the tutorials to complete the assigned work; there will be differences, however, in some aspects (such as installing software), particularly if you use a distribution not based on Ubuntu or Debian.
Undergraduate Academic Advisor
The Undergraduate Advisor for the School of Computer Science is available in Room 5302C HP; or by email at firstname.lastname@example.org. The undergraduate advisors can assist with information about prerequisites and preclusions, course substitutions/equivalencies, understanding your academic audit and the remaining requirements for graduation. The undergraduate advisors will also refer students to appropriate resources such as the Science Student Success Centre, Learning Support Services and Writing Tutorial Services.
University Policies & Resources
For information about Carleton's academic year, including registration and withdrawal dates, see Carleton's The Academic Year.
Pregnancy, Religious, or other Obligation
For pregnancy, religious, or other equity-related obligations please contact your instructor with any requests for academic accommodation during the first two weeks of class, or as soon as possible after the need for accommodation is known to exist. For more details, visit Equity Services.
Academic Accommodations for Students with Disabilities
Academic Accommodations for Students with Disabilities If you have a documented disability requiring academic accommodations in this course, please contact the Paul Menton Centre for Students with Disabilities (PMC) at 613-520-6608 or email@example.com for a formal evaluation or contact your PMC coordinator to send your instructor your Letter of Accommodation at the beginning of the term. You must also contact the PMC no later than two weeks before the first in-class scheduled test or exam requiring accommodation (if applicable). After requesting accommodation from PMC, meet with your instructor as soon as possible to ensure accommodation arrangements are made. For more details, visit the Paul Menton Centre website.
Survivors of Sexual Violence
As a community, Carleton University is committed to maintaining a positive learning, working and living environment where sexual violence will not be tolerated, and is survivors are supported through academic accommodations as per Carleton's Sexual Violence Policy. For more information about the services available at the university and to obtain information about sexual violence and/or support, visit Sexual Assault Support Services.
Accommodation for Student Activities
Accommodation for Student Activities. Carleton University recognizes the substantial benefits, both to the individual student and for the university, that result from a student participating in activities beyond the classroom experience. Reasonable accommodation must be provided to students who compete or perform at the national or international level. Please contact your instructor with any requests for academic accommodation during the first two weeks of class, or as soon as possible after the need for accommodation is known to exist. For more details, see the policy.
Student Academic Integrity Policy
Student Academic Integrity Policy. Every student should be familiar with the Carleton University student academic integrity policy. A student found in violation of academic integrity standards may be awarded penalties which range from a reprimand to receiving a grade of F in the course or even being expelled from the program or University. Examples of punishable offences include: plagiarism and unauthorized co-operation or collaboration. Information on this policy may be found here.
As defined by Senate, "plagiarism is presenting, whether intentional or not, the ideas, expression of ideas or work of others as one's own". Such reported offences will be reviewed by the office of the Dean of Science. Standard pentaly guidelines can be found here.
Senate policy states that "to ensure fairness and equity in assessment of term work, students shall not co-operate or collaborate in the completion of an academic assignment, in whole or in part, when the instructor has indicated that the assignment is to be completed on an individual basis".
Please see above for the specific collaboration policy for this course.