Tutorial 3 DB U2000429

WIA2001/WIB2001
DATABASE
SEM 1, 2022/2023
Tutorial 3
1. Why business rules are important for a good database design? Give 3 examples of business
rules in academic environment.
Business rule help standardize company’s view of data and act as a communication tool
between users and designers. They allow the creator to develop relationship participation
rules and constraints and to create a correct data model. They also allow the creators to
understand business processes, and the nature, role and scope of the data.
Example: a. Every student must have at least 40% marks to pass a subject
b. Students need to have more than 80% attendance in order to sit for an exam
c. The maximum number of a lower grade subjects a student can take is 3
2. What is the definition of DDL and DML? Explain the differences between DDL and DML.
DML: environment in which data can be managed and is used to work with the data in the
database
DDL: enables the database admin to define the schema components
The difference is DML manipulate data inside database while DDL used when want to
create, delete or edit tables.
3. Refer to Figure 2.0 below and answer the following questions:
Figure 2.0: DealCo Relational Diagram

i. Identify each relationship type and write all of the business rules.
Region and Store: one-to-many
One region can have one or many stores but one store can’t have many
region
Store and Employee: one-to-many

One store can have one or many employees but one employee can’t work in
many store
Employee and Job: many-to-many

One employee can have one or many jobs and one job can be assigned to
one or many employees.
ii. Create the basic Crow’s Foot ERD for DealCo.
4. i. How would you identify entity and relationship types from a user’s requirements
specification?
To identify entity is by searching the nouns for example staff number or staff
names. It can also be a major object such as people or places. Typically,
relationships are indicated by verbs or verbal expression such as register, work etc.
ii. How would you identify attributes from a user’s requirements specification and
then associate the attributes with entity or relationship types?
The attributes can be identified where the noun or noun phrase is a property, quality,
identifier, or characteristic of one of these entities or relationships.
As there are generally many more attributes than entities and relationship, it may
be useful to first produce a list of all attributes given in the users’ requirements
specification. As an attribute is associated with a particular entity or relationship,
remove the attribute from the list. In this way, we ensure that an attribute is
associated with only one entity or relationship type and, when the list is empty, that
all attributes are associated with some entity or relationship type,
5. The following tables form part of a database held in a relational DBMS:-
Hotel (hotelNo, hotelName, city)

Room (roomNo, hotelNo, type, price)
Booking (hotelNo, guestNo, dateFrom, dateTo, roomNo)
Guest (guestNo, guestName, guestAddress)
where
Hotel contains hotel details and hotelNo is the primary key;
Room contains room details for each hotel and (roomNo, hotelNo) forms the
primary key;
Booking contains details of the bookings and (hotelNo, guestNo, dateFrom)
forms the primary key;
and
Guest contains guest details and guestNo is the primary key.
Based on the schema above,

i) Explain why the primary keys are chosen as such for each of the table. The
primary keys that are chosen for each of the table is due to the attributes being
attributes that store values that are unique and can not be null.
ii) Identify the foreign keys for each of the table (if any).
a. Booking – hotelNo
b. Booking – guestNo
c. Booking – roomNo
d. Room – hotelNo
iii) Explain how the entity and referential integrity rules apply to these relations.
a. For each relation, the primary key must not contain any nulls. Room is
related to Hotel through the attribute hotelNo. Therefore, the hotelNo in
Room should either be null or contain the number of an existing hotel in the
Hotel relation. In this case study, it would probably be unacceptable to have
a hotelNo in Room with a null value. Booking is related to Hotel through the
attribute hotelNo. Therefore, the hotelNo in Booking should either be null or
contain the number of an existing hotel in the Hotel relation. However,
because hotelNo is also part of the primary key, a null value for this attribute
would be unacceptable. Similarly, for guestNo. Booking is also related to
Room through the attribute roomNo.

Tutorial 3 DB U2000429

Uploaded by

Copyright:

Available Formats

Tutorial 3 DB U2000429

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tutorial 3 DB U2000429

Uploaded by

Copyright:

Available Formats

WIA2001/WIB2001

3. Refer to Figure 2.0 below and answer the following questions:

Figure 2.0: DealCo Relational Diagram

Store and Employee: one-to-many

Employee and Job: many-to-many

ii. Create the basic Crow’s Foot ERD for DealCo.

Hotel (hotelNo, hotelName, city)

Based on the schema above,

You might also like