Dr. Woit's HomePage        
CPS590 Course Management Form
CPS590 Topics


TMU

Course Outline

CPS590: Introduction to Operating Systems


. Check page periodically

Students are responsible for checking the D2L Announcements daily and following all instructions so transmitted.

All typos, inconsistencies, etc.: Any such anomalies shall be resolved solely at the instructor's discretion.


Instructor Dr. Woit
Dept. of Computer Science, Toronto Metropolitan University
Office: ENG277
Tel: 416-979-5000, x7063
Email: dwoit at torontomu dot ca (see Course Email Policy below)
Office Hours: Tue 310-400
TAs Jorge Lopez jlopez@torontomu.ca (Section 1,2,4 lab)
Monty Gole mgole@torontomu.ca (Section 5,8,11 labs) (Lead TA)
Vanessa Lobo vanessa.lobo@torontomu.ca (Section 3,6,7,9,10 labs)
Prerequisites CPS 393, CPS 305
Calendar Description Introduction to O/S (system calls, interrupts, synchronous and asynchronous traps, O/S structure), using processes (process communication and synchronization), primitive communications (signals and signal management calls), pipes, messages, semaphores, shared memory, memory management, file systems, and (time permitting) remote procedure calls.
Compulsory Textbook
Operating Systems; Intervals and Design Principles. William Stallings. Either 8th or 9th Edition.
The 9th Ed is available in e-text or print from the publisher
Reference (not required): references of your choice for ANSI C and Bash, such as:
http://www.gnu.org/software/bash/manual/bashref.html
C Reference Card
https://www.gnu.org/software/gnu-c-manual/gnu-c-manual.html
Course Organization 3 hrs. lecture per week for 12 weeks.
Learning Objectives The student will be able to identify, create, implement, employ, manipulate, and reason about the OS topics and algorithms studied, within the context of the procedural paradigm, and specifically, ANSI C and Linux Operating System. The student will be able to solve the problems from the text, from class and labs, other similar problems, and those that build upon them.
Synopsis of Academic Focus and Scope The course will present both a theoretical and practical treatment of introductory-level Operating Systems.
Course Evaluation
Term Work Weight Date
Test 1 28% Sat Feb 10
Test 2 28% Sat Mar 23
Test 3 (Exam) 37% Exam Period
Labs Marks* 07% Lab answers due Mon after corresponding Lab (11:59pm)
For due dates see: /usr/courses/cps590/Labs/LAB_DUE_DATES_AND_SUBMITTING
100% Exam 100% If Exam mark is greater than weighted average above
To Pass the Course obtain at least 50% of the weighted average of the 3 tests OR 50% on Exam
Labs
  • In person, in your scheduled lab room, with your TA.
  • ATTENDANCE IS REQUIRED.
  • During the lab time, work on answering the provided lab questions (and homework/text questions if you finish the lab.)
  • For each lab, you may be required to submit specific (not necessarily all) answers (these will be indicated in the lab question file).
  • Lab solutions are NOT provided; however, your TA can help you check your answers after submission, time permitting.
  • The Lead TA is: Jorge Lopez jlopez@torontomu.ca
*Lab Marks During the term, you attend labs, and submit required answers, without knowledge of which will count toward Lab Marks. At end of term, we will announce which labs will count, and how they count, as follows:
  • Lab mark is some combination of attendance (A%) and marked lab submissions (L%) , where
    • both A and L are in [0%,7%], and A + L = 7%.
    The exact values of A and L are not provided in advance. Examples of possible A and L are:
    • A=7%, L=0% (100% attendance based)
    • A=3.5%, L=3.5% (50% attendance and 50% marked submissions)
    • A=0%, L=7% (100% marked submissions)
    • etc.
  • Calculating L: By the end of term, you will have submitted answers to many individual lab questions. At end of term, one or more of these answers will selected for grading, and their grades will combine equally for L. Selected answers must have been submitted by their given due dates in order to be eligible for grading.
  • Calculating A: By the end of term, it is expected attendance will have been taken for all/most labs. At end of term, one or more attendance marks will be selected to combine equally for A.
Marking
  • Normally, email/see your own lab TA if you have any questions regarding labs, marking, etc.
  • To escalate the issue, email/see the Lead TA, who has final authority on all lab and marking issues.
  • The Lead TA is: Jorge Lopez jlopez@torontomu.ca
Educational Technology Students are required to use bash shell and gcc C-compiler on Computer Science moons for all course work.
Evaluation Guidelines
  • Official evaluation marks are recorded on D2L only.
  • Evaluations written in pencil (when applicable) will never be re-evaluated.
  • Any error in grading must be brought to the attention of the grader for that evaluation (e.g., TA or instructor) within 24 hours of evaluation being returned (papers handed back for written evaluations, electronic posting of grade for electronic evaluations.) Students must report grading errors using the re-evaluation form provided by the instructor/TA, when required to do so.
  • Final Exam is cumulative (covers material from tests).
  • Late submissions of any course work are not accepted.
Missed Evaluations Normally receive a mark of zero. See the following for remission: Missed Tests/Examinations (Academic Consideration Request)

If the missed evaluation is the final exam, students are required, in addition to the forms mentioned in the link above, to petition for an INC grade with the Incomplete Grade Request Form. To be allowed to write the makeup exam, you must send a completed Incomplete Grade Request Form to the instructor within 3 days of the exam, and have a verified Academic Consideration Request.
Course Email Policy
  • Emails MUST contain "cps590" or "CPS590" somewhere in the subject (WITH NO SPACES!). Emails without this will not be read or answered.
  • It is best to see professor in class or office hours, as emails are not guaranteed to be answered, as follows:
  • Emails will be answered during office hours, time permitting, in order of arrival (from/to proper accounts as defined below).
  • Emails professor considers no longer (or not) relevant will not be answered.
  • Email must be to: dwoit at torontomu dot ca
  • Email must be from: your cs account or torontomu.ca account. Email sent to/from any other accounts will not be answered (e.g., gmail).
  • Email questions the professor deems appropriate to the whole class will be answered in Announcements or in class (not via email response).
University Policies Students are required to adhere to all relevant university and departmental policies including those found in D2L and/or on the following URLs: http://torontomu.ca/senate/policies https://www.torontomu.ca/cs/current-undergraduate-students/forms-policies/
Resources Available at TMU
  • CS Debug Room offers individual and group help with this course.
  • Student Learning Support offers individual and group help with computer science, writing, math, study skills and transition support.
Academic Misconduct Generally for TMU and CS: Academic Misconduct
Specifically for this Course: Course Academic Misconduct
Non-Academic Conduct see TMU Student Code of Non-academic Conduct


Further Course Information:

This is now a common page for all my courses, and is located at http://www.cs.torontomu.ca/~dwoit/courses/courseInfo.html
Modifications to the course procedures will be made in consultation with the course students.

. Check page periodically for modification.

Dr. Woit's HomePage        
CPS590 Course Management Form
Dr. Woit's CPS590 Topics