Essentially all contemporary information systems in commercial applications use relational or object-relational database technology. This course provides an introduction to this technology, both as a collection of hands-on skills and as a conceptual subject with mathematical foundations. The course includes an integrated laboratory component and a realistic database development project.
I will be available in my office (OHS 303) 2:30-3:20 Mondays, Tuesdays, Thursdays, and Fridays, as well as by appointment. Or try your luck: just stop by and see whether my door is open. You may send me electronic mail at firstname.lastname@example.org or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt.
All course materials will be available through my World Wide Web page. The URL for this course is http://www.gustavus.edu/+max/courses/S2007/MCS-274/. After this syllabus I will give hardcopy handouts only to those students who want them.
Our primary text is Database: Principles, Programming, Performance, 2nd ed., by Patrick O'Neil and Elizabeth O'Neil. Documentation for the Oracle Database 10g Release 2 will also be available both online and in hardcopy form in the lab.
Some days, shown in the syllabus, we will meet in the OHS 326 computer lab rather than in the usual classroom. Lab projects will also require you to spend additional time out of class.
You are expected to be familiar with the college academic honesty honor code policy and to comply with that policy. If you have any questions about it, please ask.
The syllabus shows due dates for eight homework assignments; each will typically consist of a few problems. You must turn in all the problems in an assignment by that assignment's due date, but may turn in individual problems earlier if you wish. I will mark each problem as "mastered" or "not yet mastered," and return them to you as rapidly as I can. For those not yet mastered, I may write some brief indication of what area needs work, but you should really take these as an invitation to come talk. You may turn in a revised version of each problem (with the previous graded version attached) however many times it takes to reach the "mastered" point, even after the original due date. The only restrictions are these:
You must have submitted an initial attempt by the original due date.
No revision will be accepted for homeworks 1 and 2 after 12:30pm February 27th, for homeworks 3, 4, and 5 after 12:30pm March 26th, or for homeworks 6, 7 and 8 after 12:30pm May 15th. These cutoff dates are intentionally synchronized with the test review days; the point of the homeworks is to prepare you for the tests.
Note that if you turn in each homework problem as soon as you can do it, rather than saving them for the assignment due dates, you will have more opportunity for revision and resubmission before the cutoff dates listed above. Particularly for the last homeworks before each cutoff date (and test), I can't guarantee you'll have time for a revision cycle otherwise.
I may also announce an earlier cutoff date for any individual problem I consider important for us to discuss in class.
The homework portion of your course grade will simply be determined by the fraction of the homework problems you eventually mastered.
There will be two intra-term exams and a final exam. The intra-term exams will be given in class as shown on the syllabus. The final exam will be as scheduled by the registrar. For each test, you may use one 8.5x11 sheet of handwritten notes. (Both sides of the sheet are OK.)
All lab assignments are due at the beginning of class on the day indicated. Late lab assignments will be penalized by one “grade notch” (such as A to A- or A- to B+) for each weekday late or fraction thereof. However, no late assignments will be accepted after graded assignments are handed back or solutions are distributed.
If you are too sick to complete an assignment on time, you will not be penalized. Simply write “late due to illness” at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.
Please point out any arithmetic or clerical error I make in grading, and I will gladly fix it. You may also request reconsideration if I have been especially unjust.
I will provide you with a grade on each test and lab assignment, in addition to the mid-term and final grades, so that you may keep track of your performance. Each of the three tests will count for 16% of the course grade, the homework for 22%, each of the first three lab projects for 6%, and the final lab project for 12%. However, I reserve the right to subjectively adjust your final grade. Please see me if you have any question how you stand. You are responsible for all course material, whether or not you are present when it was covered or distributed.
All assignments should be readily readable, and should not presuppose that I already know what you are trying to say. Use full English sentences where appropriate (namely almost everywhere) and clear diagrams, programs, etc. Remember that your goal is to communicate clearly, and that the appearance of these technical items plays a role in this communication process. Be sure your assignments are always stapled together and that your name is always on them.
If you have a learning, psychological, or physical disability for which a reasonable accommodation can be made, I would be happy to refer you to the college's disability services coordinator, and to cooperate in the accommodation process. It is generally best if this can be done as soon as possible.
In the reading column, section 0 means the material at the beginning of a chapter before the first section. Analogously, subsection 0 is the material at the beginning of a section before the first subsection.
This is my best guess as to the rate at which we will cover material. However, don't be shocked if I have to pass out one or more revised syllabi.
|2/6||2.0-2.4||The relational model|
|2/9||2.8-2.10||More relational algebra|
|2/12||3.0-3.3||Simple selects||HW 1|
|2/15||3.6-3.9||More query features|
|2/16||Lab 1 (relational SQL)|
|2/19||Lab 1 continues|
|2/22||4.0-4.2||Objects and tables||HW 2|
|2/23||Lab 1 concludes|
|2/26||Catch up||Lab 1|
|3/1||Intra-term exam 1|
|3/5||Lab 2 (object-relational SQL)|
|3/6||4.4.0-4.4.1||PL/SQL and methods|
|3/8||6.0-6.2||Entity-Relationship modeling||HW 3|
|3/9||Lab 2 continues|
|3/12||6.3-6.4||More on E-R modeling|
|3/16||Normal forms continued|
|3/19||6.8.3-6.9||More on normal forms||Lab 2|
|3/20||7.0-7.1||Integrity constraints||HW 4|
|3/22||7.2-7.4||Views, security, and metadata|
|3/23||Catch up||HW 5|
|3/27||Intra-term exam 2|
|4/13||Lab 3 (database design)|
|4/16||Lab 3 continues (w/o Max)|
|4/17||8.4-8.5||Clustered and hash indexes|
|4/19||9.0-9.3||Query processing||HW 6|
|4/20||Lab 3 continues|
|4/23||Lab 3 concludes|
|4/24||9.4-9.6||More query processing|
|4/26||9.7||Join algorithms||Lab 3|
|4/27||Lab 4 (final project)|
|4/30||Lab 4 day 2|
|5/4||Lab 4 day 3|
|5/7||Lab 4 day 4|
|5/8||10.4-10.6||Locking and recovery|
|5/10||Lab 4 day 5 (OHS 329)||HW 8|
|5/11||Lab 4 day 6|
|5/14||Catch up||Lab 4|