CpSc 462/662 (Section 1): Database Management Systems
Spring 2011

General Information:

      Class Time: 11:00 AM-12:15 PM   Tuesday and Thursday.
      Location: 415 Daniel Hall
      Instructor: Dr. James Z. Wang
      Office: 305 McAdams Hall
      Phone: 864-656-7678
      Email: jzwang@cs.clemson.edu
      Office Hours: 9:30 AM-10:30 AM   Tuesday and Thursday.
      Syllabus: http://www.cs.clemson.edu/~jzwang/1101462/syllabus.pdf

Final Exame Schedule:

             Wednesday, May 4, 3:00PM to 5:30PM

Presentation Schedule:

Date Presenters
04/19/2011 G1, G2, G3, G4, G5
04/21/2011 G6, G7, G8, G9
04/26/2011 U1, U2, U3, U4
04/28/2011 U5, U6, U7, U8

Notes and Schedule:

      01/13: Introduction
      01/18: ER Model and Database Design
      01/20: Relational Model
      02/03: SQL and MySQL
      02/08: Relational Schema and SQL Queries
      02/10: Relational Algebra
      03/10: HTML
      03/29: PHP Programming
      04/05: MySQL with PHP
      04/07: Views, Constraints, Triggers and Index
      04/12: Stored Procedure

Project:

      01/13: Project Description
      01/13: Please form your project team by January 24, 2011. You need to select a team leader who should email me all names in your team and their contact information.
      01/27: Project phase #1: ER diagram is due by 11:59PM on Wednesday, February 9, 2011. Your submission must include a cover page listing the team number and member names. You should submit your ER diagram in PDF file format and name the file as "teamX_p1.pdf" in which "X" is your team number. For instance, team U4 should name their file as "teamU4_p1.pdf". Please submit your project using Digital Dropbox in blackboard. Make sure press the SEND button after you upload the file.

Each team member must also evaluate the contribution of his/her teammates by filling the evaluation form. You must finish one evaluation form for each of your teammates and send the evaluate forms directly to the instructor by email. Please rename the evaluation file so that it includes the team number and the member name. Here is a sample evaluation.
      02/21: Project phase #2: Database Schema is due by 11:59PM on Tuesday, March 1, 2011. You can describe your database schema by table format, that is, desribe each relational table using the same format as given by the MySQL DESCRIBE statement. You can also use mysqldump (run through unix shell) or use phpMyAdmin's export function to dump the database schema into a text file.

You need to add necessary comments for all tables of your database schema. Your comments should simply describe the purpose of the table and the degree of normalization. You must try your best to convert all tables into 5NF. If a table is better to stay at the lower degree of normalization form (but at least 3NF), please state the reasons.

You may need to revise your ER diagram during the creation of your database schema, especially you need to add non-prime attributes to your entities if you did not do so in your first phase. If you revise your ER diagram, please submit your final ER diagram with your database schema. Please ZIP all your files into one single file before submission. Your submission must include a cover page indicating the team number and member names. You should name the file as "teamX_p2.yyy" in which "X" is your team number. That is, team U4 should name the file as "teamU4_p2.yyy", where "yyy" is the file extension. Please also upload a copy of your submission to your team directory in phoenix.cs.clemson.edu after you send it to me by email.

Each team member must also evaluate the contribution of his/her teammates by filling the evaluation form. You must finish one evaluation form for each of your teammates and send the evaluate forms directly to the instructor by email. Please rename the evaluation file so that it includes the team number and the member name. Here is a sample evaluation.
      03/05: Project phase #3: SQL Queries is due by 11:59PM on Friday, March 18, 2011. You are required to study YouTube and project description carefully to identify all functions that will be provided by your MeTube system. For each function, please write the necessary MySQL queries and test them with dummy data. You need to add necessary comments for all queries you write. Your comments should describe the relationship between the qureies and the related MeTube functions. If one MeTube function requires more than one MySQL queries to complete, please state the reason. Please also list the MeTube functions that do not require MySQL queries and state why no database access is needed for such queries.

You may need to revise your ER diagram and database schema when you design the MySQL queries. If you revise your ER diagram or DB Schema, please submit the new ER diagram and database schema with your queries. Please ZIP all your files into one single file before submission. Your submission must include a cover page indicating the team number and member names. You should name the file as "teamX_p3.yyy" in which "X" is your team number. That is, team U4 should name the file as "teamU4_p3.yyy", where "yyy" is the file extension. Please also upload a copy of your submission to your team directory in phoenix.cs.clemson.edu after you send it to me by email.

Each team member must also evaluate the contribution of his/her teammates by filling the evaluation form. You must finish one evaluation form for each of your teammates and send the evaluate forms directly to the instructor by email. Please rename the evaluation file so that it includes the team number and the member name. Here is a sample evaluation.
      04/04: Project phase #4: Final Report and Demonstration are due by 9:00AM on Tuesday, April 19, 2011. You should have completed your project by then. You are required to submit your source code, a technical report and presentation slides. Your technical report should include system design, ER diagram, database schema, function design, implementation details, test cases, testing results, and user manual or instruction.

Please ZIP all your files into one single file before submission. Your submission must include a cover page indicating the team number and member names. You should name the file as "teamX_p4.yyy" in which "X" is your team number. That is, team U4 should name the file as "teamU4_p4.yyy", where "yyy" is the file extension. Please also upload a copy of your submission to your team directory in phoenix.cs.clemson.edu after you send it to me by email.

Each team member must also evaluate the contribution of his/her teammates by filling the evaluation form. You must finish one evaluation form for each of your teammates and send the evaluate forms directly to the instructor by email. Please rename the evaluation file so that it includes the team number and the member name. Here is a sample evaluation.

You also need to sign up a time to demonstrate your project on or before April 29, 2011. In your demonstration, you will be asked to go through most of your test cases. The instructor may also ask you to test certain functions with certain input.

Project Teams:

      Team U1: Gina Guerrero, Matt Gallucci, Alex Propst (Undergraduate)
      Team U2: William Kirwan, Jack Merwin, Joseph Grant (Undergraduate)
      Team U3: Brittany Slisher, Justin Hurley, Goran Osim (Undergraduate)
      Team U4: Tim Myers, Paul Taylor, Peyton Greene (Undergraduate)
      Team U5: Patrick Van Stee, Jonathan Baulch (Undergraduate)
      Team U6: Cameron Hinkel, Gary Asciutto, Sameer Sherwani (Undergraduate)
      Team U7: Grant Giles, Justin Kimmett (Undergraduate)
      Team U8: Myles Cantrell, Nicholas Wourms (Undergraduate)
      Team G1: Kevin Jones, Josh Werts (Graduate)
      Team G2: Jerone Dunbar, Melva James (Graduate)
      Team G3: Mahesh Ananthanarayanan, Ramya Kailas (Graduate)
      Team G4: Haihua Yin, Dahao Qian (Graduate)
      Team G5: Dong Gu, Jin Xu (Graduate)
      Team G6: Chris Walling, Daniel Ward (Graduate)
      Team G7: Dongdong Wu, Yangyang He (Graduate)
      Team G8: Hanan A. Alnizami, Naja Mack (Graduate)
      Team G9: Wennian Li, Nikhil Vithlani (Graduate)

Academic Integrity:

“As members of the Clemson University community, we have inherited Thomas Green Clemson’s vision of this institution as a “high seminary of learning.” Fundamental to this vision is a mutual commitment to truthfulness, honor, and responsibility, without which we cannot earn the trust and respect of others. Furthermore, we recognize that academic dishonesty detracts from the value of a Clemson degree. Therefore, we shall not tolerate lying, cheating, or stealing in any form. In instances where academic standards may have been compromised, Clemson University has a responsibility to respond appropriately and expeditiously to charges of violations of academic integrity.”

“When, in the opinion of a faculty member, there is evidence that a student has committed an act of academic dishonesty, the faculty member shall make a formal written charge of academic dishonesty, including a description of the misconduct, to the Associate Dean for Curriculum in the Office of Undergraduate Studies. At the same time, the faculty member may, but is not required to, inform each involved student privately of the nature of the alleged charge.”

http://gradspace.editme.com/AcademicGrievancePolicyandProcedures#integritypolicy