Functional Dependency Mapping

Viewed 31

ER Diagram

As a result of incorrect application of 7-step mapping process, it was mapped into following relations.

Contact(type, StoreNo*, details, S_Postcode*)
Store(StoreNo, S_Street, S_Suburb, S_Postcode, staffNo*, startDate, ManagerStaffNo*, S_Name*)
Staff((StaffNo, S_Name, S_Address, Position, Salary, SupervisorStaffNo*, SupervisorStaffName*)
Product(ProductNo, P_Name, P_Description, P_salePrice)
Order(OrderNo, OrderDate, C_Email*, C_name*)
Customer(C_Email, C_Name, C_Street, C_Suburb,C_Postcode, CreditCardNo*, expiryDate*, securityCode*)
Contains(productNo*, OrderNo*, OrderDate*, Contains_qty)
Stock(StoreNo*, ProductNo*, P_Name*, P_salePrice*, stock_qty)

For each of these relations, write down all functional dependencies. If there are no functional dependencies among attributes, you must state so. Do not write down trivial functional dependencies.

My Attempt:

Contact:
    StoreNo - > S_Postcode -> details
    StoreNo, type -> details
Store:
    StoreNo -> S_Street, S_Suburb, S_Postcode 
    StoreNo, S_Street -> S_Suburb, S_Postcode
    StoreNo, S_Suburb -> S_Postcode
    staffNo, ManagerStaffNo -> S_Name 
Staff:
    StaffNo -> S_Name, S_Address, Position, Salary 
    StaffNo, Position -> Salary
    SupervisiorStaffNo -> SupervisorStaffName, S_Address, Position, Salary 
Product:
    ProductNo -> P_Name, P_Description, P_salePrice
    ProductNo, P_Name -> P_Description, P_salePrice
Order:
    OrderNo -> OrderDate 
    OrderNo, C_Email -> C_Name, OrderNo, OrderDate
Customer:
    CredtCardNo -> expiryDate, securityCode, C_Name
    CreditCardNo, C_Name -> C_Email, C_Street, C_Suburb, C_Postcode
Contains: 
    productNo -> Contains_qty
    productNo, OrderNo -> OrderDate
Stock: 
    ProductNo -> P_Name, P_salePrice, stock_qty
    ProductNo, P_Name -> P_salePrice
    StoreNo -> N/A

I don't know whether this is correct. A lot is overlapping.

0 Answers
Related