Course Title: Database Systems Lab

Course: CSE-414
Assignment-5
Date: 24-12-2023

Author: Ishrat Jereen

ID: 21701083
Department: Computer Science and Engineering
Course: CSE-414
Submitted to: Dr. Rudra Pratap Deb Nath
Associate Professor
Department of Computer Science and Engineering
University of Chittagong

1
Contents
1 Chapter 6 2
1.1 Q-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Q-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Q-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Q-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Q-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6 Q-9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.7 Q-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.8 Q-14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.9 Q-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.10 Q-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.11 Q-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.12 Q-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.13 Q-23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.14 Q-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.15 Q-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1
1 Chapter 6
1.1 Q-1
Problem Statement:
Construct an E-R diagram for a car insurance company whose customers own one or more cars
each. Each car has associated with it zero to any number of recorded accidents. Each insurance
policy covers one or more cars and has one or more premium payments associated with it. Each
payment is for a particular period of time, and has an associated due date, and the date when the
payment was received

Answer - 1 : One possible E-R diagram is shown in Figure 6.101. Payments are modeled as weak
entities sin e they are related to a spe i poli y. Note that the parti ipation of a
ident in the relationship parti ipated is not total, sin e it is possible that there is an a
ident report where the parti ipating
ar is unknown

1.2 Q-2
Problem Statement:
Consider a database that includes the entity sets student, course, and section from the univer-
sity schema and that additionally records the marks that students receive in different exams of
different sections. a. Construct an E-R diagram that models exams as entities and uses a ternary
relationship as part of the design. b. Construct an alternative E-R diagram that uses only a
binary relationship between student and section. Make sure that only one relationship exists be-
tween a particular student and section pair, yet you can represent the marks that a student gets
in different exams.

Answer - 2(a) : The E-R diagram is shown in Figure 6.102. Note that an alternative is to model
examinations as weak entities related to a se tion, rather than as strong entities. The marks
relationship would then be a binary relationship between student and exam, without dire tly involving
se tion.

2
Answer - 2(b): The E-R diagram is shown in Figure 6.103. Note that here we have not modeled the
name, pla e, and time of the exam as part of the relationship attributes. Doing so would result in dupli
ation of the information, on e per student, and we would not be able to re ord this information
without an asso iated student. If we wish to represent this information, we need to retain a separate
entity orresponding to ea h exam.

1.3 Q-3
Problem Statement:
Design an E-R diagram for keeping track of the scoring statistics of your favorite sports team.
You should store the matches played, the scores in each match, the players in each match, and
individual player scoring statistics for each match. Summary statistics should be modeled as
derived attributes with an explanation as to how they are computed.

Answer - 3 : The diagram is shown in Figure 6.104. The derived attribute season score is computed by
summing the score values associated with the player entity set via the played relationship set

3
1.4 Q-5
Problem Statement:
An E-R diagram can be viewed as a graph. What do the following mean in terms of the
structure of an enterprise schema? a. The graph is disconnected. b. The graph has a cycle

Answer - 5(a) : If a pair of entity sets are connected by a path in an E-R diagram, the entity sets are
related, though perhaps indiretly. A disconneted graph implies that there are pairs of entity sets that
are unrelated to each other. In an enterprise, we can say that the two parts of the enterprise are
completely independent of each other. If we split the graph into conneted components, we have, in
effect, a separate database corresponding to each independent part of the enterprise.

Answer - 5(b): As indicated in the answer to the previous part, a path in the graph between a pair of
entity sets indicates a (possibly indirect) relationship between the two entity sets. If there is a cycle in
the graph, then every pair of entity sets on the cycle are related to each other in at least two distinct
ways. If the E-R diagram is a acyclic, then there is a unique path between every pair of entity sets and
thus a unique relationship between every pair of entity sets.

1.5 Q-7
Problem Statement:
A weak entity set can always be made into a strong entity set by adding to its attributes the
primary-key attributes of its identifying entity set. Outline what sort of redundancy will result if
we do so.

Answer - 7 : The primary key of a weak entity set can be inferred from its relationship with the strong
entity set. If we add primary-key attributes to the weak entity set, they will be present in both the
entity set, and the relationship set and they have to be the same. Hence there will be redundancy.

1.6 Q-9
Problem Statement:
Suppose the advisor relationship set were one-to-one. What extra constraints are required on
the relation advisor to ensure that the one-to-one cardinality constraint is enforced?

Answer - 9 : In addition to declaring s ID as primary key for advisor, we declare i ID as a superkey for
advisor (this can be done in SQL using the unique constraint on i ID).

4
1.7 Q-13
Problem Statement:
An E-R diagram usually models the state of an enterprise at a point in time. Suppose we wish
to track temporal changes, that is, changes to data over time. For example, Zhang may have
been a student between September 2015 and May 2019, while Shankar may have had instructor
Einstein as advisor from May 2018 to December 2018, and again from June 2019 to January 2020.
Similarly, attribute values of an entity or relationship, such as title and credits of course, salary,
or even name of instructor, and tot cred of student, can change over time. One way to model
temporal changes is as follows: We define a new data type called valid time, which is a time
interval, or a set of time intervals. We then associate a valid time attribute with each entity and
relationship, recording the time periods during which the entity or relationship is valid. The end
time of an interval can be infinity; for example, if Shankar became a student in September 2018,
and is still a student, we can represent the end time of the valid time interval as infinity for the
Shankar entity. Similarly, we model attributes that can change over time as a set of values, each
with its own valid time. a. Draw an E-R diagram with the student and instructor entities, and
the advisor relationship, with the above extensions to track temporal changes. b. Convert the
E-R diagram discussed above into a set of relations. It should be clear that the set of relations
generated is rather complex, leading to difficulties in tasks such as writing queries in SQL. An
alternative approach, which is used more widely, is to ignore temporal changes when designing
the E-R model (in particular, temporal changes to attribute values), and to modify the relations
generated from the E-R model to track temporal changes.

Answer - 13(a) : The E-R diagram is shown below. The primary key attributes student id and
instructor id are assumed to be immutable, that is, they are not allowed to change with time. All
other attributes are assumed to potentially change with time.Note that the diagram uses multivalued
composite attributes such as valid times or name, with subattributes such as start time or value. The
value attribute is a subattribute of several attributes such as name, tot cred and salary, and refers to
the name, total credits or salary during a particular interval of time.

Answer - 13(b): The generated relations are as shown below. Each multivalued has turned into a
relation, with the relation name consisting of the original relation name concatenated with the name of
the multivalued attribute. The relation corresponding to the entity has only the primary-key attribute,
and this is needed to ensure uniqueness.
student(student id)
student valid times(student id, start time, end time)
student name(student id, value, start time, end time)
student dept name(student id, value, start time, end time)
student tot cred(student id, value, start time, end time)
instructor(instructor id)
instructor valid times(instructor id, start time, end time)

5
instructor name(instructor id, value, start time, end time)
instructor dept name(instructor id, value, start time, end time)
instructor salary(instructor id, value, start time, end time)
advisor(student id, instructor id, start time, end time)
The primary keys shown are derived directly from the E-R diagram. If we add the additional
constraint that time intervals cannot overlap (or even the weaker condition that one start time cannot
have two end times), we can remove the end time from all the above primary keys.

1.8 Q-14
Problem Statement:
Explain the distinctions among the terms primary key, candidate key, and superkey

Answer - 14 :
Superkey:
Definition:
A superkey is a set of one or more attributes (columns) that, taken collectively, can uniquely identify a
record in a table.
Uniqueness:
A superkey must have the property that no two different records have the same combination of values
for the attributes in the superkey.
Example:
In a “Person” table, a superkey could be the combination of “Social Security Number” and “Date of
Birth,” as this combination uniquely identifies each person.
Candidate Key:
Definition: A candidate key is a superkey for which no proper subset is a superkey. In other words, it
is a minimal superkey. Uniqueness: Like a superkey, a candidate key uniquely identifies each record in
the table. Example: In the “Person” table, “Social Security Number” alone might be a candidate key
because removing either attribute would cause it to lose its uniqueness.
Primary Key:
Definition:
The primary key is a selected candidate key that is designated to uniquely identify each record in a
table. It is a special case of a candidate key.
Uniqueness and Not Null:
The primary key must be unique for each record, and it cannot contain null values.
Example:
From the candidate keys, you might choose “Social Security Number” as the primary key for the
“Person” table.

1.9 Q-15
Problem Statement:
Construct an E-R diagram for a hospital with a set of patients and a set of medical doctors.
Associate with each patient a log of the various tests and examinations conducted.

Answer - 15 : patientTests is a ternary relationship set.

Another method is, to make the testsAndExaminations entity a weak entity having identifying entity
set Patient. And then adding a relationship set between the weak entity testsAndExaminations and
MedicalDoctor, representing which medical doctor performed which test and examination. In fact
doing that has the added benefit of constraining each entity in testsAndExaminations to a single
Patient.

6
But using a ternary relationship as depicted in the above diagram, also has its benefits. For example,
if a group of patients are tested and examined by the same type of test and have the same result, we
might associate each of the patients in the group to the same entity in testsAndExaminations.

1.10 Q-19
Problem Statement:
We can convert any weak entity set to a strong entity set by simply adding appropriate at-
tributes. Why, then, do we have weak entity sets?

Answer - 19 : We have weak entities for several reasons:

• We want to avoid the data duplication and consequent possible inconsistencies caused by duplicating
the key of the strong entity.
• Weak entities reflect the logical structure of an entity being dependent on another entity.
• Weak entities can be deleted automatically when their strong entity is deleted.
• Weak entities can be stored physically with their strong entities.

1.11 Q-21
Problem Statement:
Consider the E-R diagram in Figure 6.30, which models an online bookstore.
a. Suppose the bookstore adds Blu-ray discs and downloadable video to its.collection. The same
item may be present in one or both formats, with differing prices. Draw the part of the E-R
diagram that models this addition,showing just the parts related to video.
b. Now extend the full E-R diagram to model the case where a shopping basket may contain any
combination of books, Blu-ray discs, or downloadable video.

Answer - 21(a) : Here,Blu ray discs and downloadable videos are weak entities while video in bluray
and video on net are the identifying relationships sets. video is the identifying entity set and owns
both of the weak entities.

7
Answer- 21(b):

1.12 Q-22
Problem Statement:
Design a database for a worldwide package delivery company (e.g., DHL or FedEx). The
database must be able to keep track of customers who ship items and customers who receive
items; some customers may do both. Each package must be identifiable and trackable, so the
database must be able to store the location of the package and its history of locations. Locations
include trucks, planes, airports, and warehouses. Your design should include an E-R diagram, a set
of relational schemas, and a list of constraints, including primary-key and foreign-key constraints.

Answer - 22 : The above figure displays the E-R diagram of the database for the automobile company.
The attribute options of the entity set car type is a composite attribute. The ternary relationship set
sales represents a single trasaction or a sale of a car. A dealer may have never sold a car or have sold
numerous cars. A customer may have never bought a car or have bought numerous cars. But a
particular car has either been sold or in stock. This constraints are represented as mapping
cardinalities in the diagram.
When we change the diagram to a relational schema we get the following:
car type(car type id, model, brand, color, electric or gas, self driving or not,solar panel on roof)
car(VIN, car type id, dealer id)
customer(customer id, name, phone number, address)
dealer(dealer id, name, phone number, address)
sale(VIN, customer id, dealer id, amount, timestamp)
The attributes car type id and dealer id in the relation car are foreign-keys referencing car type and
dealer relations respectively. The sale relation has VIN, customer id and dealer id as foreign-keys
referencing the relations car type, customer and dealer respectively.

8
 1.13 Q-23
Problem Statement:
Design a database for an automobile company to provide to its dealers to assist them in
maintaining customer records and dealer inventory and to assist sales staff in ordering cars.
Each vehicle is identified by a vehicle identification number (VIN). Each individual vehicle is
a particular model of a particular brand offered by the company (e.g., the XF is a model of the
car brand Jaguar of Tata Motors). Each model can be offered with a variety of options, but an
individual car may have only some (or none) of the available options. The database needs to store
information about models, brands, and options, as well as information about individual dealers,
customers, and cars.
Your design should include an E-R diagram, a set of relational schemas, and a list of constraints,
including primary-key and foreign-key constraints.

Answer - 23 :
The above picture shows E-R diagram for the package delivery company. Note that it uses
specialization/generalization and aggregation. Also the specialization is both total and disjoint.
Relation Schemas:
customer(customer id, name, phone number, address)
package(package id,mass,shape,extra care note,sent from,sent to,timestamp sent,
timestamp arrived,timestamp expected to arrive)
location(location id)
truck(location id, truck license plate, color)
plane(location id,plane id)
airport(location id,airport name,city,country)
warehouse(location id,latitude,longitude,altitude)
location of package(package id, location id, start timestamp, end timestamp)
The primary key of truck, plane, airport, and warehouse is location id. Note also that their primary
key is also a foreign key to the location relation.
Another foreign-key can be found in the package relation. Both sent from and sent to attributes are
foreign-keys from the package relation referencing the customer relation.
The location id of the relation location of packages references the location relation. The package id of
the relation location of packages references the package relation.

9
 1.14 Q-24
Problem Statement:
Design a database for an airline. The database must keep track of customers and their reserva-
tions, flights and their status, seat assignments on individual flights, and the schedule and routing
of future flights. Your design should include an E-R diagram, a set of relational schemas, and a
list of constraints, including primary-key and foreign-key constraints.

Answer - 24 :
Relation schemas:
customer(customer id, name, phone number, address)
flights(flight id,src,dest,timestamp src,timestamp dest) reservation(customer id,flight id)

1.15 Q-26
Problem Statement:
Design a generalization–specialization hierarchy for a motor vehicle sales company. The com-
pany sells motorcycles, passenger cars, vans, and buses. Justify your placement of attributes at
each level of the hierarchy. Explain why they should not be placed at a higher or lower level.

Answer - 26 :

10
11