Ch 3

Database Management System

Fall 2009 Department of Computer Systems Engineering, UET Peshawar

Ch 3

Chapter 3: Modeling Data in the Organization (contd.)

Ch 3
Developing an E-R diagram The development of an E-R diagram is an iterative process that involves designers and end users. It is based on interviews, reports, business forms, ... Example:We want to develop an E-R diagram for a "typical" U.S.A. University. 1. The university is divided into different schools, each one has a Dean
1
(1,1)
Database Management Systems, Fall 2009, DCSE

SCHOOL

runs

1
(1,1)

DEAN

Ch 3
2. Each school is composed of several departments
SCHOOL

1
(1,M)

belongs to

M
DEPT (1,1)

3. Each department offers several courses

1
(1,N)

DEPT

offers

M
COURSE (1,1)

4. A course may have several sections

1
(1,N)

COURSE

has

M
(1,1)

SECTION

Database Management Systems, Fall 2009, DCSE

Ch 3
5. Each department employs several professors, but each professor belongs to a single department. Each department is chaired by a chair, who is also a professor.
employs 1 (0,N) DEPT 1 (1,1)

(1,1) 1 (0,1) chairs

PROFESSOR

6. Each professor may teach up to 4 sections.

PROFESSOR

1
(0,4)

teaches

M
SECTION (1,1)

Database Management Systems, Fall 2009, DCSE

Ch 3

7.

Each student can take up to 6 courses. Each course has a capacity of 35 students.
M (1,35)

COURSE

ENROLL

M
(1,6)

STUDENT

The relationship ENROLL between SECTION and STUDENT is M:M, therefore, we need a bridge entity.

Database Management Systems, Fall 2009, DCSE

Ch 3

8. Each department has several student majoring in that department. But each student has one major.
DEPT

1
(1,N)

has

M
(1,1)

STUDENT

9. Each student is advised by one professor, but a professor can advise many students.
PROFESSOR

1
(0,N)

advises

M
STUDENT (1,1)

Database Management Systems, Fall 2009, DCSE

Ch 3
The database for the university includes 7 entities: SCHOOL, DEAN, DEPARTMENT, PROFESSOR, COURSE, SECTION, and STUDENT It includes also 10 relationships: Relationship Relation1 Relation2 belongs to school department runs dean school employs department professor offers department course has department student contains course section teaches professor section advises professor student chairs professor department enrolls student section
Database Management Systems, Fall 2009, DCSE

Ch 3
DEAN 1 runs

SCHOOL

(1,M)

belongs to

M
employs 1 1 1 DEPT has M

STUDENT M

1
chairs M 1 offers

M COURSE 1 1 has M M SECTION M

ENROLL

PROFESSOR 1

teaches

advises

Database Management Systems, Fall 2009, DCSE

Ch 3
E-R diagram for the University database The conceptual Relational Database schema (E-R model represented in the form of table structure) for the university is SCHOOL(scode, sname,saddress,deanID,sphone) primary key (scode) foreign key (deanID) references DEAN (deanID) DEAN(deanID,deanName, deanPhone) primary key (deanID) DEPT(dept#,scode, chair, deptPhone,deptAddress) primary key (dept#) foreign key (scode) references SCHOOL (scode) foreign key (chair) references PROF (facID) chair is the facID of the chairperson of the department
Database Management Systems, Fall 2009, DCSE

10

Ch 3
E-R diagram for the University database (cont.)
PROF(facID,SSN,name, address, phone, salary,dept#) primary key (facID) foreign key (dept#) references DEPT (dept#) COURSE(course#, courseName,credit,dept#) primary key (course#) foreign key (dept#) references DEPT (dept#) SECTION(call#,course#,facID, days,time,location) primary key (call#) foreign key (course#) references COURSE (course#) foreign key (facID) references PROF (facID)
Database Management Systems, Fall 2009, DCSE

11

Ch 3
E-R diagram for the University database (cont.)
STUDENT(S#,SSN,name,address,major,dept#,advisor)

primary key (S#) foreign key (dept#) references DEPT (dept#) foreign key (advisor) references facID note:advisor is facID of the professor advising the students ENROLL(S#,course#,grade) primary key (S#,course#) foreign key (S#) references STUDENT (S#) foreign key (course#) references COURSE (course#)

Database Management Systems, Fall 2009, DCSE

12

Example

Ch 3

The university keeps track of each student's name, student number, current address, permanent address and phone, birthdate, gender, year of study (1st, 2nd, 3rd, 4th ), major department, minor department (if any), and degree program (B.A., B.Sc., ..., Ph.D.). Some user applications need to refer to the city, county, and post code of the student's permanent address and to the student's last name. Each department is described by name, department code, office number and office phones. Both name and code have unique values for each department. Each course has a course name, description, code number, number of semester hours and offering department. The value of the code number is unique for each course. Each module has an instructor, semester, year, course and module number. The module number distinguishes different modules of the same course that are taught during the same semester/year; its values are 1, 2, 3, ..., up to the number of modules taught during each semester. A grade report has a student, module and grade.
Database Management Systems, Fall 2009, DCSE

13

Ch 3

Database Management Systems, Fall 2009, DCSE

14