Database Management Systems
CS 370 - IT 376

FALL 2012 SYLLABUS

Fall 2004 Syllabus | Fall 2005 | Fall 2007 | Fall 2008 | Fall 2009| Fall 2010 | Fall 2011

This page last changed 27-nov-12

Objectives:

The student should develop skills and understanding in:

• the design methodology for databases and verifying their structural correctness
• implementing databases and applications software primarily in the relational model
• using querying languages, primarily SQL, and other database supporting software
• applying the theory behind various database models and query languages
• implementing security and integrity policies relating to databases
• working in group settings to design and implement database projects

This course's prerequisite is IT 210 or CS 240 or some experience in programming.  You should bring understand and/or skills in, or willingness to learn, the following areas:

• understand basic data structures and their uses (lists, arrays, hash tables, trees and b-trees)
• understand the concepts of object-oriented programming (classes, inheritance)
• modular software design and method/procedure/subroutine linkage
• understand the design, implementation and testing of medium-sized problem solutions
• some contexts in which databases are used
• basic familiarity with a Unix environment

Unix basics (from CS 240): Sun Unix basics | Unix I | Unix II | Unix III |  vi

Grading:

• 15% Exam 1, Friday, September 28, 2012
• 15% Exam 2, Friday, November 2, 2012
  
• 25% Final, during finals
  
• 20% Programming projects, homework assignments, and rare unannounced quizzes.  The total sum of points will weigh 20%.  The points per assignment or project will vary depending importance and effort.
  
• 25% Database project
  • This is a team project of 3 students based on one of several projects described below.
  • You will keep a printed portfolio of all designs, documents and source listings over the development of your project as a team including previous submissions in a loose leaf notebook.
  • Final project elements and submission guidelines
  • Due Monday, December 10, 2012, 4:00 p.m.
• Your final course grade can be adjusted upward (for extremely complimentary) or downward (for no contribution) according to peer evaluations by as much as 10%.

Previous year's exams are available for study. Links to study guides may be updated a few days before each exam.

Exams are a reflection of classroom and book theory, general concepts and personal understanding of the material; they will not necessarily cover programming project details. End of chapter exercises are excellent review questions for exams.

Assignments and programs:

Assignments (exercises listed below and those given in class) should be prepared for the following class meeting. Some may be collected for grading, others may just be reviewed in class. 

Programming projects, which are based on those in the text, will have their due dates announced in class or on the assignments. Some projects may be done in pairs only when clearly designated on the assignment. 

Project Descriptions:

The following projects are described in narrative form for each team to develop a functioning relational database by the end of the semester. Multiple teams may do the same project and the instructor will designate which of the projects may be selected for the semester. Not all projects will be implemented by the class.

• Photography Studio
• Wellness Clinic
• University Annual Fund
• Community Theater Group

Course policies

My standard policies on attendance, late assignments, academic integrity, etc., are described on this web page. Please read them carefully.

Disabilities Policy

The Americans Disabilities Act mandates accessibility in all aspects of the learning environment.  If you have an identified disability and are in need of specific accommodations, please notify the Office of Academic Support Services in Founders Hall and discuss your needs with me at the beginning of the semester.

DATABASE MANAGEMENT SYSTEMS
FALL 2012 TENTATIVE LECTURE/LAB OUTLINE

This schedule is a work in progress.  Assignments, case studies, and lecture notes will be under constant revision throughout the semester and may still contain references to notes from previous texts and editions. 

Exercises noted as "Review" are suggested as excellent chapter reviews and exam preparation. Exercises noted as "Homework" are expected to be written out for either credit and review during classtime, or as submitted for closer grading and credit. In either case they shall be neatly prepared for reading by others.

Notes and outlines as linked below are based on materials from the text by Ricardo, and the 2003 text by Lewis et al, which are copyrighted. Use of this material beyond the context of this course may infringe on the copyright of these texts.