CSC 104H: The Why and How of Computing University of Toronto, Winter 2011 Lecturer: Tim Capes capestim@cs.toronto.edu Lectures: Tuesday 9AM, MP103 Thursday 9AM, MP103 Lecturer Office Hours: Tuesday 10AM, BA2200 (not first day of class) Thursday 10AM, BA2200 Course Web Page: www.cs.toronto.edu/~capestim/csc104/ Tutorials: Fridays 9AM starting second week of class. Student # ending in 0 or 1 in BA3304, Student # ending in 2 or 3 in BA3308, Student # ending in 4 or 5 in BA2165, Student # ending in 6 or 7 BA2175 and Student # ending in 8 or 9 BAB024. Textbook: Mark Guzdial and Barbara Ericson, Introduction to Computing and Programming in Python, a Multimedia Approach, 2nd Edition. Topics to be Discussed: Hardware, Software and Data; Concepts in Problem Solving with Computers; Data representation; A media-driven introduction to programming; Social issues in computing; A brief history of computing. Schedule: First Lecture January 11th 2011. Last Lecture April 7th 2011. Grading Scheme: Assignment #1 (15%), due February 8th 2011 by 10AM. Assignment #2 (10%), due March 3rd 2011 by 10AM Assignment #3 (10%), due March 17th 2011 by 10AM Assignment #4 (10%), due March 31st 2011 by 10AM Test #1 (10%) on March 1st 2011 Test #2 (10%) on March 22nd 2011 Final Exam 35% see Arts & Science Final Exam Schedule once Posted Assignment Submission: Electronic submission on CDF will be covered in the course. These assignments do not require paper submission. Paper assignments will be handed in to the drop-box in BA2220 labelled CSC104 or to the Lecturer in Class. No assignments should be handed in to Teaching Assistants. Late assignments will only be accepted under exceptional circumstances and with a written explanation sent separately by e-mail. To submit an assignment late, submit it in the usual way and then send the lecturer an e-mail message or bring him a note. Any disagreements with the grade assigned to an assignment or test should normally be submitted to the lecturer within about a week of its return. Bulletin board There is a bulletin board which you are encouraged to use to communicate with other students in this course. Please see the link on the course web page. However, it is not an official part of the course and we will not necessarily be reading it; see me or TAs in office hours or send e-mail. Do not post a test message. Wait until you have something to say, then post that. Serious academic offence warning! Your work in this course which is submitted for course credit must be your own. Representing someone else's creative work as your own is an academic offence. There are a number of rules which you must follow to avoid prosecution. Rules regarding acceptable levels of collaboration differ among courses and departments; in this course you must follow the CSC 104 rules. In course work, you are expected to submit something on your own, so submitting anything which comes from others is an academic offence unless specifically and precisely acknowledged. It is also an offence to assist others in committing an academic offence. Therefore, you may not: type assignment code, formulas, or other text into a computer with others produce any part of your assignment submission while meeting with others look at someone else's assignment work, completed or partial, before the deadline show anyone (other than the instructor or a TA) your assignment work, completed or partial, before the deadline (or any extension they have for special circumstances best to wait until after the instructor solutions are posted) bring your solution, completed or partial, to any group discussion about an assignment take away any written or electronic material from any group discussion about an assignment I suggest limiting your collaboration with others to non-assignment material, and asking morespecific assignment questions of me or a TA. Students have been prosecuted and convicted for handing in work written for hire, written by personal tutors, copied from the web, or with just a bit too much text borrowed from a friend. It is not difficult for graders to detect excessive collaboration.