Computing and Information Technology Interactive Digital Educational Library


Syllabus Collection >
Syllabus >

Please use this identifier to cite or link to this item:

Title: Advanced Database Systems
Authors: WPI Computer Science
Issue Date: 
Publisher: WPI Computer Science
Abstract: Advanced Database Systems (CS 561) Course Syllabus - Fall 2000 PROFESSOR Elke A. Rundensteiner, Office at WPI is Fuller-238, HOMEPAGE: EMAIL: COURSE HOMEPAGE: CLASS MEETINGS: Tuesdays and Thursdays at 3:30 pm - 4:50 pm, WPI, Fuller 320. OFFICE HOURS: directly after class on Tuesdays and Thursdays at 4:50 pm -5:30pm, or by appointment. (I may modify times for office hours as the semester progresses, so stay tuned here.) Note that an cs561 email mailing list for this course has been set up. You need to subscribe yourself to this list asap in order to receive messages related to the course (by sending an email message to with message "subscribe cs561"). Goals and Intended Audience This course will provide you with an overview of a selected set of the advanced topics in database systems. The goal is to expose you to the current active areas in databases of interest to both academia and industry by reading papers from the recent literature and discussing them in class. You will also get an in-depth look into one set of technologies by conducting a team project in an area of your choosing (as long as related to databases in some form) and into a second topic by preparing a tutorial to present to the students in one area of your choosing (with guidance from the instructor). This course is for you if you are either interested in learning about the state-of-the-art in database systems. This course could also serve as starting point for you to begin to conduct research in the field of databases. Your course project, if selected carefully, could in some cases be extended to lead to a publication, and hence to a start for a Master's thesis or a first step towards Ph.D. level research work. Recommended Background You should have a basic familiarity with relational databases, the equivalent of a beginning course in databases. Instead if you have used a database system before in practice, you may also have sufficient basic understanding required for the course. If you are in doubt, you get permission from the instructor. Some programming experience in a high-level programming language (such as java or C++ or C) will be necessary for the course in order to pursue a course project. Text Book There will not be an assigned textbook in the course, since there is no good book available covering this diversity of current DBMS topics. Instead, we will be reading selected papers from the literature. I will hand copies of these papers out directly in class, or link them onto our course webpage, or make them available for copying as needed in the department. Optional Readings If you need to brush up on your basic relational database knowledge, then below are some books (some have newer editions) you may want to look over: * Raghu Ramakrishnan, Database Management Systems, McGraw-Hill, 1st Edition, 2nd printing, 1997. * Fundamentals of Database Systems, R. Elmasri, and S. Navathe, Benjamin Cummings, 1994. * Principles of Data and Knowledge Base Systems, Volume 1, J.D. Ullman, Computer Science Press, 1989. * Database System Concepts, 2nd Edition, H.F. Korth and A. Silberschatz, McGraw-Hill, 1991. * A First Course in Database Systems, J. Widom and J. D. Ullman, Prentice-Hall, 1997. SQL manuals * Understanding the New SQL: A Complete Guide J. Melton and A. R. Simon, Morgan-Kaufmann, 1993. * A Guide to the SQL Standard (third edition) C. J. Date and H. Darwen, Addison-Wesley, 1994. Information about Oracle. Notes on Getting started with Oracle, This link contains information to get you started with Oracle as prepared by several folks at Stanford University, including setting up connections to oracle, Web interfaces to Oracle, Java interfacing to Oracle with JDBC, etc. Topics There will be a core collection of readings in selected topics in databases around which our discussions will be centered. These may include: * Database models (relational, object-oriented models, web models). * Object-oriented databases. * Active database systems (i.e., databases and rule management). * View materialization * Data warehousing. * On-line Analytic Processing (OLAP). * Database Mining and Knowledge Discovery. * Information integration and mediation. * New data types: unstructured, textual, etc. * Databases and the WWW. * Web Site Management Systems. * Multimedia database systems. * Advanced database tools, such as schema evolution managers, middle layer engines, etc. * Heterogeneous, distributed databases and client-server systems. * Data management problems and solutions for non-traditional applications, such as E-commerce, engineering, internet, intranet, etc. Grading Policy Final grades computed based on 100 points: * 20 points: Assignments (Brief written critiques of our readings, possibly some homework) * 20 points: Student Presentation (s) and Presentation Overheads. * 35 points: Course Project (Report, Presentation, and Implementation) * 25 points: Final Examination. If you are between two grades, then active participation in the course discussions will be weighed positively, possibly helping you to reach the higher of the two grades. In general, each assignment will have a basic objective for the majority of the assignment points and an extended objective for demonstrating additional work and understanding. Final grades will reflect the extent to which you have demonstrated understanding of the material, and completed the assigned projects. The base level grade will be a ``B'' which indicates that the basic objectives on assignments and exams have been met. A grade of ``A'' will indicate significant achievement beyond the basic objectives and a grade of ``C'' will indicate not all basic objectives were met, but work was satisfactory for credit. No incomplete grades will be assigned unless there exist exceptional, extenuating circumstances. Late Policy You are strongly encouraged to turn in any assignments on-time. Unless otherwise noted for a particular assignment, the following late policy holds. Late assignments will be penalized by subtracting 20% of the total achievable points of that deliverable, if turned in within the first 24 hours after the due date. Between 24 to 48 hours late turnin will result in a reduction of 40% of the total achievable points, and 48 to 60 hours late will result in a reduction of 60% of the total achievable points. Certain deliverables may not have ANY LATE day, as announced. Late point reductions cannot be made up by later improvements. Cheating Unless explicitly noted, all work is to be done on an individual basis. Note in particular that copying of any material, may it be a single sentence or a figure, from any location (including the internet) without proper acknowledgement of the source constitutes plagerism. Any violation of the WPI's guidelines for academic integrity will result in no credit for the course and referral to the Student Affairs Office for disciplinary action.
Appears in Collections:Syllabus

Files in This Item:

File SizeFormat

All items in DSpace are protected by copyright, with all rights reserved.


Valid XHTML 1.0! DSpace Software Copyright © 2002-2006 MIT and Hewlett-Packard - Feedback