CSC 381: Database and File Systems, Fall 2008

Assignments

Friday, August 29:

(To be discussed in class) Chapter 1, Exercises 1, 2, and 4
Develop a list of database systems you commonly interact with.

Friday, September 5:

(To be discussed in class) Chapter 2, Exercises 1, 2, 3, 5, 7, and 8

Friday, September 12:

(To be discussed in class) Chapter 3, Exercises 2 and 9

Friday, September 26:

(To be handed in) Chapter 4, Exercises 1, 4, 8, 9, 12, and 20 (a, d, g, j, m, and p)

Monday, October 13:

Choose an application domain which interests you and about which you have some knowledge. Design a database to manage information for some aspect of this domain. Create a class diagram and a corresponding SQL specification (that is, a sequence of create table commands) for your database. As a minimum, there should be at least four tables in your database, with (ideally) no redundant or inadequate relationships (in the terminology of Chapter 3). In addition, give at least four examples of useful queries written against your database. Finally, write up your design decisions, and discuss at least one example of a view that could be used to provide restricted access to your database for some users.

For this project, I am not requiring that you actually create the database (for example, in Derby) or populate it with data. However, you may find it helpful to do so when testing your queries.

Wednesday, November 12:

Following the model of the CollegeDB project on the subversion repository (which is based on the DAO code from Chapter 9 of the text, and which implements the database example from the midterm exam), write Java code to interface with the database you designed in the previous assignment. Your code should have a clean separation between the client (which may be very simple), the in-memory model, and the data access objects used to connect to the back-end database. Choose at least three of your database tables to implement (perhaps in simplified form, in case your design had lots of tables), and make sure the code can handle creating the database from scratch and populating it with some example data.

Monday, November 17:

(To be discussed in class) Chapter 12, Exercises 1, 2, 7, 8, 12, and 13; Chapter 13, Exercises 1 through 8

Monday, November 24:

(To be discussed in class) Chapter 14, Exercises 3, 7, 10, 16, 18, 20, 21, 23, 25, 31, and 40

Wednesday, December 10:

In class we will be extending SimpleDB with a REAL data type. Prepare for this by reviewing the code for each of the levels we have studied, and determining what will need to be added or changed. You may ignore the parser.

DePauw University, Computer Science Department, Fall 2008
Maintained by Brian Howard (bhoward@depauw.edu). Last updated