database; the database is used to keep track of airplanes, their owners, air- port employees, and pilots. From the requirements for this database, the fol- lowing information was collected: Each AIRPLANE has a registration number (Reg#1, is of a particular plane type (OF_TYPE), and is stored in a particular hangar [STORED IN). Each PLANE TYPE has a model number (Model, a capacity (Capacityl, and a weight [Weight). Each HANGAR has a number (Number), a capacity (Capacityl, and a location [Location). The database also keeps track of the OWNERS of each plane (OWNS) and the EMPLOYEES who have maintained the plane IMAINTAINJ. Each relationship instance in OWNS relates an AIRPLANE to an OWNER and includes the purchase date (Pdate). Each relationship instance in MAINTAIN relates an EMPLOYEE to a service record [SERVICEJ. Each plane undergoes service many times; hence, it is related by (PLANE SERVICEJ to a number of SERVICE records. A SERVICE record includes as attributes the date of maintenance [Date), the number of hourr mant

Computer Networking: A Top-Down Approach (7th Edition)
7th Edition
ISBN:9780133594140
Author:James Kurose, Keith Ross
Publisher:James Kurose, Keith Ross
Chapter1: Computer Networks And The Internet
Section: Chapter Questions
Problem R1RQ: What is the difference between a host and an end system? List several different types of end...
icon
Related questions
Question

Diagram. 

###### Model. 

 

 

 

4.21. Figure 4.12 shows an example of an EER diagram for a small-private-airport
database; the database is used to keep track of airplanes, their owners, air-
port employees, and pilots. From the requirements for this database, the fol-
lowing information was collected: Each AIRPLANE has a registration number
(Reg#), is of a particular plane type (OF_TYPE], and is stored in a particular
hangar [STORED_IN). Each PLANE TYPE has a model number (Model, a
capacity (Capacityl, and a weight [Weight). Each HANGAR has a number
(Number), a capacity (Capacityl, and a location [Location). The database also
keeps track of the OWNERS of each plane (OWNS] and the EMPLOYEES who
have maintained the plane IMAINTAINĮ. Each relationship instance in OWNS
relates an AIRPLANE to an OWNER and includes the purchase date [Pdate).
Each relationship instance in MAINTAIN relates an EMPLOYEE to a service
record [SERVICEJ. Each plane undergoes service many times; hence, it is
related by (PLANE SERVICE] to a number of SERVICE records. A SERVICE
record includes as attributes the date of maintenance [Date), the number of
hours spent on the work (Hours), and the type of work done Work code]l. We
use a weak entity type [SERVICEJ to represent airplane service, because the
airplane registration number is used to identify a service record. An OWNER
is either a person or a corporation. Hence, we use a union type (category)
(OWNER] that is a subset of the union of corporation [CORPORATION] and
person [PERSON] entity types. Both pilots [PILOT] and employees
(EMPLOYEEJ are subclasses of PERSON, Each PILOT has specific attributes
license number [(Lic_num] and restrictions [Restr); cach EMPLOYEE has spe-
cific attributes salary (Salary) and shift worked [Shift). All PERSON entities in
the database have data kept on their Social Security number [Ssn), name
(Name), address [Address), and telephone number [Phonel. For CORPORATION
entities, the data kept includes name [Name), address [Address), and
telephone number [Phone]. The database also keeps track of the types of
140
Chapter 4 The Enhanced Entity-Relationship (EER) Model
Salary
Shift
Model Capacity Weight
WORKS ON
EMPLOYEE
N
PLANE TYPE
MAINTAIN
Restr Lic_num
M.
FLIES
PILOT
OF TYPE
Date
Workcode
N
Date/workcode
Hours
SERVICE
Regt
AIRPLANE
PLANE SERVICE
Pdate
STORED IN
OWNS
N.
OWNER
M.
HANGAR
Location
CORPORATION
SanH PERSON
Number
Name
Phane
Name
Phone
Capacity
Address
Address
Figure 4.12
EER schema for a SMALL_AIRPORT database.
Transcribed Image Text:4.21. Figure 4.12 shows an example of an EER diagram for a small-private-airport database; the database is used to keep track of airplanes, their owners, air- port employees, and pilots. From the requirements for this database, the fol- lowing information was collected: Each AIRPLANE has a registration number (Reg#), is of a particular plane type (OF_TYPE], and is stored in a particular hangar [STORED_IN). Each PLANE TYPE has a model number (Model, a capacity (Capacityl, and a weight [Weight). Each HANGAR has a number (Number), a capacity (Capacityl, and a location [Location). The database also keeps track of the OWNERS of each plane (OWNS] and the EMPLOYEES who have maintained the plane IMAINTAINĮ. Each relationship instance in OWNS relates an AIRPLANE to an OWNER and includes the purchase date [Pdate). Each relationship instance in MAINTAIN relates an EMPLOYEE to a service record [SERVICEJ. Each plane undergoes service many times; hence, it is related by (PLANE SERVICE] to a number of SERVICE records. A SERVICE record includes as attributes the date of maintenance [Date), the number of hours spent on the work (Hours), and the type of work done Work code]l. We use a weak entity type [SERVICEJ to represent airplane service, because the airplane registration number is used to identify a service record. An OWNER is either a person or a corporation. Hence, we use a union type (category) (OWNER] that is a subset of the union of corporation [CORPORATION] and person [PERSON] entity types. Both pilots [PILOT] and employees (EMPLOYEEJ are subclasses of PERSON, Each PILOT has specific attributes license number [(Lic_num] and restrictions [Restr); cach EMPLOYEE has spe- cific attributes salary (Salary) and shift worked [Shift). All PERSON entities in the database have data kept on their Social Security number [Ssn), name (Name), address [Address), and telephone number [Phonel. For CORPORATION entities, the data kept includes name [Name), address [Address), and telephone number [Phone]. The database also keeps track of the types of 140 Chapter 4 The Enhanced Entity-Relationship (EER) Model Salary Shift Model Capacity Weight WORKS ON EMPLOYEE N PLANE TYPE MAINTAIN Restr Lic_num M. FLIES PILOT OF TYPE Date Workcode N Date/workcode Hours SERVICE Regt AIRPLANE PLANE SERVICE Pdate STORED IN OWNS N. OWNER M. HANGAR Location CORPORATION SanH PERSON Number Name Phane Name Phone Capacity Address Address Figure 4.12 EER schema for a SMALL_AIRPORT database.
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps with 1 images

Blurred answer
Recommended textbooks for you
Computer Networking: A Top-Down Approach (7th Edi…
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Concepts of Database Management
Concepts of Database Management
Computer Engineering
ISBN:
9781337093422
Author:
Joy L. Starks, Philip J. Pratt, Mary Z. Last
Publisher:
Cengage Learning
Prelude to Programming
Prelude to Programming
Computer Engineering
ISBN:
9780133750423
Author:
VENIT, Stewart
Publisher:
Pearson Education
Sc Business Data Communications and Networking, T…
Sc Business Data Communications and Networking, T…
Computer Engineering
ISBN:
9781119368830
Author:
FITZGERALD
Publisher:
WILEY