Draw an extended entity$-$relationship diagram $($EERD$)$ based on the scenario below. If you discover while drawing the diagram that the scenario is incomplete, make up reasonable explanations to complete the story and supply your explanations along with the diagram.Figure $5\mathrm{.}4$ Specialization Hierarchy with Overlapping Subtypes

Scenario

ABC company wants to develop a database to keep information on its employees and the computers assigned to them. For each employee, the employee ID$,$ name, email, and phone number are kept. Among employees, only field managers and field workers are eligible to get a computer from the company for their work. Computers are not assigned to other types of employees. The unique attribute for field managers is salary; for field workers are #$\_$of$\_$hours$\_$worked and hourly$\_$rate.

The company gives its employees either a laptop or a tablet only. The company tag number and computer model number are kept for each computer. The unique attribute for laptop is keyboard; for tablet is touch$\_$screen

Note: In addition to the attributes given in the scenario, add at least two $(2)$ more attributes of your choice for employee and computer entities.

Requirements:

$$ Your EERD looks like the one shown in Figure $5\mathrm{.}4.$ Your EERD must show

o Entity: The proper number of entities and their names

o Attributes: In addition to the attributes given in the scenario, add at least two $(2)$ more attributes of your choice for employee and computer entities.

o Primary key and Foreign key

o Relationship:

$$ Max. and Min. cardinalities: If needed, you can put your justifications on

your answer document about why you use the cardinality

$$ Description $($text$)$ of the relationship between entities $($e$.$g$.,$ takes, advises,

has, etc.$)$

$$ Disjoint$/$overlapping constraints

$$ Subtype discriminators

$$ Partial$/$total completeness

$$ Use Crow$$s foot model $($notation$)$

$$ In drawing the diagram, you can use any $($diagraming$)$ software, such as Draw.io$,$ Microsoft

Visio, LucidChart, or even Microsoft Word.