Instructors: A.L. Hunter Email: email@example.com (just "andria" from CDF-PC) Office Hours: Thursday 5:00 - 7:00 p.m. Rm. SF 2302D (for January 27th only: office hour is 3-5 p.m.) Lecture: L5101 Tuesday 7:10 p.m. Rm. SS 2102 (weeks 2 & 3 only: lectures start at 6:10 p.m in SS 2102) J.N. Clarke Email: firstname.lastname@example.org (just "clarke" from CDF-PC) Office: SF 2304C, Phone: (416)978-4058 Office Hours: 1:30-3:00 p.m. Tuesday and Thursday Lecture: L0101 WM 10:10 a.m. Rm. SS 2102 (weeks 1-3 only: lecture on Friday at 10:10 a.m in SS 2102) Timetable: Lectures: Tuesdays at 7:10 p.m., Room 2102, Sidney Smith Hall (for weeks 2 and 3 only: lectures are at 6:10 p.m. in SS 2102) Now that the TA strike is over, all lectures will be from 7-9 pm in SS 2102. You should go to your assigned tutorial section from 6-7 pm. Tutorials: Tuesdays at 6:10 p.m., starting the fourth week of classes Tut. Who? (lastname) Tutor Room 1 A - Chin Daniel Taranovsky SS 2102 Sidney Smith 2 Chio - Ka Labonny Biswas SS 2111 Sidney Smith 3 Kb - Ma Caroline Pantofaru SS 1088 Sidney Smith 4 Mb - Sib Mary Huang LM 155 Lash Miller 5 Sic - Z Nikola Koncar LM 157 Lash Miller You must attend the assigned tutorial unless given permission to do otherwise by the instructor. There is no tutorial during the second and third week of classes. These tutorials have been replaced with lectures, all taking place in room SS 2102, starting at 6:10 p.m. Training sessions: Instead of having tutorials during the first few weeks of classes, one-hour training sessions will be held at the PC site in the Gerstein Science Information Centre to introduce you to the PCs and the software you will be using. You can attend any session you like, but if there are too many students present for the space available, you will be accommodated on a first-come, first-served basis. Official dates for the training sessions are listed on the CSC108 web site. Tutors' Office Hours: You are welcome to attend any office hour regardless of your assigned tutorial or lecture section. The office hours are held at the PC site in the Gerstein Science Information Centre, at these times: Tuesday - Thursday 2:10 - 3 p.m. Monday and Thursday 7:10 - 8 p.m. These office hours begin the third week of the term. There may be some office hours that cannot be staffed because of the difficulties of filling all the slots. Required Text books: (available from the Bookstore) "The text": D. Arnow and G. Weiss, Introduction to Programming Using Java: An Object-Oriented Approach ("Java 2 Version", Addison-Wesley, 1999) "The reference": The Java API, an excerpt from J. Lewis and W. Loftus, Java Software Solutions: Foundations of Program Design (Addison-Wesley, 1998) "The PC handbook": J.N. Clarke (ed.), How to prepare programs on the Computer Science PC facility. You will also need to buy at least one disk, as described in the PC handbook. Original Grading Scheme: This grading scheme will not be used, due to the TA strike. See below for the revised grading scheme. six assignments 40% Due dates T.B.A. test 15% During tutorial, Feb. 22 final exam 45% Three hours, open book (text & reference only) You must achieve at least 30 out of 100 on the exam to pass the course. Revised Grading Scheme: Since the TA strike is over, we're switching back to the following grading scheme that's more similar to the original grading scheme: Item Weight(%) Due date Asst 0 3 Thu January 20 (electronic only) Asst 1 6 Thu February 3 (electronic only) Asst 2 6 Thu March 2 (electronic only) Asst 3 10 Tue March 14 @ 6pm (in tutorial & electronic) Asst 4 10 Tue March 28 @ 6pm (in tutorial & electronic) Asst 5 5 Tue April 4 @ 6pm (in tutorial) Test 15 Tue February 22 @ 6pm (in tutorial) Exam 45 During exam period You must achieve at least 30 out of 100 on the exam to pass the course. Course Notices: You should pay attention to the course web site and newsgroup, which are accessible from the CDF-PC web site (http://www.cs.utoronto.ca/DCS/Undergrad/CDFPC). Most handouts for the course are available only in class or on the web site. Lists of student accounts and a few other announcements are posted on a bulletin board in the hall near Sandford Fleming room 2304. Changing from CSC 148 If you are changing from CSC 148 to CSC 108, you must notify your CSC 108 instructor. There are standard procedures for handling your tutorial, computing account, and assignments. Course Schedule: Week Monday Text Scheduled topics # Date Chap. Assignments/Tests 1 Jan. 3 1 introduction to object-oriented ideas; running a simple program 2 Jan. 10 2 message passing, methods, parameters; strings. These early chapters present a lot of material that you'll want to reread later in the course. Section 2.3 is a good example. Assignment A due Jan 13, Weight: 0 3 Jan. 17 3, 4 input from keyboard and files. Chapter 3 may not be discussed in detail in class, but you should read it carefully. Assignment 0 due Jan 20, Weight: 3 4 Jan. 24 4 cont. defining classes and writing methods Assignment B due Jan 27, Weight: 0 5 Jan. 31 5 primitive types; mathematical calculations. We may not cover all the class design in chapter 5, but you need to read it as part of learning to build programs. Assignment 1 due Feb 3, Weight: 6 6 Feb. 7 6 "if" statements and their uses. Assignment C due Feb 10, Weight: 0 Feb. 14-18 Reading Week - no classes 7 Feb. 21 8, 9 loops, introduction to Vectors. Test Feb 22 (at 6pm), Weight: 15 8 Feb. 28 7 testing and style. Assignment 2 due Mar 2, Weight: 6 Note: Mar. 3 is the "drop date." 9 Mar. 6 9, 10 Vectors and arrays. 10 Mar. 13 10, 13 In weeks 10 to 12, searching and sorting will be used as the basis for an introduction inheritance and polymorphism (from chapter 13) and complexity (chapter 10). Assignment 3 due Mar 14 (at 6pm), Weight: 10 11 Mar. 20 Assignment 4 due Mar 28 (at 6pm), Weight: 10 12 Mar. 27 13 Apr. 3 review. Assignment 5 due Apr 4 (at 6pm), Weight: 5 Total Weight for Term: 55
Your instructor's lectures are unlikely to follow exactly the sequence of topics outlined above. You should be reading along in the text roughly as shown, but be prepared to look ahead to chapters listed for later weeks. This is especially likely to be necessary during the first four or five weeks of the course.
Each chapter in the text ends with a "GUI Supplement." You should read these sections, but no course material will be based directly on them.Other Notes: Assignments are due at the beginning of tutorials, unless you are told that only electronic submission is required. For assignments that are due at the beginning of your tutorial (A3, A4, A5), here are the penalties for late submissions: Time of Submission Place of Submission Penalty By 6:10 p.m. Tuesday Your Tutorial Room No penalty By end of lecture Tuesday Lecture Room SS2102 -10% (of max. mark) By end of office hour Thurs Office Hour SF2302D -20% By 3:00 p.m. Monday Drop Box outside SF2305A -30% No assignments are accepted after 3 p.m. on Friday. The late times are only waived for a good reason such as a documented medical or other emergency. Discuss such excuses with the lecturer, not with your tutor. Some assignments will be submitted electronically only (you will not be handing in a paper copy of them at the beginning of tutorial). These assignments will usually be due at 9:00 a.m. on Thursday, and the late penalty will be -10% if submitted by 3:00 p.m. Friday and -30% if submitted by 3:00 p.m. Monday. No assignments are accepted after 3:00 p.m. on Monday. If the late penalty is different than this, it will be announced on the course web page. The work you submit must be your own, done without participation by others. It is an academic offence to hand in anything written by someone else without acknowledgement. Suspected copying will be reported to the Faculty. Illness and other troubles: If you are too sick to write the midterm test or to hand in an assignment on time, you must contact your instructor (not your tutor!) by e-mail or in person, as soon as possible. If you are too sick for the final examination, phone your college registrar's office, instead of your instructor. Tips for Success: Be sure to read and reread the text book. To become a good programmer, the key is to practise, practise, practise!
[ CSC108 Home | Outline | Announcements | Newsgroup | Assignments | Exams | Lectures | Marks | Links ]
© Copyright 2000. All Rights Reserved.