Chris Pollett > Old Classes >
CS157b

( Print View )

Grades: [Sec1]  [Sec2]

Submit: [Sec1]  [Sec2]

Course Info:
  [Texts & Links]
  [Topics]
  [Grading]
  [HW Info]
  [Exam Info]
  [Regrades]
  [Honesty]
  [Announcements]

HW Assignments:
  [Hw1]  [Hw2]  [Hw3]
  [Hw4]  [Hw5]

Practice Exams:
  [Mid1]  [Mid2]  [Final]

                            












CS157b Fall 2002 Sec1 Home Page/Syllabus

Database Management Systems II

Instructor: Chris Pollett
Office: MH 214
Phone Number: (408) 924 5145
Email: cpollett@yahoo.com
Office Hours:MW 2:30-4:00pm F 2:30-4:30pm
Class Meets:
Sec1 MWF 12:30pm-1:20pm in MH223 [an error occurred while processing this directive] MWF 1:30pm-2:20pm in MH223

Prerequisites

To take this class you must have taken: CS157A with a grade of C- or better.

To verify that you meet the prerequisite the coding part of the first assignment will serve as a prerequisite quiz. If you haven't added yet, you must complete the prerequisite quiz before you can add.

Texts and Links

Required Texts: Fundamentals of Database Systems. 3rd Ed. by El Masri and Navathe.
Online References & Other Links: Sun's Java site.
The Java 2 Platform Class Library.
Dr. Sathaye's Oracle Handbook.

Topics

This class begins with a review of the database design process as well as a discussion of OO database design. Database architecture and the system catalog are then discussed. Algorithms for processing and optimizing queries are also given. The class will then cover transaction processing. Notions such as serializability of transaction schedules will be introduced and techniques to ensure serializability using locking protocols will be given. Recovery techniques in case of database failures such as logging techniques and rollbacks, will then be presented. Lastly, some aspects of database security will be covered.

Below is a tentative time table for when we'll do things this quarter:

Week 1: Aug 26 , Aug 28 , Aug 30 Read 11.1-11.3
Week 2: Sep 2(Holiday) , Sep 4 , Sep 6 Read 11.1.-11.3
Week 3: Sep 9 , Sep 11 (HW1 due) , Sep 13 Read 11.4-11.7
Week 4: Sep 16 , Sep 18 , Sep 20 Read 16.1-16.3
Week 5: Sep 23 , Sep 25 (Midterm 1) , Sep 27 Finish Ch16
Week 6: Sep 30 , Oct 2 (HW2 due) , Oct 4 Read Ch17
Week 7: Oct 7 , Oct 9 , Oct 11 Read 18.1-18.3
Week 8: Oct 14 , Oct 16 , Oct 18 Read 18.3-18.7
Week 9: Oct 21 , Oct 23 , Oct 25 Read 19.1-19.4
Week 10: Oct 28 (HW3 due) , Oct 30 , Nov 1 Read 19.5-19.7
Week 11: Nov 4 , Nov 6 (Midterm 2) , Nov 8 Review, Read 20.1, 20.3
Week 12: Nov 11 , Nov 13 , Nov 15 Read 2-.4-20.7
Week 13: Nov 18 (HW4 due) , Nov 20 , Nov 22 Read 21.1-21.4
Week 14: Nov 25 , Nov 27 , Nov 29 Read 21.5-21.8
Week 15: Dec 2 , Dec 4 , Dec 6 (HW5 due) Read Ch22
Week 16: Dec 9 Review
The final will be Dec 13 12:15pm-2:30pm (Sec 1) and Dec 17 12:15pm-2:30pm (Sec 2)

Grading

Homeworks 40%
Midterm 1 15%
Midterm 2 15%
Final 30%
Total100%

When I assign grades the high score has an opportunity to receive an A+. I do curve grades and my curving will be in line with previous times this class has been taught. If you do better than an A- in this class and want me to write you a letter of recommendation, I will generally be willing.

Homework Info

Links to the current list of assignments can be found on the left hand frame of the class homepage. After an assignment has been returned a link to its solution will be placed off the assignment page. Each homework will consist of a reading, a writing and a programming part. Material from the reading part of an assignment may appear on midterms and finals. Homeworks for this class will be submitted and returned completely electronically. The written and programming parts of an assignment are submitted by clicking on the submit homework link for your section on the left hand frame of the homepage and filling out the on-line form. I will not accept hardcopies or e-mail versions of your assignments. The written parts of an assignment will be submitted as text documents. Homeworks will always be due by the start of class on the day their due. Late homeworks will not be accepted; however, your low homework score will be dropped.

When doing the programming part of an assignment please make sure to adhere to the specification given as closely as possible. Names of files should be as given, etc. Failure to follow the spec may result in either I or the grader refusing to grade your homework and you receiving a zero for your work. In addition, you should make sure your code conforms with the Departmental Java Coding Guidelines This will be worth one point on every assignment.

Exams

The midterms will be during class time on: Sep 25 and Nov 6 .

The final will be: Dec 13 12:15pm-2:30pm (Sec 1) and Dec 17 12:15pm-2:30pm (Sec 2).

All exams are closed book, closed notes and in this classroom. You will be allowed only the test and your pen or pencil on your desk during these exams. Beeper or cell-phone interruptions will result in immediate excusal from the test. The final will cover material from the whole quarter although there will be an emphasis on material after the last midterm. No make ups will be given. The final exam may be scaled to replace a midterm grade if it was missed under provably legitimate circumstances. These exams will test whether or not you have mastered the material both presented in class or assigned as homework during the quarter. My exams usually consist of a series of essay style questions. I try to avoid making tricky problems. The week before each exam I will give out a list of problems representative of the level of difficulty of problems the student will be expected to answer on the exam. Any disputes concerning grades on exams should be directed to me, Professor Pollett.

Regrades

If you believe an error was made in the grading of your program or exam, you may request in person a regrade from me, Professor Pollett, during my office hours. I do not accept e-mail requests for regrades. A request for a regrade must be made no more than a week after the homework is returned.

Academic Honesty

You are both allowed and encouraged to discuss general algorithms and approaches to programming problems with your classmates. But these discussions must remain at a high level and not involve actual code being exchanged. In particular, the code you submit as a solution to an assignment must be your own. Plagiarism on homework or cheating on tests will result in appropriate academic disciplinary action being taken. Information on the university policy governing academic dishonesty can be found at http://info.sjsu.edu/web-dbgen/catnarr/policies/n30.html.