CSCI 4370/6370 Database Management

Description Schedule Prerequisites Staff Communication Topics Textbooks Grading Projects Policies

Welcome to the course page of CSCI4370/6370. This page provides course information, assignments and information about the staff. In case of any questions, please feel free to contact bhargav@uga.edu with subject "CSCI4370/6370 - Query" and I would get back to you as early as possible. Also, please check this page regularly for any updates on assignments, change in office hours and for other related information.

Course Description

CSCI4370/6370 provides the student with a comprehensive introduction to the design of databases and the use of database management systems for applications. We will cover the relational model and, and SQL - the standard language for creating, querying, and modifying relational and object-relational databases. From a more theoretical perspective we will cover relational algebra, relational design principles based on functional dependencies and normal forms, and the entity-relationship and object-oriented approaches to database design. A variety of other issues important to database designers and users will be covered, including indexes, views, transactions, and integrity constraints. A special emphasis will be given algorithmic issues such as query processing and optimization. Various indexing techniques and their advantages and disadvantages at certain situations will be discussed. At different stages in the course, we will briefly address several advanced topics such as semi-structured databases (e.g. XML), and semantic data management and knowledge discovery. Lectures in all topics is complemented by a significant term project for developing a database application using MySQL, and a set of smaller projects in which students build a prototype database system.

Time & Place

Mondays 11:15 - 12:05 (Chemistry - 306)
Tuesdays and Thursdays 11:00 - 12:15 (Chemistry - 306)

Prerequisites

The Programming projects will use Linux/Windows and MySQL database management system and the Java Programming Language. We will assume the students are already proficient in Linux/Windows and Java.

Course Staff

Instructor: Dr. Budak I. Arpinar
Hardman Hall, Room-225.
Phone: 583-8249
Office Hours: Monday & Tuesday (3:30 to 4:30 PM)
Teaching Assistant 1 : Krishna Bhargava Vangapandu
Boyd 301,
Email: bhargav@uga.edu
Office Hours: Monday (2:30 to 4:30 PM)
Teaching Assistant 2 : Kavitha Anandan
Boyd 205,
Email: kavitha@uga.edu
Office Hours: TBD

Lines of Communication

All inquiries regarding the course can be sent to instructor or TA. The general course e-mail address is ugadbf07@gmail.com. This address is monitored continuously by the course staff. There is also a class mailing list: This list is used for staff to communicate with students. We ask all students to place themselves on this mailing list, and we will not hesitate to use this list to convey important and timely information. Students can post messages on this list. It is also for students to post messages with technical or logistical questions regarding the course that are expected to be of interest to most students, and for staff members to post their replies. STUDENTS ARE REQUIRED TO JOIN THE MAILING LIST.

Topics

Introduction (Ch. 1)
ER Model (Ch. 2)
Object(UML) Model
Normalization Theory (Ch. 3 : 3.4-3.6)
Relational Model (Ch. 3: 3.1 - 3.3)
Relational Algebra (Ch. 5)
SQL (Ch. 6)
SQL Programing (Ch. 8 : 8.5)
SQL Constraints (Ch. 7: 7-1 - 7.2)
Data Storage (Ch. 11)
File Organization (Ch. 12 : 12.1 - 12.2)
Index Structures (Ch. 13)
Transaction Processing (Ch. 17,18,19)

Optional Topics

Query Execution
Query Compiler and Optimizer
Overview of Advanced Database Topics(Semi-Structured Data(XML),Semantic-Web(RDF))(if time-permits)

Textbooks

Textbook 1(required)

Database Systems(The Complete Book), H-Garcia-Molina, J.Ullman, and J.Widom, Prentice Hall, 2002.

Textbook 2(optional, but useful)

Database System Concepts, Fifth Edition, Avi SIlberschatzm Henry F. Korth, and S. Sudarshan, McGraw-Hill

Grading

The components of the final grade will be distributed as follows (subject to adjustments):

30% Exam(s)
30% Final
40% Programs (projects: 4)
Homework [bonus for presenters]

An area to investigate in projects is ‘semantic database', i.e., an ontology based relational database management system.

Projects

Each project group will include 2 members. Each project page contains detailed submission instructions as well as some test data and grading criteria.

Project 1 - No link posted yet.
Project 2 - October 25th Due. Click here.
Project 3 - November 16th 11:59 PM. Click here

Homeworks

Homeworks or exercises will be assigned from the text book and announced in the class. More information would be posted here.

Late Policy

Programming work will be submitted electronically, and must be submitted by midnight on the date that it is due. Programming work submitted after the deadline but less than 24 hours late will be accepted but penalized 10%, programming work submitted more than 24 hours but less than 48 hours late will be penalized 20%, and programming work submitted more than 48 hours but less than 72 hours late will be penalized 30%. No programming work will be accepted more than 72 hours late. THIS LATE POLICY WILL BE STRICTLY ENFORCED.

Regrade Policy

Please send an email message to TA stating that you believe you deserve a project part regrade, and explaining precisely why. Please include your name, and the number of the project part in question.

Programming Work

Eeach team is expected to submit their own original work. On many occasions it is useful to ask others (the instructor, the TA's, or other students) for hints or debugging help, or to talk generally about programming strategies. Such activity is both acceptable and encouraged, but you must indicate any assistance (human or otherwise - except liserv discussions/TA/instructor help) that you received. In any event, you are responsible for coding, understanding, and being able to explain on your own all project work that you submit. We will pursue aggressively all suspected cases of Honor Code violations, and they will be handled through official University channels. If you have any questions about this policy or about the degree to which we will pursue Honor Code violations, please discuss your concerns with the course staff immediately.