CSCI-331: Database Systems
Fall 2007
!!!FINAL GRADES ARE UP ON BANNER!!!
DAYS,
TIME, & LOCATION:
INSTRUCTOR: Dr. Imad Rahal
Office: P. Engel Science Center 211 (SJU)
Email: irahal@csbsju.edu
Phone: 2837
Homepage: www.users.csbsju.edu/~irahal
Office
Hours:
TEXT BOOK (Required): R. Elmasri and S.B. Navathe. Fundamentals of Database Systems (5th Ed.)
RECOMMENDED REFERENCES
DESCRIPTION: This course provides a thorough introduction into the broad area of database systems. We will cover most of the fundamental concepts of database theory in addition to surveying a number of advanced database topics. Topics covered include: Introduction to database systems and file-based systems, database design through ER and EER modeling, the relational model, relational algebra and calculus, data definition and data manipulation languages, SQL, JDBC, functional dependencies and normalization (1NF, 2NF, 3NF and BCNF), record and file organizations, indexing, query processing and optimization, concurrency control, and other topics of interest. In addition to theoretic component which will consume most of the class lectures, the course requires a large-scale project
OBJECTIVES: Upon successful completion of the course, students will be able to understand the fundamental concepts underling contemporary relational database systems. Additionally, students are expected to gain hands-on experience in developing multi-tiered real-life database applications, giving verbal and written reports, and becoming better team players.
REQUIREMENTS:
Assignments: There will be a number of homework assignments all of which are
individual work.
Project: This course requires a major project in which groups of students
(3 members) design, develop, implement and document an application that heavily
utilizes databases mainly through the JDBC technology. Throughout the semester,
students will turn in a number of deliverables showing their progress. Towards
the end of the semester, every group will provide a high-level written manual
documenting their system in detail (this will be the final deliverable). All
groups also have to deliver an in-class oral presentation describing and
demoing their developed systems – ALL TEAM MEMBERS MUST TAKE PART IN ALL THE
PROJECT DELIVERABLES INCLUDING THE ORAL PRESENTATIONS. For your convenience,
you will be given a number of sample topics to choose from (Click here to check the projects). The descriptions for those projects ARE NOT COMPLETE;
this is left for you to pursue as part of your project. BE CREATIVE! You are
also welcome to suggest your own project topic but please seek my approval as
soon as possible. EVERY
TEAM IS REQUIRED TO MEET WITH ME ONCE AFTER EVERY REPORT IS GRADED AND
RETURNED.
Quizzes & Exams: There will be two midterm exams, and a final exam (not comprehensive but will cover some earlier parts) all of which are closed book. Students will be allowed to make up missed exams only in cases of documented emergencies and at the discretion of the instructor. In addition, there might be a number of quizzes scheduled during the term to check that students are studying the material on a regular basis.
Note the dates for all assignments, project deliverables, quizzes, and exams as they are shown in the schedule below. Please make sure that you abide by the set dates as changing them later during the semester might not be possible due to many unforeseen factors. Late assignments and project deliverables will be accepted up to a maximum of one week with a 5% deduction for every late day.
EVALUATION: The final grade for the course will be based on the following percentages:
|
Attendance, participation & quizzes |
08% |
|
Assignments |
21% |
|
Exam 1 |
13% |
|
Exam 2 |
13% |
|
Final Exam |
15% |
|
Project |
30% |
Grading
is mainly based on the performance of each student compared to the class as a
whole. In general, the following guidelines are followed expect in certain
situations where the instructor sees a need for adjustments.
A 90% Highly competent performance
B 80% Fairly competent performance
C 70% Fair comprehension of the material
D 60% Partial comprehension of the material
E > 60% Unsatisfactory performance
A grade of E may be given in situations of frequent unexcused absences, unsuccessful completion of required work in a timely manner, or evident lack of understanding of core material. Grades of AB, BC, and CD may be given at the instructor's discretion for borderline cases
TENTATIVE SCHEDULE FOR CLASS
MEETINGS
|
CYCLE |
DATE |
DAY |
TOPIC |
DUE |
READING |
|
1 |
WED 08/29 |
1 |
Introduction |
|
|
|
1 |
FRI 08/31 |
3 |
Introduction |
Sec. 1.1 - 1.8 |
|
|
1 |
TUE 09/04 |
5 |
ER Modeling |
Set 3 |
Sec. 2.1, 2.2, 2.4 |
|
2 |
THU 09/06 |
1 |
ER Modeling |
Sec. 3.1 - 3.4 |
|
|
2 |
MON 09/10 |
3 |
EER Modeling |
Phase 2: System definition |
Sec. 3.5 - 3.9 |
|
2 |
WED 09/12 |
5 |
EER Modeling |
Sec. 4.1, 4.2, 4.3.1 |
|
|
3 |
FRI 09/14 |
1 |
The Relational Model |
Sec. 5.1, 5.2, 5.3 |
|
|
3 |
TUE 09/18 |
3 |
ER-to-Relational Mapping |
HW 1 (ER/EER Modeling) |
Sec. 7.1 |
|
3 |
THU 09/20 |
5 |
ER-to-Relational Mapping |
Sec. 7.2.1 |
|
|
4 |
MON 09/24 |
1 |
ER-to-Relational Mapping |
|
|
|
4 |
THU 09/27 |
3 |
Relational Algebra |
HW 2 (ER/EER-to-Rel. Map.) |
Sec. 6.1, 6.2, 6.3 |
|
4 |
MON 10/01 |
5 |
Relational Algebra |
Sec. 6.4 |
|
|
5 |
WED 10/03 |
1 |
Relational Algebra |
Set 13 |
Sec. 6.5 |
|
5 |
FRI 10/05 |
3 |
Relational Calculus |
Sec. 6.6, 6.7 |
|
|
5 |
TUE 10/09 |
5 |
SQL |
HW 3 (Rel.
Lang.) |
Sec. 8.1, 8.2, 8.3 |
|
6 |
MON 10/15 |
1 |
SQL |
|
|
|
6 |
WED 10/17 |
3 |
EXAM 1 (Intro to |
|
|
|
6 |
FRI 10/19 |
5 |
SQL |
Sec. 8.4 |
|
|
7 |
TUE 10/23 |
1 |
SQL |
Sec. 8.5 |
|
|
7 |
THU 10/25 |
3 |
MySQL |
|
Sec. 8.6 |
|
7 |
MON 10/29 |
5 |
NO CLASS - ICDM |
|
|
|
8 |
WED 10/31 |
1 |
NO CLASS - ICDM |
|
|
|
8 |
FRI 11/02 |
3 |
SQL |
Phase
5: Physical database design HW 4 (SQL 1) |
Sec. 8.8 |
|
8 |
TUE 11/06 |
5 |
SQL |
ACCESS
GUI-MySQL: http://devsrv.cs.csbsju.edu/phpmyadmin/index.php |
Sec. 8.9 |
|
9 |
THU 11/08 |
1 |
SQL |
|
|
|
9 |
MON 11/12 |
3 |
SQL |
Sec. 9.1, 9.2 |
|
|
9 |
WED 11/14 |
5 |
JDBC |
Phase 6: System / functionality design |
Sec. 9.3 |
|
10 |
FRI 11/16 |
1 |
Lab
(JDBC) |
Sec. 10.1, 10.2 |
|
|
10 |
TUE 11/20 |
3 |
Normalization |
Sec. 10.3. 10.4 |
|
|
10 |
TUE 11/27 |
5 |
Normalization |
Sec. 10.5, 11.1 |
|
|
11 |
THU 11/29 |
1 |
Normalization |
Phase 8: User interface design & Phase 7: Class design |
|
|
11 |
MON 12/03 |
3 |
Query Processing/Optimization |
HW 6 (Norm.)
HW 6 SOLUTION |
Sec. 15.1, 15.6, 15.7 |
|
11 |
WED 12/05 |
5 |
EXAM 2 (SQL & Norm.) |
|
|
|
12 |
FRI 12/07 |
1 |
Invited Speaker |
|
|
|
12 |
TUE 12/11 |
3 |
Query Processing/Optimization |
Sec. 15.8.1, 15.8.2, 15.8.3 |
|
|
12 |
THU 12/13 |
5 |
Project presentations |
Phase 9: System implementation DEMO |
|
|
12 |
THU 12/14 |
6 |
|
Phase 9: System implementation REPORT
(11:59 PM - via email) |
|
STUDENTS NEEDING SPECIAL ACCOMMODATIONS or who have special needs of any type are invited to share this information with the instructor as early as possible.
ACADEMIC HONESTY: Work must be completed in a manner consistent with Saint Benedict’s & Saint John’s codes for academic honesty. All outside work and/or ideas used in any part of this course must be properly attributed. All acts of plagiarism, cheating, or other academic misconduct are considered forms of academic dishonesty and are strictly prohibited. Such instances of academic dishonesty will be reported to the appropriate personnel and officials. Please refer to the most recent version of the Saint Benedict & Saint John’s Academic Catalog for further relevant information and guidelines on this matter.