CSC209H -- Software Tools and Systems Programming -- Winter 2009

Contact Information

Instructor:Michelle Craig
Email: mcraig [at] cs.toronto.edu. Please include "209" in the subject line.
Office: BA 4260
Office Hours: W 3-5, F 1-2

Lectures

SectionLecturesRoomTutorials
DayWF 12-1BA 1200M 12-1
EveningW 7-9BA 1240W 6

Course Materials

Course text books:

Web page: http://www.cs.utoronto.ca/~csc209h

Handouts, assignments, marks, and important course information will be posted periodically on the web page. You should login regularly to check. It would be a good idea to follow the discussions on the bulletin board. You are responsible for announcements made in class, on the web page and on the sticky instructor posts on the bulletin board.

Grading Scheme and Assignment Schedule

Assignment Probable Topics Weight Due at 10 p.m.
1 Shell Programming and Software Tools 10% Tuesday 3 Feb (week 5)
2 C and System calls 10% Monday 23 Feb (week 7)
Midterm 15% (week 8)
3 Processes and IPC 10% Monday 16 Mar (week 10)
4 Sockets and Select 10% Monday 6 April (week 13)
Final Exam 45% See exam schedule

To pass the course you must receive at least 40% on the final exam.

Any section of an assignment in which the C program does not compile on CDF will receive a grade of 0. If you can explain clearly in a remarking request how to fix the problem, your program will be remarked with a 10% penalty.

Late Policy

The late policy is strict. All assignments will be submitted electronically. Assignments are due at 10:00 p.m. on the due date.

Late assignments will be handled based on a system of ``grace days'', as follows: Each student begins the term with 3 grace days. One grace day is 24 hours. If an assignment is due at 10:00 p.m. on a Monday then an assignment handed in by 10:00 p.m. on Tuesday uses one grace day; if handed in by 10:00 p.m. Wednesday, it uses up 2 grace days. The grace days are intended for use in emergencies (e.g., printer failure or car failure). Do not use them to buy an extension because of a busy week or you will be out of luck in a true emergency.

If you are at risk of missing a deadline due to a busy week, rather than use your grace days you should hand in a working (and tested) version of a simpler program. This will be easy to do if you have written and debugged a series of programs that accomplish more and more of the assigned problem.

In the event of an illness or other catastrophe, get proper documentation (e.g., medical certificate), and contact me (by phone, email or in person) as soon as possible. Do not wait until the due date has passed. It is always easier to make alternate arrangements before the due date or test day.

Since your assignments are submitted electronically and will usually be tested using an automated testing program, you must follow the submission instructions exactly. If you do not, you will most likely lose substantial marks on the assignment. If you find you have submitted the wrong file or omitted a file, please notify your instructor as soon as possible.

Remarking requests that result from incorrect submissions will receive a 10% penalty.

Remarking

Requests for remarking must be done using the provided online form explaining in detail what your concern is. Requests for remarking should be submitted no later than one week after the assignment or test has been returned to the class.

Academic Offenses

All of the work you submit must be done by you and your work must not be submitted by someone else. Plagiarism is academic fraud and is taken very seriously. The department uses software that compares programs for evidence of similar code. Please read the Rules and Regulations from the U of T Calendar (especially the Code of Behaviour on Academic Matters).