Chapter 6 Logical Database Design and the Relational Model

Chapter Objectives

The purpose of this chapter is to describe in depth the major steps in logical database
design, with more emphasis on the relational model. Logical database design is the process of
transforming the conceptual data model (described in Chapter 3 and 4) into a logical data model.
First, we provide a concise description of the relational data model, including the properties of
relations. Next, we describe and illustrate the various types of integrity constraints associated
with the relational model. This section introduces SQL table definitions, and the concept of
well-structured relations. We then provide a detailed description of the process of transforming
EER diagrams into relations. Next, we define normalization and describe the steps in
normalizing relations. The chapter concludes with a discussion of merging relations, and
techniques for dealing with typical issues that arise during this process.
Specific student learning objectives are included in the beginning of the chapter. From
an instructor's point of view, the objectives of this chapter are to:
1. Show students the position of logical database design within the overall database
development process. This is a key chapter in the textbook, since students will begin to
see how their databases will be implemented.
2. Provide students with a solid understanding of the relational data model, including the
properties of relations, integrity constraints, and well-structured relations.
3. Discuss the principles and detailed steps involved in mapping EER diagrams to relations.
Computer-assisted techniques are often used to speed up this process, but students should
still understand the principles involved.
4. Provide students with a firm grasp on the principles of functional dependencies,
determinants, and related concepts of normalization.
5. Emphasize why normalization is important to stable database design with the relational,
and then present a concise description of the various normal forms and the normalization
process.
6. Discuss some of the anomalies that arise when merging relations, and how to apply the
principles we have learned to address these anomalies.

Classroom Ideas

1. Motivate the need for logical database design. We sometimes start by showing the
students the conceptual data model (E-R diagrams) for Pine Valley Furniture Company
(Figure 3-21). Emphasize that this E-R diagram must be transformed through logical
database design before it can be implemented.
2. Preview the position of logical database design in the overall database development
process (see Figure 2-5). You might want to discuss who in the organization is usually
responsible for this step, and what CASE tools might be appropriate.
3. Discuss the relational data model, using Figures 6-1 through 6-4 as examples.
4. Introduce the important integrity constraints in the relational model using Figures 6-4 and
6-5 and Table 6-1. Emphasize that these constraints will be enforced by the DBMS, but
must first be specified by the designer.
5. Introduce SQL table definitions (Figure 6-6). Show how these definitions specify the
referential integrity constraints that are diagrammed in Figure 6-5.
6. Illustrate how anomalies can occur when relations are not well-structured, using Figures
6-2b and 6-7. Emphasize the fact that much real-world data (including relational data) is
not well-structured.
7. Discuss the process of transforming EER diagrams to relations (Figures 6-8 through 6-
22). We suggest you reinforce these concepts by asking your students (in teams of two)
to perform exercise 6a in class immediately following the discussion.
8. Preview the steps in normalization using Figure 6-23. You will want to use this figure
again to summarize normalization at the end of your discussion.
9. Discuss the concepts of functional dependencies, determinants, and candidate keys. Start
with your own examples on the board, then have your students give additional examples.
Summarize using Figure 6-23.
10. Discuss first through third normal forms, using Figures 6-24 through 6-26. Additional
normal forms (BCNF and 4NF) are presented in Appendix A, if time permits.
11. We strongly suggest for you to ask your students to work in small teams on one or more
Chapter-end exercises (exercises 3 and 4 work well for this purpose).

Answers to Review Questions

1. Define each of the following terms:

a. Determinant. The attribute on the left-handed side of the arrow in a functional
dependency.
b. Functional dependency. A constraint between two attributes or two sets of
attributes.
c. Transitive dependency. A functional dependency between two (or more) non-key
attributes.
d. Recursive foreign key. A foreign key in a relation that references the primary key
values of that same relation.
e. Normalization. The process of decomposing relations with anomalies to produce
smaller, well-structured relations.
f. Composite key. A primary key that consists of more than one attribute.
g. Relation. A named, two-dimensional table of data.
h. Normal form. A state of a relation that results from applying simple rules
regarding functional dependencies (or relationships between attributes) to that
relation.
i. Partial functional dependency. A functional dependency in which one or more
non-key attributes (such as Name) are functionally dependent on part (but not all)
of the primary key.
2. Contrast the following terms:
a. Normal form; normalization. Normal form is a state of a particular relation
regarding functional dependencies, while normalization is the process of
decomposing relations with anomalies to produce smaller, well-structured
relations.
b. Candidate key; primary key. A primary key is an attribute (or combination of
attributes) that uniquely identifies a row in a relation. When a relation has more
 than one such attributes (or combination of attributes), each is called a candidate
key. The primary key is then the one chosen by users to uniquely identify the
rows in the relation.
c. Functional dependency; transitive dependency. A functional dependency is a
constraint between any two attributes (or two sets of attributes), while a transitive
dependency is a functional dependency between two or more non-key attributes.
d. Composite key; recursive foreign key. A composite key is a primary key that
consists of more than one attribute, while a recursive foreign key is a foreign key
in a relation that references the primary key values of that same relation.
e. Determinant; candidate key. A determinant is on the left-hand side of the arrow
in a functional dependency, while a candidate key uniquely identifies a row in a
relation.
3. Six important properties of relations are:
a. Each relation in a database has a unique name.
b. An entry at the intersection of each row and column is atomic (or single valued).
c. Each row is unique.
d. Each attribute within a table has a unique name.
e. The sequence of columns is insignificant.
f. The sequence of rows is insignificant.
4. Describe two properties that must be satisfied by candidate keys:
a. Unique identification: for every row, the value of the key must uniquely identify
that row.
b. Nonredundancy: no attribute in the key can be deleted without destroying the
property of unique identification.
5. Three types of anomalies in tables:
a. Insertion anomaly: a new row cannot be inserted unless all primary key values
are supplied.
b. Deletion anomaly: deleting a row results in losing important information not
stored elsewhere.
c. Modification anomaly: a simple update must be applied to multiple rows.
6. Fill in the blanks.
a. second
b. first
c. third
7. A well-structured relation is a relation that contains a minimum amount of redundancy
and allows users to insert, modify, and delete the rows in a table without errors or
inconsistency. Well-structured relations are important because they promote database
integrity.
8. Describe how the following components of an E-R diagram are transformed to relations:
a. Regular entity type: each entity type is transformed to a simple relation. Each
simple attribute of the entity type becomes an attribute of the relation.
b. Relationship (1:M): a relation is created for each of the two entity types
participating in the relationship. The primary key attribute of the entity on the
one-side of the relationship becomes a foreign key in the relation on the many-
side of the relationship.
 c. Relationship (M:N): a new relation is created to represent this relationship. The
primary key for each of the participating entity types is included in this new
relation.
d. Relationship (supertype/ subtype): a separate relation is created for the supertype
and each of its subtypes. The primary key of the supertype is assigned to each
subtype, as well as attributes that are unique to the subtype.
e. Multivalued attribute: a new relation is created to replace the multivalued
attribute. The primary key of this new relation consists of two attributes: the
primary key of the original relation, plus the multivalued attribute itself.
f. Weak entity: a new relation is created corresponding to the weak entity. The
primary key of this relation consists of the primary key of the owner relation, plus
the partial identifier of the weak entity type.
g. Composite attribute: the simple component attributes of the composite attribute
are included in the new relation.
9. Four typical problems in merging relations:
a. Synonyms: two (or more) attributes have different names but the same meaning.
Solution: convince users to standardize on a single name.
b. Homonyms: a single attribute has more than one meaning.
Solution: create new attribute names that capture the separate meanings.
c. Transitive dependency: merging relations produces transitive dependencies.
Solution: create 3 NF relations by removing the transitive dependency.
d. Supertype/ subtype: may be implied by content of existing relations.
Solution: create new relations that explicitly recognize this relationship.
10. Three conditions that imply a relation is in second normal form:
a. The primary key consists of a simple attribute.
b. No non-key attributes exist in the relation.
c. Every non-key attribute is functionally dependent on the full set of primary key
attributes.
11. Integrity constraints enforced in SQL CREATE TABLE commands:
a. Entity integrity: enforced by NOT NULL clause.
b. Referential integrity: enforced by FOREIGN KEY REFERENCES statement.
12. Relationships between entities are represented by foreign key values in one relation that
match primary key values in another relation.
13. A 1:M unary relationship is represented be a recursive foreign key whose values
reference the primary key values of the same relation.
14. A M:N ternary relationship is represented by a new associative relation whose primary
key consists of the primary key attributes of the participating entity types.
15. All of the non-key attributes of a relation are functionally dependent on the primary key
of that relation.

Answers to Problems and Exercises

1. f well-structured relation
e anomaly
a functional dependency
j determinant
 g composite key
d 1NF
h 2NF
i 3NF
c recursive foreign key
k relation
b transitive dependency
2. Transforming E-R diagrams to relations:
a.
EMPLOYEE

Employee_ID Employee_Name Address Date_Employed

EMPLOYEE SKILL

Employee_ID Skill

b.
FLIGHT

Flight_No Date No_of_Passengers

c.

EMPLOYEE

Employee_ID Employee_Name

COMPLETION

Employee_ID Course_ID Date_Completed

COURSE

Course_ID Course_Title
d.
EMPLOYEE

Employee_ID Employee_Name

CERTIFICATE

Certificate_No Employee_ID Course_ID Date_Completed

COURSE

Course_ID Course_Title

e.
MOVIE

Movie_Name

VIDEO TAPE

Copy_No Movie_Name

f.
PRODUCT

Product_ID

Product_ID Effective_Date Price

g. To simplify this diagram, we divide it into three related subject areas: Sales,
Products, and Employees.
i) Sales Area:

SALESPERSON

Salesperson_ID Salesperson_Name Salesperson_Phone Salesperson_Fax Territory_ID

TERRITORY

Territory_ID

LOCATION

Customer_ID Territory_ID

CUSTOMER

Customer_ID Customer_Name Customer_Address

ORDER

Order_ID Order_Date Customer_ID

ORDER LINE

Product_ID Order_ID Quantity

To PRODUCT
 ii) Product Area:

PRODUCT LINE

Product_Line_ID Product_Line_Name
From
PRODUCES
PRODUCT

Product_ID Product_Description Product_Finish Unit_Price Product_Line_ID

From
ORDER LINE
USAGE

Product_ID Material_ID Quantity*

RAW MATERIALS

Material_ID Unit_of_Measure Unit_Price

SUPPLIES

Vendor_ID Material_ID Unit_Price

VENDOR

Vendor_ID Vendor_Name Vendor_Address

*The attribute Quantity was added to the USAGE relation following discussions with
users.
iii) Employee Area:

EMPLOYEE

Employee_ID Employee_Name Employee_Address Manager_ID

SKILL

Employee_ID Skill_ID

ASSIGNED

Employee_ID Work_Center_ID

WORK CENTER

Work_Center_ID Location

PRODUCES

Product_ID Work_Center_ID

To PRODUCT
3. Transforming EER diagrams to relations:
a.
VEHICLE

Vehicle_ID Price Make Model Engine_Displacement

CAR

C_Vehicle_ID No_of_Passengers

TRUCK

T_Vehicle_ID Car_Type Capacity

b.
RESPONSIBLE PHYSICIAN

Physician_ID

PATIENT

Patient_ID Admit_Date Physician_ID

OUTPATIENT

O_Patient_ID Checkback_Date

RESIDENT PATIENT

R_Patient_ID Date_Discharged

BED

Bed_ID R_Patient_ID
 c.

PART

Part_No Description Location Manufactured? Purchased? Quantity_on_Hand

MANUFACTURED PART

M_Part_No

PURCHASED PART

P_Part_No

SUPPLY LINE

P_Part_No Supplier_ID Unit_Price

SUPPLIER

Supplier_ID Supplier_Name
d.
PERSON

SSN Name Address Sex Date_of_Birth

EMPLOYEE

E_SSN Salary Date_Hired

FACULTY STAFF

F_SSN Rank S_SSN Position

ALUMNUS

A_SSN

DEGREES

A_SSN Degree Year Date

STUDENT

ST_SSN Major_Department

GRADUATE UNDERGRADUATE

GS_SSN Test_Score US_SSN Class_Standing

 e.
STUDENT

Student_ID Student_Name

REGISTRATION

Student_ID Course_ID Section_No Semester

SECTION

Course_ID Section_No Semester

COURSE

Course_ID Course_Name

QUALIFICATION

Course_ID Faculty_ID Date_Qualified

ASSIGNMENT

Faculty_ID Course_ID Section_No Semester

FACULTY

Faculty_ID Faculty_Name

4. The normal form for the relations are:

a. 3NF
b. 3NF
c. 2NF
CLASS (Course_No, Section_No, Room)
ROOM (Room, Capacity)
 d. 1NF
COURSE (Course_No, Course_Name)
CLASS (Course_No, Section_No, Room)
ROOM (Room, Capacity)
5. 3NF realtions for Millennium College are:
INSTRUCTOR (Instructor_Name, Instructor_Location)
COURSE (Course_No, Course_Title, Instuctor_Name)
STUDENT (Section_No, Student_Name, Major)
OUTCOME (Sutudent_No, Course_No, Grade)
6. Transforming an E-R diagram to relations:

CUSTOMER

Customer_ID Customer_Name Customer_Address

CARD ACCOUNT

Account_ID Expiration_Date Card_Type Customer_ID

DEBIT CARD

D_Account_ID Bank_No C_Account_ID Current_Balance

CHARGES

Merchandise_ID C_Account_ID Date Amount

MERCHANT

Merchandise_ID Merchandise_Address
7. Transforming Table 6-2 to relations:
a. PART SUPPLIER

Part_No Description Vendor_Name Address Unit_Cost

1234 Logic Chip Fast Chips Cupertino 10.00
1234 Logic Chip Smart Chips Phoenix 8.00
5678 Memory Chip Fast Chips Cupertino 3.00
5678 Memory Chip Quality Chips Austin 2.00
5678 Memory Chip Smart Chips Phoenix 5.00

b.
Part_No Description
Vendor_Name Address
Part_No, Vendor_Name Unit_Cost
c. Insert anomaly: we cannot insert a new vendor unless we also include a part
number.
Delete anomaly: if we delete part information, we also loose information about a
vendor who supplies that part.
Modification anomaly: if a vendor address changes, we have to modify all
records (or rows) for that vendor.
d.

Part_No Description Vendor_Name Address Unit_Cost

e. 1NF
f.
PART SUPPLIER

Part_No Description

Part_No Vendor_Name Unit_Cost

Vendor_Name Address
 8. Transforming Table 6-3 to relations:
a.

Student Student Campus Major Course_ID Course Instructor Instructor Grade

_ID _Name _Address _Title _Name _Location

b. 1NF
c.
STUDENT

Student_ID Student_Name Campus_Address Major

REGISTRATION

Student_ID Course_ID Grade

COURSE

Course_ID Course_Title Instructor_Name

INSTRUCTOR

Instructor_Name Instructor_Location
 d.
STUDENT

Student_ID Student_Name Campus_Address Major

REGISTRATION

Student_ID Course_ID Grade

COURSE

Course_ID Course_Title Instructor_Name

INSTRUCTOR

Instructor_Name Instructor_Location

Suggestions for Field Exercises

1. For this exercise, we suggest you interview at least two organizations: a manufacturing
company and a service sector organization (you may choose to combine this exercise with
Field Exercise 2 in Chapter 4). First, determine what methodology (if any) each uses for
conceptual design: E-R diagrams, object diagrams, etc. Then determine how these models are
transformed to logical data models (relational schema, object-oriented designs, etc.). To what
extent are these activities automated through the use of CASE tools? If the target data model
is relational, determine the role of normalization: who is responsible for normalization, to
what level is it performed, and how are users involved (if at all) in these activities?
2. We suggest you first perform this exercise as an in-class exercise with student participation in
the process. Bring a copy of your own document to class, and ask the students to volunteer a
document as well. This provides students with valuable “hands-on” experience in the bottom-
up design process.
3. For this exercise you may choose to assign a sample relational schema (such as Figure 6-13b
or 6-19b) as a basis for comparing the CASE tools.
4. This exercise is really a continuation of exercise 2 above, now possibly applied to a more
complex document. Use a report (or other document) that has detail lines and requires the use
of normalization skills.
Project Case

Project Questions

1. Mountain View Community Hospital will continue to use relational technology for
several reasons:
a. The present IS staff is trained and experienced in using this technology.
b. The present relational systems are stable and support existing operations quite
well.
c. Conversion to newer technology would be costly and would entail a number of
risks.
2. Yes, Mountain View Community Hospital should use normalization in designing its
relational database. Normalization helps avoid anomalies that impair data quality.
3. Entity integrity and referential integrity are important:
a. Entity integrity helps assure that two real-world entities (such as patient or tests)
are not confused.
b. Referential integrity helps assure that one real-world entity (such as a test result)
is not lost or disassociated from its owner entity (such as patient).
4. All users of data in the organization should be consulted during the normalization process
to ensure that the meaning and usage of data have been understood correctly.

Project Exercises

(See the next page)

1. Relational schemas for Mountain View Community Hospital.
a. Schema for E-R diagram (Exercise 2, Chapter 3):
WARD

Ward_No Ward_Name Employee_No

ASSIGNED

Ward_No Employee_No Hours

EMPLOYEE
Employee_No Employee_Name

BED
Bed_No Ward_No Room_No Patient_No

PATIENT

Patient_No Patient_Name Physician_ID

PERFORMS

Patient_No Physician_ID Treatment_No Results

PHYSICIAN TREATMENT
Physician_ID Physician_Name Treatment_No Treatment_Name

CONSUMES

Patient_No Item_No Date Quantity

ITEM

Item_No Description Unit_Cost

b. Schema for EER diagram (Exercise 1, Chapter4):
PERSON

Person_ID Name Address Birth_Date City_State_Zip Phone

PATIENT

PA_Person_ID Contact_Date PH_Person_ID

PHYSICIAN
PH_Person_ID Pager_No Specialty

VOLUNTEER

V_Person_ID Skill

EMPLOYEE

E_Person_ID Date_Hired

NURSE

N_Person_ID Certificate Name

STAFF

S_Person_ID Job_Class

TECHNICIAN

T_Person_ID Skill

LAB ASSIGN

T_Person_ID Name

LABORATORY CARE CENTER

Name Location Name Location
 To PATIENT RESIDENT

R_Person_ID Date_Admitted

OUTPATIENT

O_Person_ID (Other)

BED

Bed_No Room_No R_Person_ID

VISIT

O_Person_ID Date Comments

2. The functional dependencies are diagrammed in the above figures.

3. All of the relations are 3NF.
4. Following are some sample CREATE TABLE commands.
a. E-R diagram:

CREATE TABLE PATIENT

(PATIENT_NO INTEGER Not Null,
PATIENT_NAME VARCHAR(25) Not Null,
PHYSICIAN_ID VARCHAR(10) Not Null,
PRIMARY KEY (PATIENT_NO),
FOREIGN KEY (PHYSICIAN_ID) REFERENCES PHYSICIAN
(PHYSICIAN_ID));

CREATE TABLE PHYSICIAN

(PHYSICIAN_ID INTEGER Not Null,
PHYSICIAN_NAME VARCHAR(25) Not Null,
PRIMARY KEY (PHYSICIAN_ID));

b. EER Diagram:

CREATE TABLE PERSON

(PERSON_ID INTEGER Not Null,
NAME VARCHAR(25) Not Null,
BIRTH_DATE DATE,
ADDRESS VARCHAR(20),
CITY_STATE_ZIP VARCHAR(30),
PHONE VARCHAR(10),
 PRIMARY KEY (PERSON_ID));

CREATE TABLE PATIENT

(PA_PERSON_ID INTEGER Not Null,
CONTACT_DATE DATE Not Null,
PH_PERSON_ID INTEGER Not Null,
PRIMARY KEY (PA_PERSON_ID),
FOREIGN KEY (PA_PERSON_ID) REFERENCES PERSON (PERSON_ID),
FOREIGN KEY (PH_PERSON_ID) REFERENCES PHYSICIAN
(PH_PERSON_ID));

CREATE TABLE PHYSICIAN

(PH_PERSON_ID INTEGER Not Null,
PAGER_NO VARCHAR(10) Not Null,
SPECIALTY VARCHAR(10),
PRIMARY KEY (PH_PERSON_ID),
FOREIGN KEY (PH_PERSON_ID) REFERENCES PERSON (PERSON_ID));

5. You can use this exercise (or a selected subset) to illustrate the problems of merging
relations described in the chapter. You can also use this exercise to anticipate the design
of a data warehouse that consolidates user views (see Chapter 14).