Database SpecificationsDatabase Design, Spring 2016 – Kyungpook National University

Project Title

University Database

Project Members

John Doe, Jane Doe, G.I. Joe & G.I. Jane

Database Description

The primary users of the university database will be students and faculty. The students will use the DB to find courses to enroll in, check their grades, and keep track of the meetings with their advisors (Note: 8 advising sessions required for graduation). The professors will query the database to get the listing of classes taught and students enrolled in them. The faculty will also search the DB to obtain the contact information for any university employees.

Database Objectives

Generate a course listing by semester (e.g., professor, department, class time & place) For each professor, generate the classes taught & student grades for each class. For each student, generate the complete listing of advising sessions (e.g, date, time,

advisor) For each school, generate a list of all employees by department. For each department, generate a listing of all double-major students. Find the contact information for the TA (or professor) in any department.

Business Rules

A school can have many departments. Each department belongs to one school. A department has many employees. An employee works in one departments. An employee can be a professor or a staff. A course generates many classes. Each class belongs to a course. A professor teaches many classes. A class is taught by one professor. A student can take many classes. A class has many students. A student belongs to one department. A department has many students. A student may double-major in another department. A department can have many

double-major students.

E-R Diagram

Relational Schema

Note: A simplified data dictionary, which lists attributes with primary and foreign key designations for each table, can be substituted for the relational schema diagram.