Operating Systems (Fall 2017) Course Outline

From Soma-notes
Jump to navigation Jump to search

Course Information

  • Course Number: COMP 3000
  • Term: Fall 2017
  • Title: Operating Systems
  • Institution: Carleton University, School of Computer Science
  • Instructor: Anil Somayaji (anil.somayaji at carleton.ca): Mon., Wed. 2:30-3:30 PM in HP 5137
  • Teaching Assistants: (in new TA room 4125 HP)
    • Jean-Elie Jean-Gilles (jeaneliejeangilles at cmail.carleton.ca): Tuesday and Thursday 2:30-3:30 PM
    • Jagger De Leo (jagger.deleo at carleton.ca): Wed. 3:30-4:30 PM, Fri. 10:00-11:00 AM
    • Yuting Wang (yvonnewang at cmail.carleton.ca): Tuesday and Wednesday 11:30-12:30 AM
    • Asar Ghamlouch (asarghamlouch at cmail.carleton.ca): Thursday 11:00-1:00 AM
    • Mahan Niknafs (mahanniknafskermani at cmail.carleton.ca): Thursday 2:30-4:30 PM
    • Akhil Dalal (akhildalal at cmail.carleton.ca): No office hours.
  • Lectures: Tues. and Thurs. 1:05-2:25 PM in AT 102
  • Tutorials (in HP 4155):
    Monday 11:35-12:55 PM
    Monday 1:05-2:25 PM
    Wednesday 8:35-9:55 AM
  • Course Website: http://homeostasis.scs.carleton.ca/wiki/index.php/Operating_Systems_%28Fall_2017%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.

Learning Outcomes

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.

Grading

The marking scheme for this course is:

  • 20% for tutorial participation
  • 20% for the assignments
  • 25% for the midterm on November 2 (Thursday) during class
  • 35% for the final exam (Dec. 17, 7 PM)

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.

Communication

This wiki page 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 cuLearn. While you may discuss assignments there, do not post outright answers to them. You may post in either the Questions and Answers forum or the General Discussion forum.

You may get an account on class wiki so you can edit content there. Email Prof. Somayaji to get one with your preferred username and email address to which a password should be sent. (Note this is not a requirement.)

Collaboration

Collaboration on all work is allowed except for the two tests. Collaboration, however, should be clearly acknowledged.

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

Course Notes/Multimedia

Audio and sometimes video from lectures will be available via the lecture pages on the main course website. These same pages will also contain notes.

Do not rely upon the lectures and notes to cover all material related to this class. You are expected to keep up with the assigned textbook readings and material covered in the tutorials.

Required Textbooks

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.

Course Software

In this course we will primarily working with Lubuntu, a low-resource variant of 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.

University Policies & Resources

Undergraduate Academic Advisor

The undergraduate advisor for the School of Computer Science is available in Room 5302C HP, by telephone at 520-2600, ext. 4364 or by email at undergraduate_advisor@scs.carleton.ca. The advisor can assist with information about prerequisites and preclusions, course substitutions/equivalencies, understanding your academic audit and the remaining requirements for graduation. The undergraduate advisor will also refer students to appropriate resources such as the Science Student Success Centre, Learning Support Services and the Writing Tutorial Services.

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. Some examples of offences are: plagiarism and unauthorized co-operation or collaboration. Information on this policy may be found in the Undergraduate Calendar.

Plagiarism

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.

Unauthorized Co-operation or Collaboration

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.

Academic Accommodations for Students with Disabilities

The Paul Menton Centre for Students with Disabilities (PMC) provides services to students with Learning Disabilities (LD), psychiatric/mental health disabilities, Attention Deficit Hyperactivity Disorder (ADHD), Autism Spectrum Disorders (ASD), chronic medical conditions, and impairments in mobility, hearing, and vision. If you have a disability requiring academic accommodations in this course, please contact PMC at 613-520-6608 or pmc@carleton.ca for a formal evaluation. If you are already registered with the PMC, contact your PMC coordinator to send me your Letter of Accommodation at the beginning of the term, and 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 me to ensure accommodation arrangements are made. Please consult the PMC website for the deadline to request accommodations for the formally-scheduled exam (if applicable) at https://www.carleton.ca/pmc/new-and-current-students/dates-and-deadlines

Religious Obligation

Write to the 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 the Equity Services website: https://www.carleton.ca/equity/

Pregnancy Obligation

Write to the 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 the Equity Services website: https://www.carleton.ca/equity/

Medical Certificate

The following is a link to the official medical certificate accepted by Carleton University for the deferral of final examinations or assignments in undergraduate courses. To access the form, please go to https://www.carleton.ca/registrar/forms