COMS E6111-Advanced Database Systems
Spring 2014

Lateness and Collaboration Policy

Collaboration Policy

Both students in a project team will receive the same grade for the project. Team partners are expected to fully collaborate with each other on solving the project. However, communication about project details with somebody other than your partner is not permitted, and is considered cheating.

If in doubt about what kinds of consultations are allowed, please check with the instructor immediately. Please see the Computer Science Department's policies and procedures regarding academic honesty (http://www.cs.columbia.edu/education/honesty) for further details.

Project Team Policy

You will do the projects in the class in teams of two students. You do not need to notify us on your team composition. Instead, when you submit each project you should clearly indicate in your submission your team composition. You can have a different team in each project, but you must notify your teammate by email the day the project is announced that/if you intend to change the team composition. Conversely, it is your responsibility to check with your teammate the day each project is announced that he/she is still taking the class and intends to team up with you for the project.

Auditors: Only students registered for course units may turn in work to be graded.

Lateness Policy

Projects submitted after their exact deadline are considered late.  Late projects will not be accepted unless there is a valid medical or family condition with appropriate documentation submitted to the instructor. However, three grace days are provided for your benefit for projects, for emergencies and for those times during the semester where you need a little more time. Weekends and university holidays are not counted.

Grace days apply in whole: if you hand in a project due on Monday at 6:10 p.m. at, say, 7 p.m. that day, this means you have used up one grace day. (There is no such thing as "a fraction of a grace day.") You can use more than one grace day on a project.  It is also OK not to use any of your grace days, but after those three days are used up we will start deducting 25% of your grade for each day that you are late (see below). 

For example, if a project is due on Tuesday at 6 p.m. and neither you nor your partner has used any grace days, then your team can hand in the project any time up to Friday at 6 p.m., using three grace days.  If you do hand it in on Friday, however, your team will not be able to submit any other projects using grace days. As another example, if a project is due on Thursday at 5 p.m., you can submit the project by Friday at 5 p.m. using one grace day, by Monday at 5 p.m. using two grace days, or by Tuesday at 5 p.m. using three grace days. 

Important note on teams: To use a late day for a project, both team partners must have a grace day available each, and they will both be deducted one grace day each. If you change team partners and your new partner does not have any grace days left, then unfortunately you will not be able to use any grace days for the project.

How you use your grace days is up to you; however, we strongly suggest you save these grace days for the end of the semester.

After you have used all your grace days, you can still submit your project but your grade will be reduced drastically with each day that you are late. Specifically, if you don't have any grace days left and you submit your project one day late, we will reduce your project grade by 25%; if you submit your project two days late, we will reduce your project grade by 50%; finally, if you submit your project three days late, we will reduce your project grade by 75%.

Lines of Communication

Questions?

If you don't understand any of the above, either post a comment to the class discussion board or contact a TA or the professor immediately so that ambiguities can be avoided at the last minute.


Luis Gravano
gravano@cs.columbia.edu