Scribd
Upload
194 views

Tutorial 2

This document contains 5 questions regarding database design and normalization. Question 1 asks to define functional dependencies, candidate keys, and normalize a relation to 3NF. Question 2 asks to draw an entity relationship diagram and design tables in 3NF for an order entry system. Question 3 asks to design a relational schema in 3NF or BCNF for a university transcript database. Question 4 asks to analyze a relation for 1NF, 2NF, and 3NF and perform successive normalization. Question 5 asks to analyze a relation for 2NF and 3NF and perform normalization if needed.

Uploaded by

SOMEONE
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
194 views

Tutorial 2

This document contains 5 questions regarding database design and normalization. Question 1 asks to define functional dependencies, candidate keys, and normalize a relation to 3NF. Question 2 asks to draw an entity relationship diagram and design tables in 3NF for an order entry system. Question 3 asks to design a relational schema in 3NF or BCNF for a university transcript database. Question 4 asks to analyze a relation for 1NF, 2NF, and 3NF and perform successive normalization. Question 5 asks to analyze a relation for 2NF and 3NF and perform normalization if needed.

Uploaded by

SOMEONE
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

KING SAUD UNIVERSITY

COLLEGE OF APPLIED STUDIES AND COMMUNITY SERVICE


CT1313 (Database Design)
Second Semester 1434-1435
Tutorial #2
Q1- A relation NADDR is defined as follows.
NADDR = (name, street, city, state, postal_code), where name is unique, and for any given postal
code, there is just one city and state
a. Give a set of FDs for this relation.
b. What are the candidate keys?
c. Is NADDR in3NF? 2NF? Explain why?
d. If NADDR is not in 3NF, normalize it into 3NF relations.
Q2- A database used in an order-entry system is to contain information about customers,
items and orders. The following information is to be included.
For each customer:
Customer number (unique)
Ship-to addresses (several per customer)
Balance
Credit limit
Discount
For each order:
Heading information: customer number, ship-to address, date of order
Detail lines (several per order): item number, quantity ordered
For each item:
Item number (unique)
Manufacturing plants
Quantity on hand at each plant
Stock danger level for each plant
Item description
For internal processing reasons a quantity outstanding value is associated with each detail line
of each order. This value is initially set equal to the quantity of the item order and is
(progressively) reduced to zero as (partial) shipments are made.
The following semantic assumptions can be made:
No two customers have the same ship-to address.
Each order is identified by a unique order number.
Each detail line within an order is identified by a line number, unique within the order.
Draw a functional dependency diagram and design a set of the tables in the third normal form
(3NF) for the system.
Q3-

Suppose we have the following requirements for a university database that is used to

keep track of students' transcripts:


(a) The university keeps track of each student's name (SNAME), student number
(SNUM), social security number (SSSN), current address (SCADDR) and phone (SCPHONE),
permanent address (SPADDR) and phone (SPPHONE), birthdate (BDATE), sex (SEX), class

(CLASS) (freshman, sophomore, ..., graduate), major department (MAJORDEPTCODE), minor


department (MINORDEPTCODE) (if any), and degree program (PROG) (B.A., B.S., ..., Ph.D.).
Both SSSN and student number have unique values for each student.
(b) Each department is described by a name (DEPTNAME), department code
(DEPTCODE), office number (DEPTOFFICE), office phone (DEPTPHONE), and college
(DEPTCOLLEGE). Both name and code have unique values for each department.
(c) Each course has a course name (CNAME), description (CDESC), code number
(CNUM), number of semester hours (CREDIT), level (LEVEL), and offering department
(CDEPT). The value of code number is unique for each course.
(d) Each section has an instructor (INSTUCTORNAME), semester (SEMESTER), year
(YEAR), course (SECCOURSE), and section number (SECNUM). Section numbers distinguish
different sections of the same course that are taught during the same semester/year; its values
are 1, 2, 3, ...; up to the number of sections taught during each semester.
(e) A transcript refers to a student (SSSN), refers to a particular section, and grade
(GRADE).
Design an relational database schema for this database application. First show all the functional
dependencies that should hold among the attributes. Then, design relation schemas for the
database that are each in 3NF or BCNF. Specify the key attributes of each relation. Note any
unspecified requirements, and make appropriate assumptions to make the specification
complete.

Q4- Consider the following relation:


CAR_SALE(Car#, Date_sold, Salesman#, Commision%, Discount_amt
Assume that a car may be sold by multiple salesmen and hence {CAR#, SALESMAN#} is the
primary key. Additional dependencies are:
Date_sold ->Discount_amt
and
Salesman# ->commission%
Car# -> Date_sold
Based on the given primary key, is this relation in 1NF, 2NF, or 3NF? Why or why not? How
would you successively normalize it completely?
Q5-

Consider the following relation:

R (Doctor#, Patient#, Date, Diagnosis, Treat_code, Charge)


In this relation, a tuple describes a visit of a patient to a doctor along with a treatment code and
daily charge. Assume that diagnosis is determined (uniquely) for each patient by a
doctor. Assume that each treatment code has a fixed charge (regardless of patient).
Is this relation in 2NF? Justify your answer and decompose if necessary. Then argue whether
further normalization to 3NF is necessary, and if so, perform it.

You might also like