Site
Syllabus
Site.Syllabus History
Hide minor edits - Show changes to output
Changed line 23 from:
* Assignments (8 to 10): 40%
to:
* Assignments (5 to 6): 40%
Changed lines 23-25 from:
* Assignments (5 to 6): 30%
* Exam I:20%
* Exam II:20%
* Exam I:
* Exam II:
to:
* Assignments (8 to 10): 40%
* Exam I: 15%
* Exam II: 15%
* Exam I: 15%
* Exam II: 15%
Changed lines 33-35 from:
See the [[Main/Calendar|course calendar]] for the timeline. There might be changes as we progress during the semester.
to:
See the [[Site/Calendar|course calendar]] for the timeline. There might be changes as we progress during the semester.
Changed line 8 from:
We will be using the following book as a text (%red%required%black%): Database Systems: The Complete Book
to:
We will be using the following book as a text (%red%required%%): Database Systems: The Complete Book
Changed lines 3-5 from:
This course presents an overview of the "state of practice" in modern database systems. Three aspects of database management will be examined. First, we will look at the basic structure and capabilities of a database system, and we will examine the process of designing a database and using a database system. Second, we will look inside a database system to see how it is implemented. Finally, we will looks at some latest trends in database systems such as OLAP, XML databases, information retrieval and data mining.
to:
This course presents an overview of modern database systems. Three aspects of database management will be examined. First, we will look at the basic structure and capabilities of a database system, and we will examine the process of designing a database and using a database system. Second, we will look inside a database system to see how it is implemented. Finally, we will looks at some latest trends in database systems such as OLAP, XML databases, information retrieval and data mining.
Added lines 1-53:
!! Introduction
This course presents an overview of the "state of practice" in modern database systems. Three aspects of database management will be examined. First, we will look at the basic structure and capabilities of a database system, and we will examine the process of designing a database and using a database system. Second, we will look inside a database system to see how it is implemented. Finally, we will looks at some latest trends in database systems such as OLAP, XML databases, information retrieval and data mining.
!! Text Book
We will be using the following book as a text (%red%required%black%): Database Systems: The Complete Book
by Hector Garcia-Molina, Jeff Ullman, and Jennifer Widom, [[http://www.prenhall.com/ullman/details2.html| Prentice Hall, Second Edition, 2009 (ISBN:0-13-606701-8)]]. Online resources are aslo available at the book website: [[http://infolab.stanford.edu/~ullman/dscb.html]]
!! Prerequisites
This is a 4000 level course, intended for advanced undergraduates. Students are expected to have a computer science/systems background that includes data structures and algorithms. Students should be comfortable programming in C++/Java and/or other scripting languages like Perl/Python. Students will be expected to learn to use computing tools independently, and will be expected to quickly learn any new tools.
!! Class Format and Requirements
Your grade will comprise of exams, and assignments. There will be two exams during the semester, and a final comprehensive exam. The HWs will test conceptual knowledge and build practical skills in using/implementing a DBMS.
The final grade will be determined as follows:
* Assignments (5 to 6): 30%
* Exam I: 20%
* Exam II: 20%
* Final Exam: 30%
Attendance is highly encouraged. '''You are responsible for the material covered in lecture and any announcements made whether you are there or not.'''
!! Course Calendar
See the [[Main/Calendar|course calendar]] for the timeline. There might be changes as we progress during the semester.
!! Academic Integrity
The following guidelines pertain to the evaluation items listed above.
Assignments -- assignments are intended to reinforce important concepts and are meant to be learning experiences. Collaboration and discussion among students is encouraged during early stages of solving a problem. However, copying someone else's answers is not acceptable. Work with others to explore different techniques for solving a problem, then carry through the solution process by yourself. Students must turn in their own solutions for each homework assignment.
Exams -- exams are intended to gauge your understanding of the course material covered in the preceding classes. No collaboration of any kind is permitted. Exams will be '''open book'''.
Keep the following guidelines in mind: Students are allowed to work together in designing algorithms, in interpreting error messages, in discussing strategies for finding bugs, but NOT in writing code or homework. Students may not share code, they may not copy code, and they may not discuss code in detail (line-by-line or loop-by-loop) while it is being written or afterwards. This extends up to two days after the submission deadline. Students may not "show" their code or homework to other students as a means of "helping them". Students may not leave their code (either the electronic versions or the printed copies) in publicly accessible areas.
Violations of these terms in the submission of assignments will result in penalties. The standard penalty in copying homework/projects is a 0 for the assignment and a letter grade drop. A second offense or cheating in an exam will result in an F for the course and the student will be reported to the dean of students.
!! Other Policies
Late homework assignments and projects will not be accepted (a score of 0 will be assigned), so turn in what you have on the due date (partial credit will be given). Exceptions will be granted only if arranged prior to the due date or a documented illness intervenes.
Make-up exams will not be given. Students who know that they will miss an exam must notify the instructor in advance. The only exception will be for substantiated medical emergencies.
This course presents an overview of the "state of practice" in modern database systems. Three aspects of database management will be examined. First, we will look at the basic structure and capabilities of a database system, and we will examine the process of designing a database and using a database system. Second, we will look inside a database system to see how it is implemented. Finally, we will looks at some latest trends in database systems such as OLAP, XML databases, information retrieval and data mining.
!! Text Book
We will be using the following book as a text (%red%required%black%): Database Systems: The Complete Book
by Hector Garcia-Molina, Jeff Ullman, and Jennifer Widom, [[http://www.prenhall.com/ullman/details2.html| Prentice Hall, Second Edition, 2009 (ISBN:0-13-606701-8)]]. Online resources are aslo available at the book website: [[http://infolab.stanford.edu/~ullman/dscb.html]]
!! Prerequisites
This is a 4000 level course, intended for advanced undergraduates. Students are expected to have a computer science/systems background that includes data structures and algorithms. Students should be comfortable programming in C++/Java and/or other scripting languages like Perl/Python. Students will be expected to learn to use computing tools independently, and will be expected to quickly learn any new tools.
!! Class Format and Requirements
Your grade will comprise of exams, and assignments. There will be two exams during the semester, and a final comprehensive exam. The HWs will test conceptual knowledge and build practical skills in using/implementing a DBMS.
The final grade will be determined as follows:
* Assignments (5 to 6): 30%
* Exam I: 20%
* Exam II: 20%
* Final Exam: 30%
Attendance is highly encouraged. '''You are responsible for the material covered in lecture and any announcements made whether you are there or not.'''
!! Course Calendar
See the [[Main/Calendar|course calendar]] for the timeline. There might be changes as we progress during the semester.
!! Academic Integrity
The following guidelines pertain to the evaluation items listed above.
Assignments -- assignments are intended to reinforce important concepts and are meant to be learning experiences. Collaboration and discussion among students is encouraged during early stages of solving a problem. However, copying someone else's answers is not acceptable. Work with others to explore different techniques for solving a problem, then carry through the solution process by yourself. Students must turn in their own solutions for each homework assignment.
Exams -- exams are intended to gauge your understanding of the course material covered in the preceding classes. No collaboration of any kind is permitted. Exams will be '''open book'''.
Keep the following guidelines in mind: Students are allowed to work together in designing algorithms, in interpreting error messages, in discussing strategies for finding bugs, but NOT in writing code or homework. Students may not share code, they may not copy code, and they may not discuss code in detail (line-by-line or loop-by-loop) while it is being written or afterwards. This extends up to two days after the submission deadline. Students may not "show" their code or homework to other students as a means of "helping them". Students may not leave their code (either the electronic versions or the printed copies) in publicly accessible areas.
Violations of these terms in the submission of assignments will result in penalties. The standard penalty in copying homework/projects is a 0 for the assignment and a letter grade drop. A second offense or cheating in an exam will result in an F for the course and the student will be reported to the dean of students.
!! Other Policies
Late homework assignments and projects will not be accepted (a score of 0 will be assigned), so turn in what you have on the due date (partial credit will be given). Exceptions will be granted only if arranged prior to the due date or a documented illness intervenes.
Make-up exams will not be given. Students who know that they will miss an exam must notify the instructor in advance. The only exception will be for substantiated medical emergencies.