1. Convert ERD into relations (as relational schema):

i. Map strong entities to relations.

ii. Map multivalued attributes. If any

iii. Map weak entities if any.

iv. Map binary relationships.

v. Map associative entities if any.

vi. Map unary relationships if any.

vii. Map ternary and n-ary relationships if any.

2. Identify functional dependencies.

3. Propose a set of meaningful business rules on all referential integrities.

4. For each foreign key in each relation:

i. Identify the primary key and base relation that is being referenced.

ii. Identify the referential integrity for ON DELETE and the associated business rule.

iii. Identify the referential integrity for ON UPDATE and the associated business rule.

Terps Enterprise, Inc. ERD: Department Employee Terps Enterprise, Inc. Assign dotid CMASSN aptName empName Supervise Manage dpiLoc[1..3] HempFName .empMinit Organize -empleme Standale empDOB Project empGender Dependent Work Carry prild empAddress H dadName priName empStreet dpdDOB priLOG empCity dodGender hours -ompState relationship -empZip empSalary EweekHours Relations: Functional dependencies: Business rules: Referential integrities: Relation Foreign Base Primary Business Constraint: Business Constraint: Key Relation Key Rule ON DELETE Rule ON UPDATE