Fall 06: CS362 - Object-Oriented Analysis and Design
Course Components
This course has the following components:
Homeworks: 20
Class Participation and Quizzes: 15
Exam 1: 20
Project: 25
Exam 2: 20
Extra Credit: variable
All components are essential, you will not receive a passing grade in this course if you haven't completed a component of the course. For example, let us assume John Doe didn't hand in any homeworks, but received a 'B' grade or better in all other components. His final grade will be 'F' without any exceptions. The class participation grade will be determined by your attendance in the class and your contributions to the class discussions. You will only be able to contribute to the class in a significant way, if you have carefully read the assigned readings for the class.
Grade Computation Logic
You will receive an absolute letter grade for this course. There will not be any curving. As a result, everybody in this class may expect to receive an 'A'. The grades will be assigned as follows:
A: 90 and above
A-: 85 - 89
B+: 80 - 84
B: 75 - 79
B-: 70 - 74
C+: 65 - 69
C: 60 - 64
F: 59 and below
Extra Credit Policy
There will be extra credit problems in homeworks and exams.
Late Homework Policy
Late homework is not encouraged in this course. You are expected to submit your deliverables on time. Some homework solutions will be discussed in class after the due date. These homework will not be accepted after the due date and you will receive no grade for them. The penalties for other homework submission are as follows:
Upto 1 day late: 5%
Upto 2 days late: 12.5%
Upto 3 days late: 20%
Upto 4 days late: 30%
Upto 5 days late: 50%
Upto 6 days late: 90%
7 days or more: 100%
Programming Assignments
Test-Case Policy
This policy applies to the programming assignment part of a homework. If we have provided test cases with the assignment, please ensure that your program passes all these test-cases before you turn in your homework. You will receive no grades for the failing program.
Homework Packaging and Naming Convention Policy
If we have provided a naming conventions for your files, classes, fields, methods, etc. and/or instructions on how to package your homework, please carefully follow them. Failure to do so may result in receiving no grades for that part of the homework.
Teamwork Policies
Software design and development is a team activity. Most organizations have teams of varying sizes. In this class, we will practice software development as it is done in the real world. We will simulate attritions, recruitement, and other such real world events that impact software development projects.
Team Formation
At the beginning of the class, 3-4 students teams will be formed. Each team will be assigned a name and a task to be completed in the rest of the semester.
Conflicts
Please try to resolve conflicts within the team by a conversation among team members. If the conflict is still not resolved, please bring it to the attention of the instructor.
Contributions*
The teamwork process is up to the individual teams. However, each student in the team is responsible for understanding the work in the team, thus teams should be very careful to have the whole team check and explain parts of the work if it is split up. You, as a team member, should be sure that you understand all that goes on and that you take on a fair share of the work.
Certifying Contributions*
To help make sure work contributions are rewarded fairly, we have the team rate the work contributions of its team members at the end of each homework. Individual contributions are rated on a scale of 1-5, with 5 being highest, and 1 lowest. These are used to adjust the grades of team members above and below the team's grade. A rating X produces an increment to an individual's grade of (X - 3)*2.5%, which is added to the team's grade recorded for the individual (as long as the sum is between 0 and 100%).
For example, suppose Alice is in a group whose homework got 80%, and her individual rating was 5; then Alice's grade is recorded as 85%. In the same group if Bob has an individual rating of 2, then his grade is recorded as 77.5%.
The team is constrained to make the total individual work ratings average to 3, and all members must agree on the contributions of all other members. The certification of individual contributions is to be done using a standard form, which is available as a MS Word document and as a HTML page and as a text file.
Acknowledgements
*[Some parts of this policy are adopted from ComS 362 as taught by Prof. Gary Leavens in Fall 2004. These parts are identified by a following star.]