This syllabus is provided for informational purposes regarding the anticipated course content and schedule of this course. It is based upon the most recent information available on the date of its issuance and is as accurate and complete as possible. The instructor reserves the right to make any changes deemed necessary and/or appropriate. The instructor will make his or her best efforts to communicate any changes in the syllabus in a timely manner. Students are responsible for being aware of these changes.
In this course, we study fundamentals of database systems from two perspectives: the user perspective and the system perspective. In the first part of the course, we will cover the design of databases and database applications. This part will introduce several data models (relational, object-oriented, and entity-relationship models), several relational database languages (Relational Algebra, calculi, and SQL), the theory of relational database design, and basic database programming. In the second part of the course, we will study the internals of database management systems. This part will explore design and implementation issues of data storage, indexing, query evaluation and optimization, transaction processing, crash recovery, and concurrency control.
Students are expected to have a grade C or better in CS2413 and CS3233. Students must have a working knowledge on Java, C/C++, Perl, or PHP programming.
Required Textbook: Fundamentals of Database Systems, 5th Ed., by Elmasri & Navathe (ISBN 0-321-36957-2)
Recommended Textbook: Oracle10g Programming: A Primer, by R. Sunderraman (ISBN 0-321-46304-8)
Following books may be available in the JPL.
Database Management Systems, 3rd Ed., by R. Ramakrishnan and Gehrke
Database System Implementation, by H. Garcia-Molina, J. Ullman, & J. Widom
Database System Concepts, 5th Ed., by Silberschatz, Korth, & Sudarshan
Thu., Oct. 29, 2009.
|
25% |
Project |
|
20% |
Midterm Exam I (week 6) |
|
20% |
Midterm Exam II (week 12) |
|
30% |
Final Exam (Wed, Dec 09, 01:30 pm - 04:00 pm) |
|
5% |
Intangibles |
A letter grade is determined from the total numerical grades as follows: A: 90-100%; B: 80-90%; C: 70-80%: D: 60-70%; F: below 60%.
We believe in the highest level of academic integrity. Unless otherwise required, each student is expected to complete his or her assignment individually and independently. Although study together is encouraged, the work handed in for grading by each student is expected to be his or her own. Any form of academic dishonesty will be strictly forbidden and will be punished to the maximum extent.
Class attendance is required to receive credit for participation and will be an important factor in determining the final grade if your grade is at the borderline. Students who are observing a religious holy day or are participating in a University-sanctioned event may be excused, when prior notice is given to the instructor. Students who miss classes are responsible for the topics covered in the missed classes.
Assignments must be handed in by the due time. No late assignment will be accepted unless compelling reasons can be supplied and verified. Late assignments will receive no grade.
All exams will be in-class, close-book and close-note. No makeup exam will be given unless compelling reasons can be supplied and verified, and in case it is given, a makeup exam may be more difficult than the regular exam. Missed exams will receive no grade. No additional activities will be assigned to improve low grades in exams.
A class mailing list will be used to send important announcements to the entire class. This list will contain your CS email address. You are responsible of checking your email frequently. You may want to set up your CS account to automatic forward emails to your regular email address.
The course web page at http://www.cs.utsa.edu/~wzhang/cs3743/home will contain up-to-date information related to this course, including homework, projects, and announcements. You are responsible of checking out this web page frequently (at least once a week).
I prefer to be contacted by email and visited during office hours. Appointments can also be made by email.
University wide policies and services regarding disabilities may be found online at: http://www.utsa.edu/disability/students.htm.
You are also responsible for knowing UTSA's policies regarding academic dishonesty. Plagiarism (see Section 203) will not be accepted. If you are in doubt be sure to make a proper citation to the author.
The Quality Enhancement Plan (QEP) is a course of action designed to enhance student learning and is a required component of the accreditation process conducted by the Southern Association of Colleges and Schools (SACS). The UTSA QEP Quantitative Scholarship: From Literacy to Mastery provides you with the skills needed to evaluate and interpret data, understand risks and benefits, and make informed decisions in your personal and professional lives. The plan focuses on integrating quantitative reasoning and communication skills in existing courses across the undergraduate curriculum.
The SACS team will visit UTSA during March 23-25, 2010 to review the reaccreditation plan. All UTSA students, faculty, and staff are encouraged to learn more about the QEP by visiting the website www.utsa.edu/qep.
Note: (a) Students are not automatically dropped from a class if they stop attending the class. (b) University policy does not permit visitors in a class. (c) University policy does not permit faculty or office staff to report grades by telephone, fax, or email.
Color Keys:
|
Topics |
|
Reading Assignments (from the textbook) |
|
Project Due |
|
Special Events |
|
Week of |
Topics |
Reading |
Activities |
|
1. Aug. 24 |
Introduction |
Ch. 1, 2 |
|
|
2. Aug. 31 |
E/R Model Relational Model |
Ch. 3, 4.1-4.5 Ch. 5 |
Team Formed (Friday) |
|
3 Sept. 7 |
Relational Algebra E/R to Relational Translation |
Ch. 6.1-6.5 Ch. 7 |
Part One Due (Friday) |
|
4. Sept. 14 |
Functional Dependency Normalization |
Ch. 10.1-10.2 Ch. 10.3-10.6 |
|
|
5. Sept. 21 |
Database Design Algorithms Relational Calculi |
Ch. 11.1-11.2 Ch. 6.6-6.7 |
|
|
6. Sept. 28 |
Review and Midterm I |
|
Midterm Exam I (Wednesday) Part Two Due (Friday) |
|
7. Oct. 5 |
SQL (1) SQL (2) |
Ch. 8 Ch. 8 |
|
|
8. Oct. 12 |
SQL (3) PL/SQL (1) |
Book 2: Ch. 2 Book 2: Ch. 4 |
Part Three Due (Friday) |
|
9. Oct. 19 |
PL/SQL (2) Embedded SQL |
Book 2: Ch. 4 Book 2: Ch. 3, 5 |
|
|
10. Oct. 26 |
Internet Database Applications Data Storage |
Ch. 13.1-13.7 |
Part Four Due (Friday) |
|
11. Nov. 2 |
Indexing Query Processing & Optimization |
Ch. 13.8, Ch. 14.1-14.3 Ch. 15 |
|
|
12. Nov. 9 |
Review and Midterm II |
|
Midterm Exam II (Wednesday) |
|
13. Nov. 16 |
Transaction Processing Concurrency Control |
Ch. 17 Ch. 18.1 |
|
|
14. Nov. 23 |
Database Recovery |
Ch. 19.1-19.3 |
Thanksgiving (Thursday) |
|
15. Nov. 30 |
Object Databases Review |
Ch. 20, Ch.22
|
Part Five Due (Friday) |