This course is the second course in database management. It introduces concepts, approaches, and techniques required for the design and implementation of database management systems.

In this course, we go "under the hood" to learn how a relational database management system is built. Students will learn the issues involved in designing efficient database systems, and the strategies, data-structures, and algorithms used in the implementation of such systems.

The course is designed in three parts: the physical database, the query processor, and database management. Specific contents include the following.

The content of CSE-3421 is assumed.

Course materials will be primarily drawn from the assigned readings in the assigned textbook. Some auxiliary readings may be assigned during the course.

The grading policy is standard. Collaboration and discussion on the assignments is fine. Note however, that unless you work through the exercises yourself, you will not get much benefit from them.

York University's rules for academic honesty and plagiarism are always in effect. ( See below.) Discussion is fine on the assignments and projects. However, collaboration is not. The work must be your own.

There will be two projects, in sum worth 10% of the final grade. Students will be required to design and implement some of the key algorithms and data-structures for a relational database system. Your code will be in Java.

The projects will probably consist as follows. We may use the Minibase system. (See Appendix B in the textbook.) The Minibase system provides a code base for a simple database system. Your code will augment the Minibase code. The good news is that you do not have to do everything from scratch; the bad news is that you will have to understand the Minibase code to use it.

Late projects will not be accepted, unless prior approval has been obtained with good reason.

There will be three assignment sets through the semester. It is important to put effort into the assignments for understanding of the materials, and because similar problems will appear on the exams. Solutions to assignment sets will be made available after the turn-in dates for study purposes.

All written work for the assignments need not be typed; but if you hand-write them, you must write legibly for credit. Late assignment sets will not be accepted, unless prior approval has been obtained with good reason.

The following schedule is tentative, which means we may deviate from it some during the term. We may need to slow down, or speed up, on certain topics, depending on how things go. As well, we might not get to everything on the schedule, though we shall try. It is your responsibility to keep track of due-dates and what we are covering.

A#:	Assignment '#' due.
P#:	Project '#' due.

Assignments and projects are due on the Thursday of the week indicated above. For example, Assignment #2 due in Week #8 — with lectures on Tuesday 5 March and Thursday 7 March — would be due on Thursday 7 March. Specific details for turning in assignments and projects will be set. For your assignment solutions, they should be dropped off in the class's dropbox next to #1003, the main office for CS&E, in the Lassonde (CS&E) building. For your project solutions, they should be submitted online by the submit command on a PRISM machine by 11:59pm.

Exams must be taken when scheduled unless the student has a medical documentation or can demonstrate special circumstances for a need for a rescheduled exam. The student must obtain approval from the instructor.

Class attendance is important as the student will have an opportunity to ask for clarification of course and text material. There will be problem solving sessions during class period so that students gain experience applying the theory in practice. However, attendance itself is not part of the grade or otherwise enforced.

The Department of Computer Science (& Engineering) Academic Honesty Guidelines are in effect for this course, as, indeed, they are for any CS&E course.

Plagiarism is defined as taking the language, ideas, or thoughts of another, and representing them as your own. If you use someone else's ideas, cite them. If you use someone else's words, clearly mark them as a quotation. Note that plagiarism includes using another's computer programs or pieces of a program. All noted instances of plagiarism will be reported.

These policies are not intended to keep students from working with other students. One can learn much working with others, so this is to be encouraged. Should you encounter any situations for which you are uncertain whether the collaboration is permitted or not, please ask.