This course offers an introduction to database systems as a key concept in information management. The course covers logical and physical database organization, data models, file structures, indexing, hashing, query optimization, and design issues. This course will cover the design and implementation of databases.
Upon successful completion of this class, the student will:
Lectures are devoted to general explanations of the concepts and ideas underlying the topic at stake. All practical work, coding, programming, testing, etc. will be carried at home.
Homework assignments will assist the students in making sure they understand classes expectations and the content of the lecture, as well as to practice their coding and problem-solving skills. The progression of the students will be regularly tested and assessed through quizzes and exams. Active and relevant participation during the lectures is appreciated.
It is our mutual interest for you to succeed: I love to share knowledge and to expand it by helping students, and students want to gain a useful and agreeable experience that will prove valuable in their future endeavors. To this end, here is:
I should be your first point of contact for any question regarding the content of this class, but many other ressources are available:
Students will be evaluated using three different types of evaluation:
Homework assignments will be given during the course of the semester: they are not expected to be handed back, and won’t be graded, but quizzes with questions taken or inspired from those assignments will be given. Those quizzes happen (almost always) every other week, are closed book and timed (± 10 min.).
There will be two in-class exams, held during the regular class periods.
The final exam will take place during the exam period.
Refer to the planned schedule for precise dates.
Your grade will be computed as follows:
|In-class Exams (×2)||40%|
using the following course grade scale:
|2||01/14||01/17: Quiz||The Relational Model|
|3||01/21||01/21: MLK day||Continued|
|6||02/11||02/14: Exam||Review Session|
|8||02/25||02/28: Quiz (and Midterm)||E.R.-to-Relational Models Mapping|
|9||03/04||03/07–08: Spring pause||Guidelines and Normal Form|
|11||03/18||-||Unified Modeling Language Diagram|
|12||03/25||03/28: Exam||Review Session|
|14||04/08||04/07–08: Spring break||Introduction to Data Programming Using Java|
|16||04/22||-||Introduction to NoSQL|
|17||04/29||05/01: end of class||-|
|18||05/06||05/08 (5–7pm): Final||-|
This schedule is subject to change and enhancements, but provide an indication of the pace, assignments, and major deadlines that you will need to plan for the semester.
The University’s Student Code of Conduct, the student’s manual, as well as the academic regulations and all applicable policies are supposed to be known by the students and will be enforced.
Section 5.2, Academic Conduct of the student’s manual defines precisely what kind of collaborations are acceptable. As long as you don’t lie, cheat, plagiarize, assist others or being assisted by others without authorization, we should not need any of that. If you are unsure about whether or not certain kinds of collaboration are permissible, please ask me.
I am committed to the founding principles of Universal Design, and to make my lecture accessible to every one. Concretely, that means that I’m not requiring you to use a particular Operating System, that I always try to give the information repeatedly, and using multiple channels, that I am available over the phone, email, or in my office. If you are registered with Testing and Disability Services, please see me at your earlier convenience to discuss accommodations.
Please be aware of the USG guidance on House Bill 280. Note that you may not carry a handgun if high school students are enrolled in the class, and that it is your responsibility to visit the registrar to determine whenever this is the case or not.