This course is an introduction to database management systems (DBMSs), which are the core software systems that applications use to store, manage, query, and manipulate very large-scale data efficiently. The course covers three core topics.
Topics under (1) and (2) are topics from the perspective of DBMS users and administrators and teach students the principles and tools needed for using DBMSs efficiently in practice. These principles and tools will be very important when you build your own data-intensive applications in your careers. In contrast, topics under (3) are from the perspective of system engineers that actually implement the DBMS, and aims to engage students interested in the low-level implementations of the core data structures, algorithms, and protocols DBMSs use to support higher-level applications.
| Week | Lecture Topics & Slides | Readings | Dates | Important Notes | |
|---|---|---|---|---|---|
| 1 | Overview of DBMSs, Course Overview, Administrative Information [l1.pdf] | DSC Ch 1 | Mon, Jan 6 | ||
| Introduction to the Relational Model [l2.pdf] | DSC Ch 2 | Wed, Jan 8 | |||
| 2 | Relational Algebra Part 2 [l3-1.pdf] | DSC Ch 3 | Mon, Jan 13 | ||
| SQL 1 [l4.pdf] | DSC Ch 3-4 | Wed, Jan 15 | A1 out on Fri, Jan 17 | ||
| 3 | SQL 2 [l5.pdf] | DSC Ch 4 | Mon, Jan 20 | ||
| SQL 3 [l6.pdf] | DSC Ch 4 | Wed, Jan 22 | Project Milestone 0 Due | ||
| 4 | SQL 4 [l7.pdf] | DSC Ch 4 | Mon, Jan 27 | ||
| SQL (5) [l8.pdf] | DSC Ch 4, 5 | Wed, Jan 29 |
Crowdmark will be used to submit non-coding assignments. When the CrowdMark instance is ready, all students enrolled in the class will receive an email with a link to their individual submission site. In order to submit, upload a separate PDF file (multiple pages are allowed) to each question. You may resubmit as often as necessary until the due date. (More detailed CrowdMark information is available at https://crowdmark.com/help/completing-and-submitting-an-assignment/.)
Marmoset will be used for the programming questions. More details will be provided in individual assignments.
Assignment release dates and due dates are as follows (dates are tentative and may change):
| Assignment | Date Posted | Due (11:59pm EDT/EST) | Hand In Via | Markers |
|---|---|---|---|---|
| 1 | Fri, Jan 17 | Fri, Jan 31 | Crowdmark Marmoset | |
| 2 | ||||
| 3 |
Instructions for Assignments: Your written solutions will be judged not only for correctness but also for the quality of your presentation and explanations.
Collaboration Policy: The work you hand in must be your own. Unless specified otherwise, you can always use any result from the textbook, notes, or previous assignment just by citing it. You may discuss the assignment questions verbally with others, but you should come away from these discussions with no written or electronic records and you must acknowledge the discussion. Acknowledge any sources you have used. Any assistance received (from human or nonhuman sources) that is not given proper citation may be considered a violation of the university policies.
Late Policy:
The group project is optional. You can choose between doing the group project or having higher weighted exams (refer to the Mark Breakdown section below).
Learn will be used to submit the group project. Detailed instructions will be given in week 2.
| Milestone | Due (11:59pm EDT/EST) |
|---|---|
| 0 (Team up) | Wed, Jan 22 |
| 1 (Proposal) | Fri, Feb 7 |
| 2 (Midterm Report) | Fri, Mar 14 |
| 3 (Final Report & Demo) | Thu, Apr 3 |
| Assessment-type switching cutoff | Sat, Feb 15 |
You have until February 15 to switch between the exam- or project-based grading schemes. After February 15, the teams in the project-based grading cannot switch to the exam-based assessment. Individuals dropping out of the project-based grading must receive consent from the other team members (cc-ed in an email to the IA, ISC, and the instructor); if the team size reduces to below 4 afterwards, the entire team will be switched to the exam-based grading.
We will use Piazza for all course announcements and as a forum for students to ask and answer questions. Note that Piazza is for student-student interactions. So you should enroll yourself at your earliest convenience. During Piazza discussions, please do not reveal the solutions to the assignments by requesting or offering detailed advice. We'll delete comments that reveal too much. Violations can result in academic sanctions.
Similarly, do not solicit hints or provide hints about how to solve the homework problems on other bulletin boards, such as Facebook. Violations can result in academic sanctions.
Piazza is not the place to dispute how assignments are marked. If you have a complaint, please follow the process given below.
| Instructor | Email (@uwaterloo.ca) |
Office Hours |
|---|---|---|
| Semih Salihoğlu | (ssalihog) | Mondays, 4:00-5:00 PM (DC 3351) |
| Instructional Apprentices and Teaching Assistants | Email (@uwaterloo.ca) |
|---|---|
| Guy Coccimiglio (IA) | (gccoccim) |
| Shubhankar Mohapatra (IA) | (shubhankar.mohapatra) |
| Anurag Chakraborty | (a8chakra) |
| David Rui | (drui) |
| Gaurav Sehgal | (g3sehgal) |
| Nimmi Rashinika Weeraddana | (nrweerad) |
| Instructional Support Coordinator | Email (@uwaterloo.ca) |
|---|---|
| Sylvie Davies | (sldavies) |
Two marking schemes, depending on whether you choose to do the group project:
Note: If you decide to e-mail the course staff, you must use your uwaterloo Quest e-mail account (WatIAM/Quest userID @uwaterloo.ca); otherwise we cannot verify who you are and are limited on what we can accept and respond to.
| Help Topic | Contact |
|---|---|
| Assignment: Missed Deadline | We do not accept emailed assignments. The last files submitted before the
deadline will be marked (submit early and often, even if
not finished). If the deadline is missed due to illness or other valid, verifiable reason, see Missed Work Due To Illness below. |
| Assignment: Marking Error | Re-mark request, due within one week of release of marks on CrowdMark/Markoset. Contact the TA who marked the specific question and submit a written request. See TAs for contact information. |
| Assignment: Recording Error | Grades will be made available through Crowdmark and Marmoset. Official marks will finally be on Learn. If you notice an error in the recorded value, please contact Sylvie Davies (CS 348 ISC). |
| Enrollment | If Quest won't let you enroll or switch LEC or TUT sections without a permission/override number: Instructors and course staff are unable to help you—you must see a CS academic advisor. |
| General Course Help | Check office hours. |
| Missed Work due to Illness or Valid & Verifiable Reason (Assignments, Exams) | Validation required. See Verification of Illness Services but substitute Sylvie Davies (CS 348 ISC) for references to instructor. |
| Accessibility Services (AAS) exam accommodation forms (request to write at AAS) | Submit to AAS at least 3 weeks before exam |
Mental Health: If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support.
On-campus Resources
Off-campus Resources
Diversity: It is our intent that students from all diverse backgrounds and perspectives be well served by this course, and that students’ learning needs be addressed both in and out of class. We recognize the immense value of the diversity in identities, perspectives, and contributions that students bring, and the benefit it has on our educational environment. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In particular:
MOSS (Measure of Software Similarities) is used in this course as a means of comparing students' assignments to ensure academic integrity. We will report suspicious activity, and penalties for plagiarism/cheating are severe. Please read the available information about academic integrity very carefully.
Discipline cases involving any automated marking system such as Marmoset include, but are not limited to, printing or returning values in order to match expected test results rather than making an actual reasonable attempt to solve the problem as required in the assignment question specification.