COURSE POLICIES AND SYLLABUS
MIS 5612: DATABASE DESIGN AND ADMINISTRATION
First Module (August 24 – October 16), Fall 2009
Time: 6:00 p.m. - 9:40 p.m.
Place: PH 2040
Instructor: Laku Chidambaram
E-mail Address: firstname.lastname@example.org
Office: AH 307b
Office Phone: 325-8013
Office Hours: 3:30 p.m. - 5:30 p.m. Monday & Tuesday, and by appointment
Admin. Assistant: Donna Wade
E-mail Address: email@example.com
Office: AH 307a
thJ. A. Hoffer, M. B. Prescott, and F. R. McFadden, Modern Database Management (8 Edition), Pearson/Prentice Hall, 2007.
Upon completion of this course you will be able to:
1. create a conceptual and logical database design
2. build an enhanced entity-relationship model of an organization’s data
3. implement the database design using SQL
4. write, understand and debug SQL queries
Classes will include traditional lectures, in-class practice sessions and computer lab sessions. The computer labs will be held in AH 109 as indicated in the schedule. Course readings, homework assignments and the group project can all be found in the textbook. SQL Server will be used in our class labs and to implement the group project. I will use e-mail to notify you of any changes in the course schedule. Course information will also be posted on my website (see URL above).
Databases are at the heart of every large organization—both public and private. Whether you are
a manager, user or systems developer, you will be interacting with database management systems. This course will prepare you towards that end. However, you cannot expect to become an expert in database design after just one course … that takes longer and requires lots of practice. So, like any other skill, you have to keep working and keep practicing to master it.
If you are currently not enrolled in this course, you need to add it by the appropriate deadline. If you want to drop the course without penalty, you may do so by the appropriate date. For these and other deadlines, including receipt of an automatic grade of ―W‖, please consult the Schedule
of Classes or check with the Graduate Office.
A grade of I (for incomplete) will not be given under normal circumstances. Not performing well in class, not being able to complete a project in time or being out of town during a test are inadequate reasons for requesting or granting an incomplete. Only circumstances beyond your control—such as an illness—that will need to be documented may warrant a grade of an ―I‖.
I expect all students enrolled in this class to abide by all aspects of OU’s Honor Code. The two
basic tenets of this Code are:
1. Students will behave honorably, ethically, and responsibly in all academic matters both
inside the classroom and in outside work related to their courses.
2. Students who are aware of academic misconduct in any form will report the violation
to the instructor or other school representative. Students who are aware of academic
misconduct and who fail to report the violation are considered to be guilty of academic
For more details on the Honor Code, please check the OU website or ask the instructor.
Behaving ―honorably, ethically, and responsibly‖ means that everyone in class deserves to be
treated with respect and dignity—that includes all students, lab monitors and the instructor. So, we will resolve to address each other in a civil manner, without prejudice and without rancor.
Being civil also includes:
- Not browsing the web, checking e-mail or texting when in class or in the lab
- Not talking with your neighbor constantly when class is in session
- Not reading newspapers, magazines or other books
- Not being late to class or leaving early
- Not eating or drinking in class
- Not sleeping in class
If you want to engage in these activities, please do so outside class. If you are found to repeatedly engage in these activities, you will be asked to leave the class.
OTHER IMPORTANT NOTES
In this course, part of your course grade will be based on group projects. The reasons for group projects include:
1. Simulating a real-world systems development effort (where all information systems
projects are based on group work).
2. Enabling the execution of more extensive and challenging assignments than could
reasonably be completed on an individual basis.
All group members should work together on a given project. If there appears to be a problem, you should try to resolve it with the other members. If no resolution is possible, you need to inform me as soon as possible, so I can take appropriate action.
At the end of the course, each member of a group will be asked to provide an assessment of the proportion of work done by other members. If there is consensus within the group that a group member has clearly under- or over-performed on the group projects, the number of points earned on such projects will be adjusted downward or upward.
Due Dates for Assignments
Homework and project due dates are firm, unless a change is announced in class. Assignments
are due by 6:00 p.m. on the date specified in the class schedule. You may turn in assignments directly to me (in class) or leave them in my mailbox (in AH 305). A 20% penalty will be levied for each day that the assignment is late. After five days, no credit will be given for an assignment.
The examination dates are also firm. No changes to the exam dates will be made … please make
your travel plans accordingly. If something beyond your control, such as an illness (which needs to be documented), occurs a make-up exam may be given at the discretion of the instructor.
Final Exam 65%
Class Participation 5%
(Including attendance and in-class behavior)
Homework Assignments 15%
Database Project 15%
The exact breakpoints between letter grades will not be determined until the course is over. However, see below for an approximate guide to the lower limits for letter grades:
A – 90% or above
B – 80% to 89%
C – 70% to 79%
D – 60% to 69%
F – 59% or below
1. This is a tentative schedule and is subject to change! Based on the progress of our class,
technological limitations or classroom constraints, schedule changes can and will be made.
2. You will need to read Chapters 1 and 2 before you come to class on the first day. While
you will not be examined directly on the material in these chapters, they will inform what
we do throughout the semester.
SESSION DATE TOPIC READING WHAT’S DUE? #
1a. The Entity-Relationship Model Chapter 3
Aug. 24 (pp. 85-105)
1b. The E-R Model (contd.) Chapter 3
2a. The Enhanced E-R Model Chapter 4 Assignment 1 due
Aug. 31 (pp. 139-156)
2b. Lab 1 -- SQL: Introduction Chapter 7
3a. The E/E-R Model (contd.) Chapter 4 Project: Part I due
Sept. 14 (pp. 157-180)
3b. Lab 2 -- SQL: Querying Single Chapter 7
Tables (pp. 308-319)
4a. The Relational Model Chapter 5 Assignment 2 due
Sept. 21 (pp. 187-204)
4b. Lab 3 -- SQL: Aggregation and Chapter 7
Group Functions (pp. 320-326)
5a. The Relational Model (contd.) Chapter 5 Project: Part II
Sept. 28 (pp. 205-210) due
5b. Lab 4 -- SQL: Joins and Sub-Chapter 8
queries (pp. 333-348)
6a. Normalization Chapter 5 Assignment 3 due
Oct. 5 (pp. 211-222)
6b. Lab 5 -- SQL: Advanced Queries Chapter 8 (pp. 349-362)
Project: Part III 7. Oct. 12 Final Exam due