Differences

This shows you the differences between two versions of the page.

--- syllabus [2010/01/04 19:37] – created bil
+++ syllabus [2011/01/10 21:43] (current) – bil
@@ Line 1: / Line 1: @@
-**Instructor & TAs**
+==== Instructor & TAs ====
-Instructor
-    * Bil Tzerpos
+== Instructor ==
-      Office: Computer Science and Engineering Building, Room 3024
+  * Bil Tzerpos
-      Office hours: Mondays and Wednesdays, 11:30 - 12:30
+    * Office: Computer Science and Engineering Building, Room 3024
-      Email: bil@cse.yorku.ca
+    * Office hours: Mondays and Wednesdays, 11:30 - 12:30
+    * Email: bil@cse.yorku.ca
-Teaching Assistants
+== Teaching Assistants ==
-    * Steven Castellucci
+  * Steven Castellucci
-    * Ahmed Sabbir Arif
+  * Ron Tal
+  * Anthony Calce
-TA Office hours
+Students are welcome to come to the instructors' office hours to ask questions about the lecture material or other aspects of the course.
-TBA
-Students are welcome to come to the instructors' and TAs' office hours to ask questions about the lecture material or other aspects of the course.
+==== Textbook ====
-====== Textbook ======
+H. Roumani. [[http://www.cse.yorku.ca/~roumani/jba|Java by Abstraction: A Client-View Approach]]. Third edition. Pearson Addison Wesley, Toronto. 2010.
-H. Roumani. [[http://www.cse.yorku.ca/~roumani/jba|Java by Abstraction: A Client-View Approach]]. Second edition. Pearson Addison Wesley, Toronto. 2008.
 This is available in the York University Book Store in York Lanes.
-If you have the first edition of this textbook, it is reasonable to use it for the course. The difference from the first edition to the second edition is that the errata have been fixed. A list of errata can be found here, and another list can be found here.
+A copy of the textbook is on reserve at the Steacie Science Library. Students can also use the second or first edition. Errata for the second and first edition can be found [[http://www.cse.yorku.ca/~roumani/jba/2/errata.htm|here]] and [[http://www.cse.yorku.ca/~roumani/jba/1/errata.htm|here]], respectively.
-H. Roumani. Java by Abstraction: A Client-View Approach. First edition. Pearson Addison Wesley, Toronto. 2006.
-Note: If you are using the first edition, you should download the software from the second edition. This can be found on the textbook webpage.
+**Note**: If you are using older editions, you should still download the latest software from [[http://www.cse.yorku.ca/java/api/type/|here]].
-Course Components
-Lectures
-The lectures consist of presentation and discussion of the course material. One chapter from the textbook is covered each week. Students are encouraged to read the current week's textbook chapter prior to attending the lecture. See the calendar for details.
-Practise Programming Exercises (eChecks)
-These are ten weekly practise programming exercises that must be completed and submitted electronically. These are called eChecks in the textbook and are submitted online. (Okay, there is an eleventh one that is not part of the marks, Practise #0. But that one is quite simple and is for introductory purposes only.)
+==== Course Components ====
-Students receive instant feedback whether their solution passed all the tests. Each eCheck is graded on a pass-fail basis (so all or nothing), and must be completed within a week. eChecks are assigned in your weekly lab session. See the calendar for details.
+== Lectures ==
-To learn how to submit eChecks electronically, do the initial self-paced labs of the textbook consulting the Guided Tour for CSE1020 students . The URL of the eCheck server (which you need in order to submit electronically from home) can be found in the guided tour.
+The lectures consist of presentation and discussion of the course material. One chapter from the textbook is covered each week starting with the Wednesday lecture. Students are encouraged to read the current week's textbook chapter prior to attending the lecture. Material developed during the lectures can be accessed by clicking on Lectures on the sidebar.
-Students are expected to adhere to the coding style that is given in Appendix C of the textbook.
+== Labs ==
-Lab Tests
-There are two lab tests held throughout the course. These are programming tests are conducted in your normal lab session.
+The Friday lab session will be used for several purposes including getting you started, running lab tests, and providing help on eChecks. To see the exact schedule, click on Labs on the sidebar.
-The lab tests are closed-book, no aids allowed. Blank sheets of paper for scratch work may not be be brought into the lab.
+== eChecks ==
-Midterm Exam
-The midterm exam consists of two components: a written test and a lab-based test (which is like the lab tests above). The midterm is scheduled at a common time for both sections of the course, A and E. (This is tentatively scheduled for Sunday 25 October.)
+These are twelve weekly programming assignments that must be completed and submitted electronically. The eCheck exercises can be found at the end of each chapter in your textbook. For the first 7 weeks, you may choose one eCheck exercise to submit. For the remainder of the course, the eChecks to work on will be specified by the instructor.
-The midterm will cover Chapters 1-5 of the textbook. You are also responsible for material from the Guided Tour.
+Students receive instant feedback whether their solution passed all the tests. Each eCheck is graded on a pass-fail basis (so all or nothing), and must be completed within a week. The deadline for all eChecks is Monday at midnight.
-A copy of the midterm test (written part) from fall 2008 with answers.
+To learn how to submit eChecks electronically, do the initial self-paced labs of the textbook consulting the {{:guidedtour.pdf|Guided Tour}} for CSE 1020 students. The URL of the eCheck server (which you need in order to submit electronically from home) can be found in the guided tour.
-Final Exam
-The final exam also consists of two components: a written exam, and a lab-based test. Scheduling for the final exam will be determined by the registrar's office later in the term.
+Students are expected to adhere to the coding style that is given in Appendix C of the textbook.
-The final exam will cover chapters 1-12 of the textbook. It will consist of a written component and a programming component. The written component will be conducted during the exam period at a time scheduled by the registrar's office (see Examination Schedules). The programming component will be conducted in the lab on the same day (times TBA).
+== Lab Tests ==
-Midterm & Final Written Exam Procedures:
+There are two lab tests in this course. They are both open book, which means that you are allowed to have the textbook with you, but nothing else. For details on these tests, click on Labs on the sidebar.
-    * The written portion is closed-book/no aids.
+== Written tests ==
-    * Exam booklets and/or answer sheets will be provided.
-    * A (non-electronic) dictionary may be used during the exam, if needed.
-    * Proof of Identity must be provided. A photo ID and a student card are required.
-    * Blank sheets of paper for scratch work may not be be brought into the exam.
-The questions of the written exams (midterm and final) will focus on concepts, not on writing code. The programming parts will obviously test you on writing code.
+There is also one written test that will take place during the normal lecture time (also open book). See Important Dates for the date.
-A sample of the final exam written part can be found here (WARNING: these questions are provided only as examples of short answer type questions; your exam may vary).
+== Final Exam ==
-Grading
-You can access your marks so far in the course at the ePost server.
+The final exam consists of two components: a written test, and a lab test. Scheduling for the final exam will be determined by the registrar's office later in the term.
-The weight distribution of the course components is as follows:
-    * 10% : practise programming exercises / eChecks (1% each for practise #1 -- #10)
+The questions of the written part will focus on concepts, not on writing code. The lab test will obviously test you on writing code.
-    * 10% : lab test #1
-    * 15% : lab test #2
-    * 30% : midterm exam
-    * 35% : final exam
-Note also that conversion from numeric to letter grade is applied to the overall mark only and in accordance with the following departmental standard:
+== Grading ==
-F
+The weight distribution of the course components is as follows:
-E
-D
-D+
-C
-C+
-B
-B+
-A
-A+
-<40
-≥40
-≥50
-≥55
-≥60
-≥65
-≥70
+    * 17% : eChecks (1% each for the first 7 weeks, 2% each thereafter)
+    * 15% : Lab test #1 (10% on Week 4 + 5% on Week 5)
+    * 15% : Lab test #2 (Week 7)
+    * 15% : Written test (Monday, March 14)
+    * 38% : Final exam (19% lab test + 19% written test)
-≥75
+== Textbook Labs ==
-≥80
+Every chapter in the textbook contains a "lab". Students are encouraged to follow the steps in these labs, as they are very helpful for understanding the course material. It is especially important to do so in the first weeks of the course. However, the textbook labs are optional and are not marked.
-≥90