Grading & Assessment
Grades are specified as in the following table. There are no qualifiers or modifiers (such as plus or minus) added to grades.
| Grade | Percent |
| A | 100% - 90% |
| B | 89% - 80% |
| C | 79% - 70% |
| D | 59% - 60% |
| F | Below 60% |
Table 1
Attendance in class is mandatory and expected. Excessive absences, as defined in the college policy, may result in a student failing the course, at the discretion of the instructor. If a student must miss class, it is the student's responsibility to:
- Notify the instructor BEFORE class
- Turn in any assignments due that period BEFORE class
- Learn any material presented in class BEFORE the next class
- Obtain any assignments given during class.
It is important for everyone to take an active role in class
discussions, questions and answers. Be willing to both
answer and ask questions. Answer with confidence, even if you think
your answer may be incorrect.
The grade for the course is based on the following items. Percentages are approximate, intended to convey emphasis, and may be adjusted by the instructor:
|
Item |
Percentage |
Dates
|
| 3 Exams | 30% | 1- Sept. 24 2- Oct. 24 3- Nov. 28 |
| 1 Final | 10% | Tuesday, Dec. 11, 0800 hrs, TH 215 |
| Projects | 50% | Due one week after assigned |
| Homework, Class Participation |
10% | assigned in
class, homework is demonstrated in class (next class period) |
Table 2
Each of the 3 exams will be given in-class on the dates shown. DO NOT miss the exam dates--make-up exams will not be given.
Projects and homework will be assigned in class. Each person should do, and submit, his or her own work for homework and projects. However, studying and working together in groups of two or three is strongly encouraged. Note: You may turn in any projects up to 1 week late for a 10% penalty (one grade level). After one week, projects will be worth 0 points for grading purposes.When you submit a project, you must submit both a printed copy of your project, and submit a zipped copy of your Eclipse project viaWebCT.
Homework problems will be assigned in class by the instructor, as needed to help solidify concepts. Assigned problems are due the next class period. Written answers will not be collected and graded. Rather, students should be prepared to give solutions in class, if asked by the instructor, and we will discuss the answers in class. Each student is graded on preparedness to give an aswner if asked, and on the correctness of that answer.
Each student will be expected to write a self-evaluation report at the end of the semester. Learning to logically evaluate your own effort and work is an important skill to develop. In this report, you will make a case for your grade in the course, citing evidence of your work across the semester. The report should be single-spaced, and no more than 2 pages. This assignment is part of the Homework & Participation grade.
Schedule
This This page gives a schedule for the course. The schedule may change over the course of the semester.
Projects are assigned on the Tuesday of the week listed, and are due 1 week after being assigned. Projects may be turned in up to 1 week late, after which they will receive no credit.
Students should expect to spend a significant amount of time and effort planning projects and coding. Some projects are more difficult than others, and will require more time and effort than others. All are designed to help you learn a structured approach to software development, good habits and critical concepts and skills.
Coding standards
- Follow the coding standards as given in your text, with the following adjustments:
- You may place member fields, constructors and inner classes in a different order than the above standard indicates, as long as you are consistent, and it is easy to read.
- You may use a switch staement when applicable.
- Your Javadoc generated comments should be reasonably complete.
- Your code should show eveidence of a reasonable decomposition and design.
You will lose points on your programs for not following these standards.
| Week # |
Date |
Topic
|
| 0 | 22 Aug | Course Overview |
| 1 |
27-29 Aug |
Review of 201 Concepts (Ch. 1-11) , Project 1 |
| 2 | 3-5 Sep | Inheritance, Test Drivers (Ch. 10, 13) |
| 3 | 10-12 Sep | Composition, Aggregation and OO Design (Ch. 17), Project 2 |
| 4 | 17-19 Sep | Files and Streams (Ch. 16), Project 3 |
| 5 | 24-26 Sep | Midterm Exam, Exceptions (Ch. 15), Project 4 |
| 6 | 1-3 Oct | Recursion (Ch. 18), Project 5 |
| 7 | 8-10 Oct | Graphics (Ch. 5), Project 6 |
| 8 |
15-17 Oct |
Sorting & Searching (Ch. 19), Project 7 |
| 9 |
22-24 Oct |
Midterm Exam, Sorting & Searching, Project 8 |
| 10 | 29-31 Oct | GUIs & Event Handling (Ch. 12, 14), Project 9 |
| 11 | 5-7 Nov | Linked Lists (Ch. 20), Project 10 |
| 12 | 12-14 Nov | Stacks (and more Swing), and Queues (Ch. 20), Project 11 |
| 13 | 19-21 Nov | Fall Break |
| 14 |
26-28 Nov |
Project 11 due on the 27th. Midterm Exam, Generics (Ch. 22) |
| 15 | 3-4 Dec | Last Two Days of Class |
| 11 Dec | Final Exam, TH215, 8:00 AM |