Suppose you are given the following business rules to form the basis for a database design. The database must enable the manager of a company dinner club to mail invitations to the club's members, plan the meals, keep track of who attends the dinners, and so on$.$

Each dinner serves many members, and each member may attend many dinners.

A member receives many invitations, and each invitation is mailed to many members.

A dinner is based on a single entree, but an entree may be used as the basis for many dinners. For example, a dinner may be composed of a fish entree, rice, and corn. Or the dinner may be composed of a fish entree, a baked potato, and string beans.

A member may attend many dinners, and each dinner may be attended by many members.

Because the manager is not a database expert, the first attempt at creating the database uses the structure shown in attached file.

Given that structure, write its relational schema and draw its dependency diagram. Label all transitive and$/$or partial dependencies. $($Hint: This structure uses a composite primary key.$)$

Break up the dependency diagram you drew in to produce dependency diagrams for normal forms $1$NF$,2$NF$,$ and $3$NF$.($Hint: You might have to create a few new attributes. Also, make sure that the new dependency diagrams contain attributes that meet proper design criteria; that is$,$ make sure that there are no multi$-$valued attributes, that the naming conventions are met, and so on$.)$

Using the results, draw the Crow's Foot ERD.