Problem 1.
For this problem, the appropriate solution would be removing the FK RepNum from Customer table and adding the PK from Customer table as FK to the Rep table. Therefore, it is understood that each Rep can represent one or more Customers.

Customer (CustomerNum, CustomerName, Street, City, State, PostalCode, Balance, CreditLimit)

Rep (RepNum, LastName, FirstName, Street, City, State, PostalCode, Commission, Rate, CustomerNum)
CustomerNum
CustomerName
CreditLimit
Street City
State
PostalCode
Balance
Represented
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
CustomerNum
CustomerName
CreditLimit Street City
State
PostalCode
Balance
Represented
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum

Customer
Customer

n n 1
1

Problem 2.
To solve this problem, the PK RepNum from Rep table would be added to Orders table. Order table would be compost of CustomerNum, RepNum, OrderNum and OrderDate. As a result, when user places an order it won’t matter who the rep will be.

Customer (CustomerNum, CustomerName, Street, City, State, PostalCode, Balance, CreditLimit)

Rep (RepNum, LastName, FirstName, Street, City, State, PostalCode, Commission, Rate, CustomerNum)

Orders (CustomerNum, RepNum, OrderNum and OrderDate)

CustomerNum
CustomerName
CreditLimit Street City
State
PostalCode
Balance
Orders
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
CustomerNum
CustomerName
CreditLimit Street City
State
PostalCode
Balance
Orders
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum

Customer
Customer

n n OrderNum
OrderNum
OrderDate
OrderDate

1
1

Problem 3.
Item (ItemNum, Description, Category, Price, StoreNum)
PK – ItemNum
FK - StoreNum

Storehouse (StoreNum, StoreDescription, UnitNum)
ItemNum
Description mNum
Category
Price
Item
ItemNum
Description mNum
Category
Price
Item
PK – StoreNum
AK – UnitNum

Exist
Exist

Storehouse
StoreNum
StoreDescription
UnitNum
Storehouse
StoreNum
StoreDescription
UnitNum

Problem 4.
Customer (CustomerNum, CustomerName, Street, City, State, PostalCode, Balance, CreditLimit, TerritoryNum)
PK - CustomerNum
AK - TerritoryNum

Rep (RepNum, LastName, FirstName, Street, City, State, PostalCode, Commission, Rate, CustomerNum, TerritoryNum)
PK - RepNum
AK - TerritoryNum

Territory (TerritoryNum, TerritoryName, CustomerNum, RepNum)

CustomerNum
CustomerName
CreditLimit Street City
State
PostalCode
Balance
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
Customer
TerritoryNum
TerritoryName
Territory located located
CustomerNum
CustomerName
CreditLimit
Street City
State
PostalCode
Balance
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
Customer
TerritoryNum
TerritoryName
Territory located located

1
1

1
1

1
1

1
1

Problem 5.
Customer (CustomerNum, CustomerName, Street, City, State, PostalCode, Balance, CreditLimit, TerritoryNum, TerritoryName, RepNum)

Rep (RepNum, LastName, FirstName, Street, City, State, PostalCode, Commission, Rate, CustomerNum, TerritoryNum, TerritoryName, RepNum)

CustomerNum
CustomerName
CreditLimit Street City
State
PostalCode
Balance
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
Customer
TerritoryNum
TerritoryName
Territory located located
CustomerNum
CustomerName
CreditLimit
Street City
State
PostalCode
Balance
Rep
Rate
Commission
PostalCode
State
City
Street
LastName
RepNum
Customer
TerritoryNum
TerritoryName
Territory located located

1
1

1
1

1
1

1
1

Problem 6.
Adding a new attribute to the Customer table called ShipAddress as optional would solve this problem.

Customer (CustomerNum, CustomerName, Street, City, State, PostalCode, Balance, CreditLimit)

Shipping (ShippingNum, ShippingAddress, CustomerNum)

Customer
CustomerNum
CustomerName
Street
City
State
PostalCode
Balance
Customer
CustomerNum
CustomerName
Street
City
State
PostalCode
Balance

1
1
n n Has
Has
ShippingNum
ShippingAddress mNum
Shipping
ShippingNum
ShippingAddress mNum
Shipping
CreditLimit
CreditLimit