QUESTION 1 (10 marks)

Business rules are important in data modeling because they govern how data are handled and
stored. Examples of basic business rules are data names and definitions. In terms of
conceptual data modeling, names and definitions must be provided for the main data objects:
entity types, attributes, and relationships and can be captured in a data model, such as an
entity-relationship diagram (ERD).

Below is a scenario of business rule in a furniture company. Understand the scenario and
create ERD for the scenario given.

A furniture company produces products. The following product information is stored: product
name, product ID and quantity on hand. These products are made up of many components.
Each component can be supplied by one or more suppliers. The following component
information is kept: component ID, name, description, suppliers who supply them, and
products in which they are used.

Create an ERD to show how you would track this information.

Show entity names, primary keys, attributes for each entity, relationships between the
entities and cardinality.

Assumptions

• A supplier can exist without providing components.

• A component does not have to be associated with a supplier.
• A component does not have to be associated with a product. Not all components are
used in products.
• A product cannot exist without components.
Question 2 (10 marks)

As a database analyst, prepare an ER diagram representing the requirements for a property

management company. Also prepare the text definition for each entity type and
attributes. Describe 2 more attributes/entities you would add to the information below. The
following business rules describes the company.

1. The company has a number of sales offices in several locations. A location is described
by the office number (key), an address, and the number of agents at the location.

2. Each sales office is assigned one or more employees. Attributes of employees include:
Employee_ID (key), and Employee_Name. An employee must be assigned to only one
sales office.

3. For each sales office, there is always one employee assigned to manage that office. An
employee may manage only the sales office to which s/he was assigned and an office
must always have one manager.

4. The firm lists properties for sale. Attributes of a property include Property_ID
(identifier) and Location. Components of Location include Address, City, State, and
Zip_Code. In addition, we want to know the selling price of the property and the year
it was constructed.

5. Each unit of property must be listed with one (and only one) of the sales offices and
one and only one agent in the company. A sales office may have any number of
properties listed, or may have no properties listed.

6. Each unit of property has one or more owners. Associated with an owner is Owner_ID
and Owner_Name. An owner may own one or more units of property. A feature of
the relationship between property and owner is Percent_Owned.
Question 3 (10 marks)

When transforming ER diagrams into relations typically results in well-structured relations.

However, there is no guarantee that all anomalies are removed by following these steps.
Normalization is the process of successively reducing relations with anomalies to produce
smaller, well-structured relations.

Below are questions related to Normalization. Answer all.

a) Why is this table not in 1NF?

b) Describe and illustrate the process of normalizing the data shown in this table to first
normal form (1NF).

a) Why is this table not in 2NF?

b) Describe and illustrate the process of normalizing the data shown in this table to
second normal form (2NF).
Question 4 (20 marks)

Based on the student result report from University of Southern New Jersey (USNJ), draw the
relation and illustrate the Normalization process until third normal form (3NF). Explain every
steps of the Normalization process from 1NF to 3NF.