DESIGN THE FOLLOWING ER MODEL:

EMPLOYEE is a role that a PERSON carries out within an organization. There are attributes related to each PERSON whether they are with the organization or not. There are attributes specific to each EMPLOYEE. Some attributes exist for both: Address, Phone, Email, etc. To begin to understand the complexity of this, you will model ADDRESS, PHONE and EMAIL as separate entities.

Each PERSON can relate to instances of ADDRESS differently (home, work, alternate, etc.). Each PERSON can relate to instances of PHONE differently (home, work, mobile, fax, etc.). Each PERSON can relate to instances of EMAIL differently (home, work, etc.). The lists of these different types of these relationships are Domain Entities. ADDRESS_TYPE, PHONE_TYPE, etc.

Requirement 1 Properly model PERSON and its M:N relationships to ADDRESS, PHONE, EMAIL. Include the TYPE in the relationship models as well as a Sequence attribute to allow ordering of these relationships for each PERSON. Each EMPLOYEE is hired for a POSITION in the organization. Each POSITION is supervised by another POSITION instance in a hierarchical manner. The organization itself is typically broken up into a hierarchy of DEPARTMENTs. Some POSITION instances have supervision responsibility for a DEPARTMENT. Each EMPLOYEE is compensated for their service in a POSITION. Over time each EMPLOYEE receives changes in compensation for a given POSITION or is assigned to another POSITION.

Requirement 2 Properly model the POSITION and DEPARTMENT hierarchies of the organization. Properly model EMPLOYEE and its relationship into the organization. Make provisions to document EMPLOYEE compensation (PayRate) and organization relationship changes over time. Ensure that redundant relationships are not created in your model.

Requirement 3 In a ER model note block, identify Business Roles (User-Defined Constraints) that are not captured in the model that is developed.