CS 5530/6530 Spring Semester, 2010
WEB 2230 TH 3:40-5:00
Instructor: Thomas C. Henderson
Examine the representation of information about real world enterprises using important data models including the entity-relationship, relational and object oriented approaches. Learn about database design criteria, including normalization and integrity constraints. Cover selected topics such as distributed, temporal, active, and multi-media databases.
(In this course we will not cover the details of how to use any specific commercial database system.)
· Thomas C. Henderson, Professor
· E-Mail: tch@cs.utah.edu
· Phone: 801-581-3601
· Fax: 801-581-5843
· Instructor Office Hours: By appointment 2871 WEB (arrange by email).
· TA: Seth Juarez
· TA Office Hours (3431 MEB): 2-3:40 TH.
· TA: Wei-Fan Chiang
· TA Office Hours (3167 MEB): 2-3:40 MW.
·
Required Book for Class: A First Course in Database Systems, Ullman and Widom
The prerequisite is successful completion of CS 3500.
In this class you will learn the practical benefits that stem from using a Database Management System (DBMS). To better understand a DBMS’s behavior, you will explore the theory behind the implementation of relational database management systems. In particular, the course will cover conceptual data modeling, relational and semi-structured data models, database schema design, relational algebra, SQL, and the xPath and XQuery query languages. This course is designed to cover the fundamental database concepts and query languages that are used in current relational database engines.
CS 5530 vs. CS 6530
This course offering serves both graduate and undergraduate students:
· CS 5530: All undergraduates should register under this number. It is also recommended for graduate students from other (non-SoC) departments.
· CS 6530: All SoC computer science graduate students must register under this number. Grades are based on different assignments for the two classes.
Textbook
The required course textbook is First Course in Database Systems with a GOAL access card by J.D. Ullman and J. Widom, 3rd edition.
You will need GOAL access for your homework assignments. The University Bookstore sells both the textbook and the GOAL access card. See GOAL
We strongly encourage students to attend class because effective lectures rely on student participation to raise questions and contribute to the discussion.
Read the textbook before lectures, and study it more carefully after class. Please note that all required readings may serve as the basis for exam questions, even if not explicitly covered in class. Lectures motivate and serve as a roadmap to your reading.
Students taking CS6530 are required to perform an individual research
project.
Students will follow the instructions given in the programming assignments for using database software. For homework, see GOAL
|
Date |
Particularly Appropriate Reading |
Assignments |
Assignments Due |
|
|
|
|
|
|
Weeks 1-5 Jan 1 – Feb 12 |
Chapters 1-4, 5.1 |
Homeworks (see GOAL) Exam 1: 11 Feb |
Programming Assignment 1 |
|
Weeks 6-10 Feb 15 – Mar 19 |
Chapters 6-9 |
Homeworks (see GOAL) Exam 2: 18 Mar |
Programming Assignment 2 |
|
Weeks 12-16 Mar 29 – Apr 29 |
Chapters 11-12 |
Homeworks (see GOAL) Final Exam (May 5, 3:30-5:30) |
Programming Assignment 3 |
|
|
|
|
|
Homework (ugs) |
10% |
|
Programming Assign. (ugs) |
15% |
|
Exams (ugs & grads) |
75% |
|
Project (grads) |
25% |
Student Integrity
Cheating of any kind will not be tolerated. Any assignment or exam that is handed in must
be your own work. However, talking with
others to better understand the material is strongly encouraged. Recognizing the distinction between cheating
and cooperation is important.
·
If you copy somebody else’s solution,
you are cheating. If you let somebody
else copy your solution, you are cheating.
Both parties will fail the assignment and receive a failing grade in the
course.
·
If somebody dictates a solution to you,
or if you find solutions on-line or elsewhere, you are cheating. Everything you hand in must be your own work
in your own words, based on your understanding of the problem and solution.
·
If somebody helps you understand the
problem during a high-level discussion, you are not cheating. We strongly encourage students to help one
another understand the material presented in the class and in the book and
general issues relevant to the assignments.
·
When taking an exam, you must work independently. Any collaboration during an exam will be
considered cheating.
·
Any student who is caught cheating will be given an E in the course
and referred to the University Student Behavior Committee. Please do not cheat – if you’re having
trouble understanding the material, please let us know and we will be happy to
help.