Tiger Furniture Company
The Tiger Furniture Company sells a number of different furniture products around Kuala
Lumpur area. These products are grouped into several product lines. The identifier for a
product is Product_ID, while the identifier for a product line is Product_Line_ID.
Referring to the customer invoice, we identify the following additional attributes for
product: Product_Description, Product_Finish, and Unit_Price. Another attribute for
product line is Product_Line_Name. A product line may group any number of products,
but must group at least one product. Each product must belong to exactly one product
line.
Customers submit orders for products, the identifier for an order is Order_ID, and another
attribute is Order_Date. Meanwhile, also we should consider following details:
a. A customer may submit any number of orders at a time, although it is not
compulsory for a customer to submit any orders.
b. Each order is submitted by exactly one customer.
c. The identifier for a customer is Customer_ID. Other attributes include
Customer_Name and Customer_Address.
d. A given customer order must request at least one product.
e. Any product sold by Tiger Furniture may not be requested on any order, or
may be requested on one or more orders.
f. An attribute associated with each order and product is Quantity, which is the
number of units requested.
The Tiger Furniture has established another facility called sales territories for its
customers. Each customer does business in one or more of these sales territories. The
identifier for a sales territory is Territory_ID. A sales territory may have any number of
customers, or may not have any customers doing business.
Moreover, the Tiger Furniture Company has several salespersons. The identifier for a
salesperson is Salesperson_ID. The other attributes include Salesperson_Name,
Salesperson_Telephone, and Salesperson_Fax.. A salesperson serves exactly one sales
territory. Each sales territory is served by one or more salespersons.

Each product is assembled from one or more raw materials. The identifier for the raw
material entity is Material_ID. Other attributes include Unit_of_Measure and Unit_Price.
Each raw material may be assembled into one or more products.
The raw materials are supplied by vendors. The identifier for a vendor is Vendor_ID.
Other attributes include Vendor_Name and Vendor_Address. Each raw material can be
supplied by one or more vendors. A vendor may supply any number of raw materials, or
may not supply any raw materials to Tiger Furniture Company. An attribute of the
relationship between vendor and raw material is Unit_Price.

Can anyone help me to solve this??? I dont get it at all!!
1. List the possible business rules based on the scenario.
2. Identify all the entities and attributes.
3. Draw the E-R diagram and Relationship Schema to show the relationships
between the entities and attributes.
4. List the functional dependencies in your model. State the normal forms of your
relations.

Sure, show us what you've done so far and feel free to ask questions. Some of us will be happy to give you suggestions!

-PatP

The thing is I was hoping for someone to help me.....like I said I dont get it at all!!...I'll try though....

Thanks anyway

How to draw the E-R diagram???

College classes must be rough these days..

Identify your entities (e.g. Customer) and identify your attributes (e.g. customer_name) and attribute domains (customer_name: varchar(40)) and then put it all together using whatever notation you're supposed to learn.

A simple way of identifying entities is to look for nouns in the description. Attributes can be identified by looking at adjectives and adverbs.

How to represent one-one relation between products and product_line and one-many relation between product_line and products?

Relation <> Relationship. That's probably worth looking up for a start.

A relationship cardinality is two way. You can't have it one to one in one direction and one to many in another. Why would you even want to? It seems like you are on point 3. You done 1 & 2?

pootle flump ur codings are working excelent.

Thanks pootle flump.
I dont see any points, but Iam just a beginner in this field, just had a crash course of 4 days... so all silly doubts!!
Can u tell me how would be the relationship between these two entities?

poots, come on, of course each relationship has two different cardinalities

each product belongs to only one product line == 1 product, 1 product line

each product line has multiple products == 1 product line, N products

r937,
each product belongs to only one product line == 1 product, 1 product line

each product line has multiple products == 1 product line, N products

yup, this is given in the requirement above, but what would be the next step, like how to represent this relation in the ERD?

it is represented in the ERD by a line, with numbers near the ends of the line

products ---------product_line
many --------- one
is this relation correct?

r937,
I developed an ERD, Can u let me know if Iam wrong somewhere!!

yes, you should not have product_id FK in the product_line table

FKs implement one-to-many relationships, and the FK always goes in the "many" table

you should try to do your ERD without resorting to surrogate "id" keys

but perhaps your teacher will overlook this problem

Thanks very much r937.

Actually, my crash course is done and now my teacher is not guiding me, as the course is done.

I think then, I should not have Product_id in order_detail table and order_id should be in Product table.
Is that right?

Thanks again.