Syllabus (Spring 2018)

Course Description

Storage of and access to physical databases including indexing, hashing, and range accesses. Relational data models, database design principles, query languages, query optimization, transaction processing and recovery techniques. Object-oriented and distributed databases.


There will be 1000 points distributed thoughout the course via homeworks, exam and projects. There will be no extra credit points.

Points GPA
900-1000 4.0
850-900 3.5
800-850 3.0
750-800 2.5
700-750 2.0
650-700 1.5
600-650 1.0
0-600 0.0

Requirements To Receive A Passing Grade

To be eligible to earn a non-zero grade in the course, a student normally must do ALL the following:

  • Earn at least 50% (150 points) of the total points on the exam.

If you failed to get half the points on the exam, you may request an oral exam if you believe your performance on exam was not an accurate representation of your understanding of the course material. Your request must include an explanation of why your poor exam performance wasn't an accurate indication of your understanding and provide your avaliabilities to have an hour-long oral exam within two weeks of the exam's being returned. This request would be in a private Piazza Post.

Important: Contact your instructor, if you have any concerns about your performance in the class.


There will be at least 12 weekly homeworks (through Mimir). The homeworks are intended to be straightforward if you have done the projects and done the lectures. Only your top 10 homework scores will count toward your final grade; all others will be dropped. The counted scores will each be worth 20 points for a total of 20% of your final grade. Homeworks are always due the Thursday after they are assigned at 10pm. Not submitting your homework on time may result in zero points for that assignment.


The exam will occur approximately 2/3 of the way through the semester (see the Schedule) and will cover all of the material to that point. It will be worth 300 points (30% of your final grade). We will hand out a sample exam at least one week before the actual exam that will closely resemble it so that you know exactly what to expect. There will be no final exam.


There will be six projects over the course of the semester, each contributing in total 500 points (50%) to your final grade. Project durations range between 9 days and two weeks, and will be due at 10pm at the end of the due date. Make sure that you turn in projects on time because each will build on the previous, so if you're late on one it make completing the next more difficult.

All projects should be implemented in Python and we strongly recommend that you refresh your Python knowledge if you haven't used the language recently.

Project Grade Distribution
  • Project 1: 50 points
  • Project 2: 100 points
  • Project 3: 100 points
  • Project 4: 100 points
  • Project 5: 100 points
  • Project 6: 50 points
Late Project Turn In

If you do hand in a project late, you will 10% of the project's points per day. No project will be accepted more than 2 days late so that solutions can be made available.


Those who participate in class provide us with another source of information as to how well they are learning the material, and how much effort they are putting into the course. We can use this information to help counterbalance a difficulty with exams or projects. Let's have an active class! Class participation will never harm your grade; always ask any questions you may have about the material. We strongly encourage students to ask and answer each others questions on Piazza. Although there aren't points associated with participation in this class, providing helpful answers on Piazza or giving constructive criticism on the class can improve your grade. Once initial grades are assigned, participation can boost grades up one step (that is, one-half letter grade or 0.5 on a 4-point scale). If your grade is borderline, we may consider your participation to sway our decision to your advantage.

The Spartan Code of Honor Academic Pledge

As a Spartan, I will strive to uphold values of the highest ethical standard. I will practice honesty in my work, foster honesty in my peers, and take pride in knowing that honor in ownership is worth more than grades. I will carry these values beyond my time as a student at Michigan State University, continuing the endeavor to build personal integrity in all that I do.‚Äč

Collaboration On Coding Assignments

Plagiarism (unsourced use of other's intellectual property) is not allowed. However, citing and using other's works is generally fine (please ask if uncertain) as long as the material wasn't made specifically for solving assignments for this class. Additionally, the use of material from previous semesters and code from other students in the class are instances of academic dishonesty. Intellectual (non-code) collaboration with other students in the class is allowed, but each student should write (and not share) their own code. If a student submits code that they don't understand, such is also an act of academic dishonesty.

Academic Dishonesty

Because a goal of this course is to teach professionalism, any academic dishonesty will be viewed as evidence that this goal has not been achieved, and will be grounds for receiving a final grade of 0.0. Examples of academic dishonesty include (but are not limited to):

  • Copying another student's code or exam answers, or sharing your own solution.
  • Using code implemented by someone else intended to solve this class's assignments (i.e., don't get someone else to do your assignment for you!).
  • Using code independently implemented by someone else without attributing credit (i.e., you can use tools, libraries, or code snippets from the web, but cite them!)
  • Writing code that deceptively passes the test cases, but doesn't solve the problem given. In other words, abusing the auto-grader to give unearned points
  • Using websites and sources, whose purpose is to provide assignment solutions (e.g. using for any purpose regarding this class).
  • Submitting a solution that you don't understand / can't explain to an instructor.
  • Providing false information to the instructor about matters related to the course
  • Facilitating another student in any of these activities

See Academic Dishonesty and Attribution for more details.

Depending on circumstances, we may require a code audit of your work, where you meet with an instructor and explain how your code works and how you came up with it.

Grief Absence Policy

If their occur unfortunate circumstances that would lead you to have unexpected absences, MSU has a Grief Absence Policy. You need to contact the Associate Dean, and we will make every effort to aid you in continuing the class after we recieve confirmation from the administration.

Incomplete Grades

According to the university, the grade of "incomplete" is reserved for "exceptional cases, where an unanticipated event beyond one's control interferes with a student's completion of course requirements."


Requests for regrading can go in either direction; we are often generous when we first grade something, so please be sure that we did make a mistake before you submit your request. On the other hand, our goal is for you to understand the course material, so we will always be willing to explain to you any portion that you are stuck on. All requests for regrades must come within one week of the return of the graded item. Thereafter, no requests will be considered, so be sure to pick up your returned assignments on time.

Resource Center for Persons with Disabilities

Michigan State University is committed to providing equal opprotunity for participation in all programs, services and activities. Requests for acommodations by persons with disabilities may be made by contacting the Resource Center for Persons with Disabilities at 517-884-RCPD. Once your eligibility for an accommodation has been determined, you will be issued a verified individual services accommodation ("VISA") form. Please present this form to me at the start of the term and/or two weeks prior to the accommodation date (exam, project, etc.). Requests received after this date will be honored whenever possible.

General Note

The goal of this class is for you to learn. If you find that anything is coming in your way of that goal, please talk with us about it. We plan to keep the class flexible to the learning styles that seem to work best for the students, so feedback is always appreciated.