| Department of Computer Sciences |
|
Check my WWW page for upto date information.
Class meets 10am to 10:50am MWF in Crawford Building, room 220.
The lab instructors are Andy Mehta and Oksana Kohutyuk. Lab sections 1 and 2 meet at 11am to 12:15pm in OEC 127 and 128. Lab sections 3 and 4 meet at 12:30pm to 1:45pm in OEC 127 and 128. The lab WWW page is http://sites.google.com/a/my.fit.edu/cse-1002/.
The Florida Tech List Server has a
WWW-based e-mail list
especially for this class.
Class announcements will be sent to the list.
Please join, read and contribute to it.
Members can receive all e-mail sent to the list;
also anyone can view the lastest postings via RSS:
This is a good place to get help.
Another good place is the CS help desk in the computer lab.
We review basic Java programming, introduce object-oriented programming, generics, and study simple data structures.
Basically, the prerequiste for cse1002 is the ability to read and write Java programs using static methods and fields. Students should aready know most of the Java statements, operators, and primivite types.
The textbook for the class is:
| Sedgwick |
Robert Sedgewick and Kevin Wayne. |  |
There will be three in-class midterms and a final exam. Tests will make up 60% of the total grade. Every week there will be programming assignments and possibily quizes.
For each student the numeric scores for the assignments and exams are recorded. The lab grades can be found elsewhere. If you have any question about your standing in the class, or if some score has been recorded wrong, please contact me or the lab instructor. No scores will be changed more than two weeks after they have been posted.
It goes without saying that students are expected to take the final exam at the scheduled time during finals week. Also, anyone representing someone else's work as their own, will receive an F for the class. Please keep in mind the CS honor code. If you receive ideas, code, or help from any source, be sure to give proper credit and acknowledgment.
I tend to grade using the entire scale and not just the top end. This means that your numeric score may be lower that you are accustomed. This does not necessarily mean you are doing badly. Your grade is determined mostly by how you do compared to the rest of the class, not by the magnitude of your numeric scores. The average numeric score is roughly equivalent to a B- letter grade. Hence, the (approximate) way to tell how you are doing in the class is: above average numeric score means A or B, below average means C or D. The letter grade for the class will be assigned to each student at the end of the semester. Cutoffs based on the weighted sum of these numeric scores will determine the letter grade. Sometimes I have to make some very tough choices; invariably someone in the class must receive the highest B, the highest C, etc in the class. Your best strategy is to not make it close.
Please note, that copies of some work (homework, projects, exams, etc) for undergraduate classes may be kept on file. This is done for two purposes. For review by CSAB, for the purposes of maintaining the accreditation of the CS program, and to detect plagiarism.
| Monday, 17 August 2009 | first lecture |
| Tuesday, 18 August 2009 | first lab |
| Friday, 4 September 2009 | first midterm exam Introduction and sections 1.3, 1.4, & 1.5 |
| Monday, 28 September 2009 | second midterm exam Chapters 1 and 2. |
| Monday, 12 October 2009 | Columbus Day/Fall Break (no classes) |
| Wednesday, 11 November 2009 | Veterans Day (no classes) |