Use a dependency diagram to determine the functional dependencies that exist in the following table.

Guest$($ person$\_$id$,$ first$\_$name, last$\_$name, phone, email, birthday, rsvp$,$ num$\_$attending, event$\_$id$,$ event$\_$name, begin$\_$time, end$\_$time, $($venue$\_$id$,$ venue$\_$street, venue$\_$city, venue$\_$state, venue$\_$zip, venue$\_$phone, venue$\_$notes$))$

RSVP can have values of yes, no or maybe while num$\_$attending indicates how many guests will accompany that person

Begin$\_$time and end$\_$time are date objects, meaning they include both date and time

Venue$\_$notes is a text object that allows for a description or rules to be stored

Include your dependency diagram in your submission.

$2.$ Using your dependency diagram, convert this table to an equivalent collection of tables that are in third normal form. Write the table definitions for the resulting tables using the following notation:

Table$\_$Name $($Primary$\_$Key, Attribute$1,$ Attribute$2,...$AttributeN$)$

$3.$ Create an ERD using Crow$$s Foot Notation in LucidChart of result tables. Paste an image of your ERD here for credit.

$4.$ Alter your ERD from #$3$ to support the following requirements:

Each event should have a coordinator that is ultimately responsible for it$.$ Those coordinators must have a $$Guest$$ account in the system.

We$$d like to store a list of caterers that are available at each venue. Caterers may have contracts with multiple venues and venues may accept contracts from multiple caterers, but ultimately, a single caterer will serve at each event. Use the following definition to include caterers in your ERD:

Caterer$($cater$\_$id$,$ cater$\_$name, cater$\_$contact, phone, e$-$mail, cuisine$\_$type$)$