CS 451/551 Database Processing

Spring 2024

[ Assignments | Links | Databases | Slides | Handouts | Piazza ]

• Course Description In this class, we will learn about data modeling, relational models, normal forms, file organization, index structures, SQL, and concurrency control; we will design and implement actual database systems using MySQL, and we will create front-end Web pages to access our databases via PHP.
• Prerequisites: CIS 313, 314 (415 suggested)

• Time and Place: Wednesday, Friday 4:00-5:20 in room 128 Chiles

• CRN:
  • CS 451: 36016
  • CS 551: 36017

• Instructor: Chris Wilson
  • 326 Deschutes
  • office hours: WF 2:30-3:30
  • email cwilson@cs.uoregon.edu

• GTF: Ruimin Zhang
  • 234 Deschutes
  • office hours: M Th 4-5:30 (Zoom) and Th 12:30-2 (In-Person @ DES 234)
  • email ruiminz@uoregon.edu

• Links: Assorted pages offsite that may be of interest.
• Evaluation:
• The homework will be a combination of written and programming work.
• The Final Project will be due in parts: Part 1 is due Wednesday, May 22 and Part 2 on Thursday, June 13. We assume that you will work on it individually. If you wish to work in a group of two, please check with the instructor.

The approximate weighting of the work done is

Homework Assignments	37%
Test 1 (May 15))	18%
Test 2 (June 7)	18%
Final Project	27%

• Text: Database Management Systems (3rd ed) by Ramakrishnan and Gehrke

• Supplemental Reading: The free Red Book: Readings in Database Systems (5th Ed) by Bailis, Hellerstein, and Stonebraker (editors)

• Schedule

Week of	Chapter	Description	Events
Apr 1	1	intro, general concepts & architecture
Apr 8	3, 5	relational model, SQL
Apr 15	2, 3	data modeling (ER model)
Apr 22	4, 5	relational algebra, more SQL
Apr 29	19	normalization
May 6	8, 9, 10	normalization, indexes, test review
May 13	10	B-trees	Test 1 Wed May 15
May 20	16	transaction management	Final Project, Part 1: Wed, May 22
May 27	17	concurrency control
Jun 3	17, 18 (maybe)	concurrency and crash recovery, test review	Test 2 Fri, June 7
Jun 10		finals week	Final Project, Part 2: Thu, June 13

• Database Engine: Our default DBMS will be MySQL.

• Late policy: All assignments are due by midnight of the stated due date, though it is much safer to turn them in at class time. Assignments will be accepted for up to three days past the due date with a penalty of 5% per (calendar) day.

  Academic Honesty

  • All projects turned in for the course must be your own work. Copying from other class members or other sources is not acceptable. If you collaborate with someone else on any assignment, you must indicate such on the work you turn in. Collaboration that is not explicitly credited is plagiarism.
  • Academic honesty is expected and cases of suspected dishonesty will be handled according to university policy. In particular, copying someone else's work (including material found on the web) will not be tolerated. If solutions to assignments are obtained from outside sources, the source must be cited.
  • You are also responsible for protecting your work. That is, you must take reasonable precautions to prevent your work from being copied. This means that if you store your assignment solutions on a shared server, the file permissions must be set to keep others from accessing your files. If you are working on assignments in the lab, you must remove any of your files on the lab machine before you leave.
  • Turning in someone else's code is collusion, and is a particularly heinous form of plagiarism; if collusion is detected, all individuals involved (i.e., the copyee and all copyers) will be given a grade of F in the course.