COURSE INFORMATION Fall 2005

60-212 Object-Oriented Programming in Java

School of Computer Science, University of Windsor

 

Instructors

Section 1                                              Section 30

Dr. Subir Bandyopadhyay                      Dr. Dan Wu

School of Computer Science                   School of Computer Science

Room: LT 5112                                      Room: LT 8116 

Email: subir@uwindsor.ca                       Email: danwu@uwindsor.ca

Tel: (519) 2533000 Ext  2999                  Tel: (519) 2533000 Ext  3777

 

Course Description

Concepts of classes and objects, Java applications, frames, event handling, control structures, methods, recursion, arrays, string manipulations, object-based programming, object-oriented programming—inheritance, polymorphism, interface and abstract classes, anonymous classes, data structures in Java. Linked lists, stacks, exception handling and introduction to graphical user interface.

 

Pre-requisites

Minimum grade of C- in 60-141.

 

Resource Material

Lecture Notes for 60-212

C. J. Deitel and H. Deitel , “Java : How to program”, 5th or 6th ed. Prentice Hall.

Bruce Eckel, “Thinking in Java”, Electronic book: www.mindview.net/Books/TIJ/

 

Lectures

Section 1   – Tuesdays and Thursdays,   1430 - 1550, Room:  DH361

Section 30 – Thursdays,                           1900 - 2150, Room: TC104

Tutorial[1] (Open to all sections) – Fridays, 1000 - 1120, Room: DH361

 

Office Hours

Section 1:   Thursdays, 1600-1700

Section 30: Thursdays, 1300 - 1400, 1750 - 1850

 

E-mail is one of the best methods to contact the instructor. Only emails originating from a valid University of Windsor student account will be accepted from students wishing to contact the instructors. Students must include their full names and student ID’s in their correspondence.

 

Labs

Students must register in one of the following sections.

Section 53 -- Wednesdays 1600 – 1720,   ER 3119 

Section 54 – Thursdays     1600 – 1720,   ER 3119   

Section 55 -- Wednesdays 1730 – 1850,   WL 305  

Section 58 -- Wednesdays 2030 – 2150,   WL 305 

Note: Lab attendance is mandatory. All students must check the SIS to ensure that they are enrolled in a lab section as well as in a lecture section. Students who registered in lab sections 51, 52, 56 or 57 must register in one of the lab sections shown above.


Examinations

Midterm 1:              Saturday, October     22, 2005, 0900-1200, Location: Toldo Bldg, Room 200

Midterm 2:              Saturday, November 26, 2005, 0900-1200, Location: Toldo Bldg, Room 200

Final Examination:  Friday,     December 16, 2005, 1900-2200, Exam Slot: TBA

 

 

Course Evaluation

 

 4.5%    9 Laboratory

10%      2 Laboratory tests

 5.5%    1 Project

 25%     Midterm #1

 25%     Midterm #2

 30%    Final Exam

 

Grading Scheme

 

The letter grade will be calculated using the following scheme:

³ 93

<100

A+

³ 63

<67

C

³ 86

< 93

A

³ 60

< 63

C-

³ 80

< 86

A-

³ 57

< 60

D+

³ 77

< 80

B+

³ 53

< 57

D

³ 73

< 77

B

³ 50

< 53

D-

³ 70

< 73

B-

³ 35

< 50

F

³ 67

< 70

C +

 

<35

F-

 

Notes to Students

 

General

1.      A website has been set up for this course. The URL will be announced in class. Lab materials and project will be available online as the course progresses.

2.      Students must read the material in the textbook/course notes before coming to class. Most of the lecture time will be devoted to problem solving that illustrates the topic being discussed. Students are expected to actively participate in the discussions and answer questions.

3.      Student Evaluation of Teaching (SET) will be arranged during the last two weeks of the class schedule.

 

Laboratory sessions

4.      Labs and project are expected to be completed on the assigned due date and time. LATE submissions ARE NOT ACCEPTED. Students must allocate enough time to complete the assignments; start early and report difficulties to the instructor.

5.      Each lab carries 0.5 mark. The grade will be awarded based on completing a working program corresponding to the lab assignment given in the previous week. Each student will have to present the lab assignment and SIGN an attendance sheet before he/she leaves the lab.

6.      If a student is caught adopting unfair means such as copying, no marks will be awarded for the lab.

7.      The lab instructor will allow a student to attend only his/her scheduled laboratory session.

8.      If a student misses a lab due to serious reasons (e.g., medical reasons), he/she has to bring in documentation (e.g., a copy of the doctor’s note) when s/he comes to the next lab session. The student must present the laboratory to the instructor of the lab and not the TA or the GA.

9.      Students must keep a copy of each of laboratory and project work in their directory. If a student finds that some of his laboratory works were not graded, he/she must appeal WITHIN 3 days after the lab/project mark is posted. Late appeals will not be considered.

 

Project

10.   There will be 1 project. The weight of the project is 7.5%.

11.   The project must be presented during the week reserved for project presentation. Students will get a grade for the project as soon as the presentation is over.

12.   If it is discovered later that the student resorted to unfair means, such as copying, the student will get 0 for his/her project.

13.   The students will have to answer a number of questions when s/he is presenting his/her project.

14.   Permission to submit a project late will be granted only in exceptional circumstances. This permission will be granted after the student submits a written request supported by adequate documentation (e.g., doctor’s note). Late projects will be graded by a course instructor and not by a TA or a GA.

15.   If a student wishes to appeal his/her project grade, s/he must do so in the same session s/he presented the project. No late appeals will be considered. Such appeals for project grade will be considered by course instructor and not by the TA’s and GA’s.

16.   The marking scheme for project is summarized below :

Category

Grade

Correct execution of program

3

Program Style and documentation

0.5

Viva Voce test

2

Exams

17.   The midterm tests and the final test will be open book tests. Students will be allowed to take two unmarked copies of English textbooks on Java. One of these textbooks may be the printed class notes for the course. No other material will be allowed.

18.   Once a student attends a test, the grade in that test cannot be overlooked for any reason. If a student is ill on the day of the test or has any other difficulty, s/he must contact the course instructors before the test and will be required to submit a written application including a doctor’s note in case of illness.

19.   There will be no make-up test if a student misses a midterm test. A student who misses a midterm test due to unavoidable reasons must submit a request, with adequate documentation (e.g., doctor’s note), to prorate their grade within 48 hours of the scheduled midterm test. The prorating will be done on the basis of other written tests and will not include the assignment grades or the project grade.

20.   If a student misses both the midterm tests, s/he must contact course instructors to determine what should be done.

21.   If a student misses the final examination due to serious and unavoidable reasons, s/he must contact Dr Dan Wu and submit a written request by 12 Noon, Monday December 19, 2005, with adequate documentation (e.g., doctor’s note), to take a supplementary test. Such a student will be allowed to take a supplementary test. When setting the supplementary test, the instructors will take into account the fact that the student had more time to prepare for the test and may involve an oral test to be administered by a course instructor.

22.   Students will not be allowed to get their test booklets back. They will get a chance to look at their tests and may request a copy of their midterm tests by paying the appropriate photocopying charges. Announcements will be made indicating how the students may look at their midterm tests and the final test.

23.   Students should refer to section 2.4.22 in the 2005-2008 undergraduate calendar for the policy on plagiarism. All cases of academic misconduct will be reported to the Director, school of Computer Science and appropriate actions will be taken.

24.   If a student becomes ill either before or during a test, it is his/her responsibility to get a doctor’s note. No consideration will be made without an adequate doctor’s note (see requirements for a doctor’s note given below).

25.   Once a student writes a test and hands it in, his/her grade for the test cannot be prorated, ignored or replaced by his/her grades for other exams.

Requirements about Doctor’s note

26.   If a student misses a lab, a project presentation, or a test (lab test, midterm test or the final examination) due to medical reasons, a doctor’s note must be submitted immediately. The student must submit a Xerox COPY of the doctor’s note and keep the original until at least June 30, 2006. The doctor’s note must indicate specifically that the student was medically unfit for the day of the test, project presentation or lab; otherwise the note will not be allowed.

 

Policies regarding appeals for grade changes

27.   No appeals for project grade will be allowed after the grading session is over. All appeals must be made immediately, as soon as the grading is done.

28.   An appeal for a lab mark will be considered only if the student has signed the attendance sheet during his laboratory slot, submitted the lab assignment and has not copied the lab from someone else. If two students submit similar programs, both will be given 0 for the lab.

29.   After the final examination, only the appeals, that may take the student into the next letter grade, will be examined.

30.   As a result of an appeal, the mark assigned may go up or down or not change.

 

Examples of academic misconduct by students

Some typical examples of improper conduct during a written test which may lead to severe disciplinary measures against students are given below. The list is not exhaustive.

l         Submitting a program very similar to that submitted by another student or a program available somewhere else (e.g., a book or a web site). If two programs are different only in variable names or comments, they would be viewed as being similar.

l         Communicating with any unauthorized person during an examination in any way (e.g., verbally, using a cell phone, passing messages in some form to another student).

l         Bring into an examination any unauthorised material (e.g., a book or a class note which is marked in any way, bringing any unauthorized documents or aids).

l         Attempting to obtain, by any means, a copy of the test before the examination takes place. This includes stealing a test, buying a test before the examination is held, accepting (from anyone) a copy of the test before the examination is held.

l         Starting to write a test before the test is officially scheduled to start.

l         Refusing to stop writing a test when the test is over.

l         Refusing to obey the instructions of the officer in charge of an examination.   

 


Tentative course lecture schedule

*(The instructor reserves the right to change the outline to accommodate student pace and understanding of the subject matter)

 

Week

Lecture Topic

Week 1 (Sept 8 – 9)

Introduction to the course and the Java language.

Week 2 (Sept 12 – 16)

Control statements

Week  3 (Sept 19 – 23 )

Classes, objects, and methods (I)

Week  4 (Sept 26 –  30 )

Classes, objects, and methods (II)

Week  5 (Oct 3 – 7)

Arrays, Strings, StringBuffers

Week  6 (Oct 10 – 14)

Programming techniques (I): Recursion

Week  7 (Oct 17 – 21)

Classes, objects, and methods (III)

Week  8 (Oct 24 – 28)

Inheritance and Polymorphism (I)

Week  9 (Oct 31 –  Nov 4)

Inheritance and Polymorphism (II)

Week 10 (Nov 7 - 11)

GUI components (I)

Week 11 (Nov 14 - 18)

Introduction to graphics

GUI components (II)

Week 12 (Nov 21 -- 25)

Exception Handling

Week 13 (Nov 28 – Dec 2)

Programming techniques (II): Data structures

Week 14  (Dec 5 - 7)

 TBA

 



[1] The tutorials are intended to help students understand the assignments, the labs and to solve problems. Attendance is not mandatory.