TA
Yong Rao
Office Hours:
3 -5 pm Wednesday
Phone (410)
455 8934, ITE Rm 351
email: yongrao1@csee.umbc.edu
Meeting Time and Place
Monday and Wednesday
5:30 pm - 6:45 pm, ACIV 145
Important Dates
Midterm Exam : October
25, 2004, Class time
Final Exam : Wednesday
December 22, 2004, 6 - 8 pm
Project Demo and Report
Due : TBD
(Certainly
during the time between last day of class and the final exam)
Last Day of Class: Dec
13, 2004
Project Test
Queries Announced on Dec 16 at 2:00 pm
(you need to show the implementation/results for these queries at the
time of the demo)
Project
Demo Schedule
Homework2
--
Due October 11
Datalog
lecture slides (modified 10/18/04)
Midterm
Review Topics
Lecture slides on Indexing
and Hashing
Homework3
-- Due November 15
Lecture slides on Concurrency
Control and Transaction
Management
Homework4
-- Due November 29
Homework5
-- Due December 13
Lecture slides on Query
Processing and Query
Optimization
Final
Review Topics
Homework6
-- no need to submit (use as practice problems from Ch 15 and 16)
Required Text: Database Systems: The Complete Book, Hector Garcia-Molina, Jeffrey D. Ullman, and Jennifer Widom
Course Description: This course is meant to be a second course in Databases consisting of advanced topics on the mathematical foundations of database concepts.
Course Objective: At the end of the course, the student will have developed skills in three areas: i) a deeper understanding of the theory behind various data models and query languages and of issues related to management of databases including query optimization, security, recovery, and concurrency control; ii) a practical knowledge in designing and implementing a fairly complicated relational database using modern software tools; iii) a familiarity with research in the database field.
Grading
Homeworks - 15%
Midterm Exam - 25%
Final Exam - 30%
Project - 30%
List of Topics | Related Papers (citations available at the end of the chapters) |
Chapter 1 (reading assignment)
Chapter 2: The Entity-Relationship Data Model Chapter 3: The Relational Model |
Reference [2] from Chapter 2 and [4] from Chapter 3 |
Chapter 5: Relational Algebra
Chapter 6: SQL Chapter 10: Logical Query Languages |
Reference [4] from Chapter 3 and [3] from Chapter 6 |
Chapter 7: Constraints and Triggers
Chapter 8: System aspects of SQL |
|
Chapter 12: Representing Data Elements (reading assignment)
Chapter 13: Index Structures Chapter 14: Multimedimensional and Bit Map Indexes |
Reference [3] from Chapter 13 |
Chapter 18: Concurrency Control | Reference [11] |
Chapter 19: Transaction Management | |
Chapter 15: Query Execution | Reference [2] |
Chapter 16: The Query Compiler | |
There will be 5 homework assignments. All homework must be done independently. No late homework is accepted.
You will be required to work on a semester-long project requiring substantial work. Project work requires working in a team of 2-3 students. A detailed description of the project will be provided on the second or the third day of class. Teams will also be assigned at the same time. A final project report is due on the date shown above. A demonstration of the project will be scheduled for each team around the same time (1st week of December). You are also required to pass intermediate milestones. No late projects are accepted. You will be provided accounts on the Oracle Server from OIT.
Midterm and final exams are closed book and conducted in class during the times shown above. Final exam is comprehensive (butmore weightage will be given to topics from second half). Makeup exams and incompletes are allowed only under extraordinary circumstances as per University policy.
Academic Honesty
Each individual is responsible for his or her own homework.
Under no circumstances should written or printed materials be shared. With
respect to the project, I would like to see a healthy competition among
teams to generate innovative ideas and come up with the best project at
the end of the semester. Photo IDs may be required for admission
to exams. By enrolling in this course, each student assumes the responsibilities
of an active participant in UMBC's scholarly community in which everyone's
academic work and behavior are held to the highest standards of honesty.
Cheating, fabrication, plagiarism, and helping others to commit these acts
are all forms of academic dishonesty, and they are wrong. Academic misconduct
could result in disciplinary action that may include, BUT IS NOT LIMITED
TO, suspension or dismissal. To read the full Student Academic Conduct
Policy, consult the UMBC Student Handbook.