Homepage - CS3200 Database Design

Fall 2009  Professor Futrelle

Started August 28, 2009, version of December 13, 2009

Published as Tiny URL: http://tinyurl.com/cs3200f09

Contents

  1. Homepage - CS3200 Database Design
  2. Fall 2009  Professor Futrelle
      1. Started August 28, 2009, version of December 1, 2009
      2. Published as Tiny URL: http://tinyurl.com/cs3200f09
    1. Course
    2. Professor Futrelle
    3. You are required to use Google Docs for all homework handins
      1. How Google Docs will work in this course
    4. All course tinyurls as of December 1, 2009
    5. Grades and late policy
    6. Textbook
    7. Bird names
    8. Google Docs, Derby, and email rules - If you do not follow the rules, no credit.  We won't read your handins
  3. Major course pages
      1. Assignments page here
      2. Assignment details page here
      3. Apache Derby here
      4. Project here
      5. Exams here



Course

CS 3200 Database Design
Fall semester, 2009
Key number: 11516
4.0 Credits
1:35 pm - 2:40 pm, Monday, Wednesday, Thursday, 110 WVH 
All course web pages are public Google Docs

Professor Futrelle

Office: 450 WVH, 617-373-4239, Lab 460 WVH, 617-373-4607
Office hours: Wednesdays and Thursdays 3 - 4 PM in my office or lab.
Other meeting times can be arranged
Homepage: http://www.ccs.neu.edu/home/futrelle/
Email to me for this course:  futrelle.cs3200f09@gmail.com

You are required to use Google Docs for all homework handins

You will need a  Gmail account. Get one if you don't already have one. You are not required to use Gmail, just Google Docs, though you might find Gmail convenient for mailing your database-related zip files.

How Google Docs will work in this course

When you are ready to hand in your Google Doc, use the Share menu to share it with the TA and me, with edit privileges.  We can then add remarks and a grade to your handin.  Our changes to your Google Doc will appear in your browser (refresh your browser) within seconds. Each student and the TA and I can send notes to the other about any particular Doc by using "Send messages to collaborators" on the Share menu.

All course tinyurls as of December 1, 2009

More important and/or recent links are at the beginning of the list.

http://www.tinyurl.com/cs3200f09   Course homepage

http://tinyurl.com/CS300f09-ScheduleTable The table form for the entire course schedule

http://tinyurl.com/cs3200f09-Project The project page
AKA: http://docs.google.com/View?id=dcnk9tr8_7hpsr4zg4

http://tinyurl.com/cs3200f09DerbyAssigns Has notes and further links

http://tinyurl.com/cs3200f09TwoClients-OneServer This is "Scrub Jay" now due Wednesday, December 2nd,

http://tinyurl.com/cs3200f09ClientServer Earlier version of the TwoClients-OneServer, but useful just the same

http://tinyurl.com/cs3200f09BetterDerbyDemo  Supercedes the EmbeddedExample

http://tinyurl.com/cs3200f09EmbeddedExamp
 
http://tinyurl.com/cs3200f09-PtarmiganErrors
 
http://tinyurl.com/cs3200f09QuizNotes101509

http://tinyurl.com/cs3200f09-CommonOwlMistakes

http://tinyurl.com/cs3200f09-XML-v1

(Common "Osprey" mistakes were sent in email to the class)


Grades and late policy

The points for each assignment, your project, and exams, are on the Assignments page.
The late policy is a one point deduction for each day late (the assignments average 4 points each)
The two lowest grades for exercises will be dropped (textbook exercises and Derby exercises only).

Textbook

The textbook is A First course in Database Systems, 3rd edition.  A copy is on Reserve in Snell Library.  The homepage for the book is http://infolab.stanford.edu/~ullman/fcdb.html
There are various small errors and typos in your book (depending on which printing you have)  http://infolab.stanford.edu/~ullman/fcdb/errata.html

Bird names

Bird names must be used in titling and referring to all assignments.  Birds, also known as class Aves in phylum Chordata in Kingdom Animalia will be matched in size to the size of the assignments.  Such names should be familiar to Linux people, Ubuntu's Jaunty Jackalope, and to Mac people, Snow Leopard.  Birds are appropriate for a database course, considering the prodigious memory for food storage locations possessed by crows, Clark's Nutcracker, and other Corvidae.

Google Docs, Derby, and email rules - If you do not follow the rules, no credit.  We won't read your handins

I have about fifty students, total, in my two classes. Each class will have about a dozen assignments.  That's too much to keep track of reliably without carefully specified organization and protocols.  You must clearly identify Google docs you permit to me, and all files you will be required to send, and all email.

Standard formats that you must use for identifying your work, illustrated for a hypothetical student, Ms. Nostra Ziploc:


Equally important is the following:  On and in every document you produce, text or source code, you must include your name, the course, the date, and any other relevant information such as a title for a Google doc or your name as the author in a java source code javadoc comment.  Creating informative file names as described earlier, is only half the story.  Just imagine that I print out one of your Google docs or Java source files.  The filename doesn't appear in what I printed.  If there is nothing written in the file as to who you are and what it's about, then I'm stuck (and so are you!).  If it's in a pile on my desk, and it has absolutely no identifying information, I won't be able to tell it's yours.  Over the years, I've received many papers from students, in hardcopy in the past, with practically no information at the top as to what the document is and whose it is.  The students must have thought I had extrasensory powers. More likely they didn't think much or at all about how I could ever associate the document with them. (This is not unlike the warning that you should always carry your ID with you. The sister of a HS classmate of our daughter was struck by a bus in NYC recently.  She had no ID of any kind with her.  She was in the hospital in critical condition for 18 hours before they were able to identify her.)

Major course pages

Assignments page here

Includes exercises from the textbook, using the Derby database, exams, and your semester project. Organized on a week-by-week basis, with all due dates specified.  All handins (electronic) are due by 11:59PM on the due date specified.

Assignment details page here

Supplements the main Assignments page.

Apache Derby here

The relational database system we'll use, includes details on the Derby assignments.

Project here

Has information about your semester project and its three handins.

Exams here

Information About the quiz, midterm, and final exams (in preparation)