Wally Los Gatos, owner of Wally’s Wonderful World of Wallcoverings, has hired you as a c...

In the above ER diagram:

This system contains the six entities such as EMPLOYEE, DEPENDENT, BRANCH, ITEM, CUSTOMER, and ACCOUNT.

EMPLOYEE entity type:

• The entity EMPLOYEE is identified by the identifier has EMPLOYEE ID.

• The attributes of the EMPLOYEE entity has Employee Name, Employee Address, Employee Phone, Employee Title, Employee Salary, Employee Age, and Employee Hire Date.

• The multivalued attribute of the EMPLOYEE entity has Employee Skill.

• The composed attribute of the EMPLOYEE entity has Street, City, State, and ZipCode.

BRANCH entity type:

• The entity BRANCH is identified by the identifier has Branch No.

• The attributes of the BRANCH entity has Branch Location and Square Footage.

• The multivalued attribute of the BRANCH entity has Address, City, State, and ZipCode.

CUSTOMER entity type:

• The entity CUSTOMER is identified by the identifier has Customer ID.

• The attributes of the CUSTOMER entity has Customer Name, Customer Street Address, Customer City, Customer State, Customer Zip Code, Customer Phone, Customer DOB, and Customer Primary Language.

ACCOUNT entity type:

• The entity ACCOUNT is identified by the identifier has Account No.

• The attributes of the ACCOUNT entity has Account Type, Account Balance, Account Payment Date, and Account Payment Amount.

ITEM entity type:

• The entity ITEM is identified by the identifier has Item ID.

• The attributes of the ITEM entity has Item Description, Item Type, Item Pattern, Item Color, and Item Size.

• The weak entity DEPENDENT is identified by the identifier has Dependent Name.

• The attributes of the DEPENDENT entity has Dependent Relationship and Department Age.

Carries relationship:

The weak relationship between the entity EMPLOYEE and entity DEPENDENT is “Carries” and the cardinality relationship is “mandatory one to optional many”.

• This is because; employee may have more than one dependent.

Employs relationship:

The relationship between the entity EMPLOYEE and entity BRANCH is “Employs” and the cardinality relationship is “mandatory many to mandatory one”.

• This is because; employee must work in exactly one branch.

Sells relationship:

The weak relationship between the entity BRANCH and entity ITEM is “Sells” and the cardinality relationship is “mandatory many to mandatory many”.

• This is because; branch may sell all items or may sell only one item.

Serves relationship:

The relationship between the entity BRANCH and entity CUSTOMER is “Serves” and the cardinality relationship is “mandatory many to optional many”.

• This is because; branch has more than one customer and customer may or may not have one or more branch.

Contains relationship:

The relationship between the entity ITEM and associative entity ORDER is “Contains” and the cardinality relationship is “mandatory many to optional many”.

• This is because; orders are collected from one or more items.

Owns relationship:

The relationship between the entity CUSTOMER and entity ACCOUNT is “Owns” and the cardinality relationship is “mandatory one to optional many”.

• This is because; customer may have more than one account or no account.

Consists Of relationship:

The relationship between the entities ITEM is “Consists Of” and the cardinality relationship is “optional many to optional many”.

• This is because; item holds more than one items.

ORDER associative entity type:

• The associative entity ORDER between the entity BRANCH and entity CUSTOMER.

• It contains the attributes of the “Order Date” and “Order Credit Status”.

o The cardinality relationship between entity BRANCH and associative entity ORDER is “mandatory one to optional many”.

o The cardinality relationship between entity CUSTOMER and associative entity ORDER is “mandatory one to optional many”.