CIT 381, Fall 2007

Database Systems

[ Homeworks | Labs | Links | News | Slides | Models | Databases | Grades ]

• Time and Place:
  • Tuesday and Thursday 10:00-11:20am in 216 Allen
  • Lab sessions are held in room B26 Klamath.
    • 9:00-9:50am Friday
    • 11:00-11:50am Friday

• Instructor: Chris Wilson, 326 Deschutes, 346-3412, cwilson@cs.uoregon.edu.

• Teaching Assistant: Paea LePendu, 227 Deschutes, 346-1380 paea@cs.uoregon.edu.

• Office hours: Students can drop in anytime, make an appointment, or find us in our offices.
  • Chris: MWF 3-4, and usually UH 2-3:30
  • Paea: I enjoy talking with students. Unless otherwise noted, I will be in my office Thursday, 2-3PM & Wednesday, 10-11AM. I share an office, so please knock if the door is closed.

• Course Objectives: There are two primary goals for this course
  • To learn how to do logical database design for relational databases.
  • To learn how to extract meaningful data from a relational database management system (RDBMS) using SQL, the standard language for extracting information from a RDBMS.

• Evaluation: Course grades will be based on the following criteria

  Homework Assignments	35%
  Test 1 (Nov 1)	17.5%
  Test 2 (Nov 29)	17.5%
  Final Project	30%

• Textbooks: We will try to go without a textbook for now. However, this one doesn't look too bad for the second half of the term.

• Software: There are two main applications we will use in this course. Both will be provided on the lab machines (PCs running Windows)
  • ER Studio from Embarcadero
  • MySQL

• Labs: Lab attendence is required. You are responsible for knowing the material introduced in the lab. See here for lab hours.

• Homeworks: There will be 4 homework assignments. They will not be handed out in class. You will find them on the web here. Please do your own work and follow the class naming conventions.

• Midterms: The two midterms will be a combination of multiple choice, true false, design problems, etc and will cover all material from readings, lectures, and labs.

• Final Project: This will involve designing and implementing a small relational database, populating the database with some data, and building a few web pages using PHP that use SQL to extract data. We exect that you will work in teams of two. Part 1 of this project, an ER diagram, is due on Nov. 8.

• Tentative Syllabus [UNDER CONSTRUCTION]

  Date	Lecture Topic	Reading	Supplemental	Due
  Sep 25	introduction and data modeling		terms
  Sep 27	databases and data modeling	slides1	requirements analysis
  Oct 2	ER Modeling	slides2	U of Texas, erExample.doc
  Oct 4	ER Modeling, Keys	slides3	erExample2.doc
  Oct 9	Modeling with ER Studio	slides4	keyexercise07.doc, erExample3.doc
  Oct 11	Modeling with ER Studio			assignment 1 (due Friday)
  Oct 16	More ER Studio modeling	slides5
  Oct 18	Normalization	Normalization (also this)	wikiNormalization
  Oct 23	Physical Design	physical design
  Oct 25	MySQL Databases, Some SQL	week 4 lab		assignment 2 (due Friday)
  Oct 30	Relational Algebra and SQL, test review	Beginning SQL
  Nov 1	test 1
  Nov 6	SQL Joins	SQL Joins
  Nov 8	SQL Functions and Views	SQL Functions		part 1 final project
  Nov 13	SQL Set Operations, Aggregates	SQL Subqueries		assignment 3
  Nov 15	SQL Group By	SQL Hard Queries and Transaction
  Nov 20	Guest Lecture: Dave Clements and Sierra Taylor		Dave's old lecture	assignment 4
  Nov 22	no class: Thanksgiving
  Nov 27	test review, course evals
  Nov 29	test 2
  Dec 7	final project due			Final project

• Late policy: All assignments are due by 4:30pm of the stated due date, though it is much safer to turn them in at class time. Late assignments are subject to a 10% per day penalty. Late assignments will not be accepted once the graded assignments are returned or once sample solutions are handed out. It is your responsibility to turn in the assignments on time.