Introduction to DataBase Management Systems

Bob Matthews

Department of Mathematics and Computer Science

January, 2001

Working Draft


Weekly reading and lecture schedule


Exam reviews

Group Projects



Grading Policies

Programming exercises will be graded on style and documentation as well as correctness. Programs and control scripts must include header documentation as well as adequate internal documentation unless otherwise specified. Late assignments will generally not be accepted, will incur an increasing penalty when accepted, and will certainly not be accepted after the graded exercise is returned to the class unless I have asked you to correct and resubmit the exercise. Late exercises must be submitted in hard-copy form with listings of the assignment source and of test runs. Programs marked for correction and re submission must be turned in within a week of the day that the assignment was returned to the class. If a program or control script meets requirements, works OK, is readable, and at least minimally documented (header documentation and some internal documentation at important points, it earns between 70% and 80% of the points possible. If a program or control script is well structured, meets all tests (tests are driven from the statement of the assignment, and the specific tests I will use on your program will be taken from the problem description in the assignment write-up, but the specific tests will not generally be provided in advance), and is well documented, it will earn between 80% and 95% of the total possible points. To earn 100% of the total possible points, the program or control script must meet all of the above and do something exceptional beyond the statement of the program.

A minimum grade of 50% on exams and 50% on homework assignments is a necessary (but not necessarily sufficient) condition for a passing grade. All assignments turned in must represent individual effort: work done by a committee cannot be accepted except where a group effort is a clearly stated part of the assignment. All students in Computer Science classes at the University of Puget Sound are responsible for the material contained in the document on academic honesty published by the Department of Mathematics and Computer Science and included in the Academic Handbook The final exam will have the weight of two hour exams.

Important notes:

The final exam for this class will be Thursday, May 10, at 4:00 PM. It will be a comprehensive, two hour in-class examination.
Should you find yourself in difficulty at any point in the semester, please make arrangements to meet with me as quickly as possible.

Course Syllabus


I. Introduction

II. Required Topics

Class exercises will include practice with actual database management systems. The University of Puget Sound has a commercial copy of the Oracle relational database management system which is / may be used for the majority of database exercises in the class. In addition, software developed at the University of Puget Sound will be used for exercises in the relational algebra and relational calculus. Postgres may be used for exercises in object-oriented database systems. The term project (if used) will involve a substantial effort in the specification, design and implementation of a information system using Oracle. The information system will include data entry/enquiry forms, possibly embedded SQL code in C and Java programs, and the use of Developer 2000.


Note: Please note that, except for scheduled University events and exam dates, the schedule of topics, readings, and assignments is tentative. Please refer to the current weekly schedule posted above. It may be necessary to change an exam date: if that happens, I will give you at least a week's notice and make alternate arrangements for students unable to take the exam on the rescheduled date. Please inform me of any conflict between the dates entered here and those in the catalog and course schedule. In the event of any conflicts, the catalog and course schedule have the final say. Please note: It is not possible to change the date or time of the final examination. All students in the class must take the exam at the date and time given in the final exam schedule. The course is in roughly four parts:

The tentative schedule of readings and examinations is as follows. Several of the readings overlap, particularly in the reference material to which we will return several times during the semester.

CSci 455 Lecture Schedule

Spring 2001


Exam Schedule:

I will try very hard to adhere to the following exam schedule. If it becomes necessary to change the date of an exam (except, of course, the final exam over which I have no control), I will give the class advance notice, and work to make arrangements for students who can not take the exam on the changed date.

The date and time of the final exam is fixed by the Registrar. Should the date and time I have for this exam conflict with the announced schedule, the Registrar's schedule will apply.

Weekly Schedules:

Unless otherwise specified, readings refer to Date

Spring 2001 Schedule

Important Note: University dates are taken from the Master Calendar and from the schedule of final exams. If there is a disagreement between the dates below and those dates, the master calendar and Spring 2001 schedule documents are the correct dates. Please let me know if you spot any schedule disagreements.

The official schedules are available on the UPS web site,

The following is a start-of-semester draft only, and is subject to change as the semester moves on. I will, however, try very hard to stick to the published exam dates. If it becomes necessary to change an exam date, I will give you at least a week's notice.


Return to my home page