CS/MIS 43: Database Management Systems Spring, 2003
Walt Will (willwalt@luther.edu, http://www.cs.luther.edu/~willwalt) Olin 318 563-387-1173
Office
Hours:
8:30-11:00 MTThF (except Chapel Time) and 3:30-4:00 TTh.
Good
Alternate Times (Suggest appointments): Before 8:30 MTThF,
After 4:00 MThF.
Poor
Alternate Times: Wednesday mornings,
3:20-3:45 Tuesday.
Worst
Times: 11:00 – 3:20 MTThF, Wednesday afternoons.
Text: Principles of DATABASE SYSTEMS with
Internet and Java Applications by Greg Riccardi: Addison-Wesley, 2001. ISBN
0-201-61247-X
References:
·
An
Introduction to Database Systems,
by C. J. Date. There are several
editions of this classic textbook; the most recent is the 7th. Copies of useful editions will be on reserve
in Preus Library.
·
Any book on
Microsoft's Access 2000 DBMS
Course Web Page:
A good deal of information relating to this course will be stored in, or
linked to, a page with URL http://www.cs.luther.edu/~willwalt/Public/Pub4303/cs43.html
Grading:
|
3 Exams: Tue, Mar 4; Tue, Apr 8; Tue,
May 6 @100 |
300
points |
|
Homework, Programs, Labs total about
|
200 |
|
Final Exam |
100 |
|
Semester Total |
600
points |
Software:
We will use the Windows
platform in this class, along with Microsoft's
Access 2000 as the DBMS and JBuilder3 for the Java programming. Students working on other platforms or with
other software should leave time to translate their projects to those that run
as specified above.
Individual Projects:
Programming projects are assumed to be single-person projects except
where clearly identified as team projects.
It is natural, expected, and a good idea to discuss ideas with one
another, and often a second person can be helpful in debugging one’s code. But the program must be the intellectual
creation of the student whose name it bears.
“This is mine -- I created it myself” is a claim the student can make
truthfully.
Late Work Policy: Only in cases of genuine emergency,
illness, or school-sponsored activities can the exams be rescheduled. Whenever
possible the student is to contact me in anticipation of the event. Late
homework, projects and programs will not be accepted.
Labs: Many weeks one of the class meetings will
be designated as a laboratory. That
will often occur on Fridays, though that will not always be the case. Attendance at labs is required some of the
time – usually early in the semester.
After midterm, some of the lab periods will be "open" so that
groups of students can work together on projects.
Course Outline
Here is a rough
outline of the topics to be studied during the semester, along with the
approximate timing and relevant reading in Riccardi’s text. Of course, we will vary the topics and
timing as the need arises.
We will be
guided by the text, but skip over some sections. I will supplement with some examples and topics from elsewhere.
A more detailed
schedule will be maintained on line; it has a day-by-day schedule and links to
class notes. It can be accessed most
easily from the class Web page.
Wk
|
Dates |
Chapters |
Topics |
|
1 |
Feb 6 - 7 |
1, 2 |
Overview;
History; Intro to E-R Model |
|
2 |
Feb 10 - 14 |
3 |
Entity-Relationship
Model |
|
3 |
Feb 17 - 21 |
4 |
Extended
E-R; Intro to Access |
|
4 |
Feb 24 - 28 |
5 |
Relational
Model |
|
5 |
Mar 3 - 7 |
5 |
Exam 1; Functional Dependencies and Normal
Forms |
|
6 |
Mar 10 - 14 |
6, 7 |
Normalization;
Relational Algebra |
|
7 |
Mar 17 - 21 |
7 |
Relational
Algebra; Relational Calculus
|
|
|
|
|
|
|
8 |
Mar 31 – Apr 4 |
8, 9 |
SQL |
|
9 |
Apr 7 - 11 |
9, 10 |
Exam 2; Programming for DBs;
JDBC; HTML basics
CGI programming; Java Servlets; JDBC transactions
|
|
10 |
Apr 14 – 18 |
11 |
File access;
Connect to databases |
|
11 |
Apr 21 – 25 |
12 |
Indexes; B+
trees; |
|
12 |
Apr 28 – May 2 |
13 |
Query
Processing; Optimization; Transactions |
|
13 |
May 5 – 9 |
14, 15 |
Exam 3 ; |
|
14 |
May 12 - 16 |
16 |
Issues with
Distributed Apps; Review |
.