W4111 Spring 2016 Syllabus (Section 002)

Goal

    The goal of this class is two-fold.  First, to introduce
    you to core database concepts (e.g., data modeling, logical
    design, SQL) so that you too can build a billion dollar
    application.  Second, to teach enough about database engine
    internals (e.g., physical database design, query optimization,
    transaction processing) so you have a good sense of why
    queries may be running slowly/incorrectly.

See the schedule on the course web site: http://www.cs.columbia.edu/~coms4111/ewu.html

Instructor

Eugene Wu
Office Hours: After class on Weds, Mudd 421
Class is in 614 Schermerhorn

Office hours

TA office hours will be in the TA room

Textbook

(Not Required) Database Management Systems 3rd Edition by Ramakrishnan and Gehrke.

Prerequisites

COMS W3134 or W3137 (equivalent courses taken elsewhere are acceptable as well) and
Fluency in Python or can pick it up during the class
- basic data structures (e.g., linked lists, trees, hashtables)
- big O notation
HTML/javascript will help
Will expect students to use tools such as ssh to work with machines in the cloud
You need to get permission from the instructor if you do not have these prerequisites. This course is intended for both Computer Science majors as well as non-majors.

Programming Resources

See our Java to Python Quick Guide
Additional resources

Assignment Collaboration Policies AKA Cheating

Homework assignments must be done alone.
- No collaboration is allowed. Don't do it
Projects are in teams of 2.
- Both members will recieve the same grade and should collaborate with each other.
- Collaboration outside of the team is not allowed. Don't do it
- CVN students are also required to have a partner. The partner can be someone in the main class or flipped classroom.
Cheating is no fun for anyone
- Rampant cheating devaluages the Columbia degree.
- Any hint of cheating will be reported to student affairs and result in
- If you are struggling to keep up in the course, come see the instructor during office hours.
- Cheating is a slippery slope -- it may be enticing, but goes against the values in this course.
If you have any doubt, see Columbia's description of academic honesty

Homework Submission Policy

Homework is generally due before class (2:40 PM) on the due date, unless indicated otherwise.
Auditors: Only students registered for course units may turn in work to be graded.
For CVN students with local teammates, their teammates can turn in homework for them. If both teammates are remote, let the staff know and we can set up electronic submission for you.

Grading

Grading Policy

Homework: 15% equally weighted
Project 1: 15%
Project 2: 5%
Midterm 1: 25% (closed book, 1 two-sided cheat sheet)
Midterm 2: 40% (closed book, 1 two-sided cheat sheet)
Scribing: up to 5% extra credit

Notes on grading (please read):

The percentages are subject to change as circumstances dictate.
Active participation in piazza and/or OH can positively affect your final grade.
Since exams are the main indicators we have of individual grasp of the material, we reserve the right to adjust final letter grades based on exam performance.
Extra credit is added in a way that only benefits the reciptients and does not harm others in the course. In other words, you are NOT penalized in any way if you do not recieve extra credit.
Work that you submit must be your own (or for two-person projects, the team's). We will run the standard software duplication checkers on submitted assignments.
Don't cheat. It's not worth it.

Late Days

Homeworks

You allowed 3 penalty free late days to use throughout the semester for homework only.
One late day equals one 24 hour period after the due date of the assignment.
Even 1 minute late equals the use of a late day.
Once you have used your late days, there will be a 25% penalty for each day an assignment is late.
You do not need to explictly declare the use of late days; we will assign them to you in a way that is optimal for your grade when different assignments are worth different numbers of points.

Projects

Same deal as homeworks
For projects, you are allowed 3 penalty free late days to be used only for projects.
One late day equals one 24 hour period after the due date of the assignment.
Even 1 minute late equals the use of a late day.
Once you have used your late days, there will be a 25% penalty for each day an assignment is late.
You do not need to explictly declare the use of late days; we will assign them to you in a way that is optimal for your grade when different assignments are worth different numbers of points.
TEAMS: both members of the team are deducted late days for each day the assignment is late.
If either member is out of late days, your grade will be deducted as per above.

Additional late day rules

Late days are nontransferrable between homeworks and projects
To use a late day for a project, both team partners must have a project grace day available each, and they will both be deducted one project grace day each. If you change team partners and your new partner does not have any project grace days left, then unfortunately you will not be able to use any grace days for the project.

Alternative procedures to submit late homework:

(Preferred) Bring to any TA's office hours.
Bring to class.
(Least preferred) Submit to Eugene Wu's office: 421 Mudd in the DSI space: map

When using late days, note that homeworks tend to get harder later in the course.

Communication

(Preferred): Piazza
(Least Preferred): Email course staff. There are too many people in the course for this to be a primary option!
Announcements will be on website and via emails using courseworks

How to ask for help:

Search google and see if it answers your question. Then tell us:
What are you trying to do?
What steps did you think would work and which have you tried?
How did it fail and why do you think it failed (OK to say I don't know why it failed)?
What error did it produce?

tsellam / syllabus