CS 743 (Fall 2014)
Principles of Database Management and Use


General Course Information Course Description Evaluation Schedule Assignments Paper Reviews Academic Integrity

Course Information

Note: There will be no CS743 class on Tuesday Sep 9th. The first class will be on Thursday Sep 11th.
Meeting Time and Place: TTh 11:30-12:50 in DC 2568
Instructor: Ken Salem, DC3512, userid: kmsalem
Office Hours: by appointment

Course Description and Objectives

From the CS graduate course calendar:

An overview of relational databases and how they are used; exposure to relational database technology. Fundamentals of transactions. Database views. Introductions to two or three alternative data models and systems, such as those used for structured text, spatial data, multimedia data, and information retrieval. Introduction to several current topics in database research, such as warehousing, data mining, managing data streams, data cleaning, data integration, and distributed databases.

CS743 is intended to be a first course in database management for graduate students who have not had previous coursework in the area.

For Fall 2014, this is a tentative list of topics (beyond relational databases) to be covered:

This list may be tuned based on class interests.


CS743 course marks will be determined as follows


This is a tentative schedule for the first few weeks of classes. Lecture notes and reading materials will eventually be linked here.
Sep 11: Organizational Meeting
Sep 16: Relational Database Systems, Relational Model
Sep 18: SQL
Sep 23: SQL
Sep 25: ER Model and Database Design
Sep 25: ER Model and Database Design (2)
Oct 02: Normalization
Oct 07: Transactions
Oct 09: Query Processing
Oct 14: Linked Data
Oct 16: Linked Data (2)
Oct 21: Warehousing and Analytics
Oct 23: Streaming Data
Oct 28: Streaming Data (2)
Oct 30: Analytics (2)
Nov 04: no class
Nov 06: Data Quality
Nov 11: Data Quality (2)
Nov 13: NoSQL and Analytics (3)
Nov 18: Graph Databases
Nov 20: Graph Databases (2)
Nov 25: NoSQL (2)
Nov 28: Miscellaneous


Paper Reviews

A number of paper reviews are due, as indicated in the course schedule. Paper reviews are expected to be written in the style of reviews appearing in ACM Computing Reviews. Specifically, the review should briefly summarize the key idea(s) in the paper, and should highlight both positive and negative aspects of the paper and/or the work it describes. Each review should be no more than one page in length, and should be formatted in a single column in 10 point font with single spacing.

Each review should clearly indicate both the paper being reviewed (give a bibliographic citation at the top of the review) and the name, student ID number, and UW e-mail address of the reviewer, as well as the date.

Reviews are due at the beginning of class on the dates indicated in the schedule. Reviews should be submitted in hard copy.

Here are a few example reviews in the style that is expected for CS743:

Academic Integrity

In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. All members of the UW community are expected to hold to the highest standard of academic integrity in their studies, teaching, and research. The Office of Academic Integrity's website (www.uwaterloo.ca/academicintegrity) contains detailed information on UW policy for students and faculty. This site explains why academic integrity is important and how students can avoid academic misconduct. It also identifies resources available on campus for students and faculty to help achieve academic integrity in - and out - of the classroom.

Grievance: A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70 - Student Petitions and Grievances, Section 4, http://www.adm.uwaterloo.ca/infosec/Policies/policy70.htm

Discipline: A student is expected to know what constitutes academic integrity, to avoid committing academic offenses, and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offense, or who needs help in learning how to avoid offenses (e.g., plagiarism, cheating) or about "rules" for group work/collaboration should seek guidance from the course professor, academic advisor, or the Undergraduate Associate Dean. When misconduct has been found to have occurred, disciplinary penalties will be imposed under Policy 71 - Student Discipline. For information on categories of offenses and types of penalties, students should refer to Policy 71 - Student Discipline, http://www.adm.uwaterloo.ca/infosec/Policies/policy71.htm

Avoiding Academic Offenses: Most students are unaware of the line between acceptable and unacceptable academic behaviour, especially when discussing assignments with classmates and using the work of other students. For information on commonly misunderstood academic offenses and how to avoid them, students should refer to the Faculty of Mathematics Cheating and Student Academic Discipline Policy, http://www.math.uwaterloo.ca/navigation/Current/cheating_policy.shtml

Appeals: A student may appeal the finding and/or penalty in a decision made under Policy 70 - Student Petitions and Grievances (other than regarding a petition) or Policy 71 - Student Discipline if a ground for an appeal can be established. Read Policy 72 - Student Appeals, http://www.adm.uwaterloo.ca/infosec/Policies/policy72.htm