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.
Our primary text is Database Systems: An Application-Oriented Approach, Introductory Version, 2nd ed., by Michael Kifer, Arthur Bernstein, and Philip M. Lewis. Only Chapters 1-13 of the textbook are assigned in the syllabus. However, you may want to consult Chapters 14 and 15 for project guidance, particularly if you have not taken MCS-270 (object-oriented software development). Chapters 16 and 17 could make interesting reading if you are looking for something a little extra. Documentation for MySQL and Java will also be available both online and in hardcopy form in the lab.
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. One specific requirement of that policy is that you write the following in full and sign it on every examination and graded paper:
On my honor, I pledge that I have not given, received, nor tolerated others' use of unauthorized aid in completing this work.
For the purposes of this policy, I am defining "graded papers" to be lab reports but not homework problems. (I still expect you to comply with the honor code on homework problems, just not to write the explicit pledge on them.) When lab reports are co-authored, each co-author should write and sign the pledge.
I will assign homework problems. You may turn in any individual homework problem whenever you think you have it solved. I will return it to you as quickly as I can, but normally with only an indication of whether it is acceptable or needs more work. (Sometimes I may give a brief indication of what area it needs more work in.) If a problem needs more work, and you aren't sure what sort of work it still needs, you should treat that as an invitation to come talk with me about it. Once you've done the additional work, you may turn the problem in again. In fact, you may turn in each problem in as many times as you like, until it is marked as acceptable. Your grade for the homework portion of the course will be based on the fraction of homework problems that you eventually did acceptably.
Normally homework problems may be turned in at any time up until the start of class on March 1st for Chapter 1 through Section 5.1, April 6th for Section 5.2 through Chapter 8, and May 17th for Chapters 9-13. However, if we would benefit from discussing a homework problem in class, I may issue a "last call" for solutions to that problem, at least a week in advance.
Unless I indicate that a particular problem must be done individually, you may work on any problem in a group of two or three students. One copy of the solution produced by the team should be turned in, with all team members names on it. Write "we all contributed fairly to this solution" and have all team members sign under that statement.
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.)
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.
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.
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/9||3.0-3.3.4||Relational data model|
|2/11||3.3.5-3.3.12||Constraints and views|
|2/15||4.5||From E-R to relational database schemas|
|2/18||Designing schemas, continued|
|2/21||4.6-4.7||Unified Modeling Language|
|2/25||No class (conference)|
|2/28||5.1.2||Derived operators||Lab 1|
|3/4||Intra-term exam 1|
|3/7||5.2.0-5.2.2||Simple SQL queries|
|3/8||No class (trip to West)|
|3/9||5.2.3-5.2.4||Nested queries and quantification|
|3/11||5.2.5-5.2.10||Aggregate and other queries||Lab 2|
|3/18||6.8-6.9,6.11-6.13||More normal forms|
|3/21||7.0-8.2.4||Triggers and embedded SQL|
|3/22||Real world: Ron Colwill and Paul Johansen from Midwest Wireless|
|3/23||8.2.5-8.3,8.5.0-8.5.8||Stored procedures and JDBC|
|4/5||Lab day (in OHS 329)|
|4/8||Intra-term exam 2|
|4/12||Initial project briefings||Lab 3|
|4/19||Second project coordination meetings||Project draft|
|4/26||Project delivery meetings||Project deliverables|
|4/27||9.0-9.4||Physical organization and indexes|
|5/3||10.0-10.4||External sorting and selection|
|5/4||10.5-10.7||Computing joins (12:50-1:20)|
|5/10||11.4-11.5||More on query optimization|
|5/17||13.2-13.3||Atomicity and durability|
|5/18||Review/catch-up/evaluation||Lab 5 and homework revisions|