As the first introductory course for databases, this course studies the fundamentals of using and implementing relational database management systems. First, from the user perspective (i.e., how to use a database system), the course will discuss conceptual data modeling, the relational and other data models, database schema design, relational algebra and calculus, and the SQL query language. Further, from the system perspective (i.e., how to design and implement a database system), the course will study data representation, indexing, query optimization and processing, and transaction processing. Finally, we will look at large scale “big-data” processing systems.
Background: Data Structures CSE30331 taken previously or concurrently
Programming: For projects, you will do some significant application programming, with both SQL and some host languages of your choice (e.g., C, C++, Java, PHP). We will not cover programming-specific issues in this course.
M/W/F 9:25am – 10:15am
Dr. Tim Weninger (email@example.com)
Wed 10:00am in 353 Fitzpatrick Hall
or by appointment
Justus Hibshman (firstname.lastname@example.org)
Zhihan Zhang (email@example.com) Office Hours: Fridays 4-5pm
Gang Liu (firstname.lastname@example.org)
Office Hours: Wednesdays 5-6pm
TA Office Hours will be held Online on Campuswire and in 150 Fitzpatrick Hall
Questions about the course material, homework, project, or any other course-related questions should be asked on Campuswire. Private questions can be directed to the instructor and/or TAs, but we may ask you to ask it on the forum.
|1||ER Model Basics|
|1||Special Relationships in ER Diagrams|
|2||Project Overview||HW1 Out|
|2||Relational Model Translation|
|3||The Normal Forms||HW1 Due [Solutions] , Stage 0 Due|
|3||Boyce and Codd’s Normal Form|
|4||Web Programming||HW2 Out|
|4||Relational Algebra||Stage 1 Due|
|5||Relational Algebra Expressions|
|6||SQL Subqueries||HW 2 Due [Solutions] HW 3 Out|
|6||SQL Aggregation||Stage 2 Due|
|6||SQL Aggregation Operators|
|7||SQL Insertion, Update, and Delete|
|7||SQL Views, Joins, and Foreign Keys|
|7||SQL Constraints, Triggers, and ORM|
|8||No regular class – project work day|
|8||Exam Review||HW3 Due|
|10||Spinning Disks||HW4 Out|
|10||Indexing B+ Tree||Stage 3 Due|
|11||Indexing in SQL|
|11||Query Execution / Optimizaion||HW4 Due|
|11||Transaction Management||HW5 Out|
|12||Transaction Logging / Locking|
|13||NoSQL and CAP|
|15||Exam Review||HW6 Due|
Assignments will typically be due at the end of a particular class period (unless otherwise specified). All assignments shall be uploaded to Gradescope with questions annotated in the system. Unannotated submissions will not receive a grade.
This table indicates minimum guaranteed grades. Under certain limited circumstances (e.g., an unreasonably hard exam), we may select more generous ranges or scale the scores to adjust.
90-100 A-, A
80-89 B-, B, B+
70-79 C-, C, C+
There will be a semester-long course project, which involves significant database application programming. The project will be structured with several milestones due during the semester, leading to a demo and write-up near the end of the semester.
Textbooks are not required. However, much of the class material and even some of the homeworks will draw from these and other resources.
Database Systems: The Complete Book, 2nd ed., by Hector Garcia-Molina, Jeffrey D. Ullman, and Jennifer D. Widom.
Data-Intensive Text Processing with MapReduce, by Jimmy Lin and Chris Dyer. 2010.
Students should attend all classes. Effective lectures rely on students’ participation to raise questions and contribute in discussions. We will strive to maintain interactive class discussions if possible.
Lecture capture is enabled for this class. This system allows us to record and distribute lectures and other audio and video recordings to you in a secure environment. Because we will be recording in the classroom, your questions or comments may be recorded
All requests to change grading of any course work must be submitted to Gradescope within one week of when the grades are made available. Requests must be specific and explain why you feel your work deserves additional credit. Do not ask for a regrade until you have studied and understood our sample solution.
All scheduled due dates/times are US Eastern Time. Homework is typically due at the beginning of class on the due date, but check each the assignment for specifics.
Due date/time will be strictly enforced. Missing or late and/or unannotated work gets zero credit. If you are unable to complete an assignment due to illness or family emergency, we will understand but please see the instructor as soon as possible to make special arrangements. All such exceptional cases must be fully documented.
Notre Dame Students are expected to abide by Academic Code of Honor Pledge:
As a member of the Notre Dame community, I acknowledge that it is my responsibility to learn and abide by principles of intellectual honesty and academic integrity, and therefore I will not participate in or tolerate academic dishonesty.
All course work that you submit must be efforts of your own (if it is an individual assignment) or of your approved team (if it is a group assignment). Discussion of homework problems is encouraged, but writing solutions together or looking at other students’ solutions is not allowed. Much of the material in this class can be found online. You may look to online sources for guidance, but you must always cite your source(s).