Develop a database to help "YourPerfectEvent" event planners to manage their operations. The database must be able to accommodate the following.
 

A customer contacts the company and makes arrangements for their event. They are required to put
down a 10% deposit on the event and then to make payments as scheduled in their contract. The
database must collect information appropriate for a customer entity and also have the ability to record
deposits and payments for events.

 

Events are held at many different locations around the city. The database must hold information about
the location like address, rate, etc. It also will need to store a list of available services from a preset list.
For example, the coordinator should be able to check off handicap accessible, kitchen on premises, and
air conditioned (these are examples of services that might or might not be available but it is a set
list...imagine checkboxes on a form that the coordinator might fill out). There should also be an area for
a venue to mention other features that might not be on the list...an "Other" option.
 

The database needs to store information about employees as well as assign them to certain events.
Include appropriate attributes for an employee but also have something similar to preset checklist for
special skills (e.g. bilingual, knows CPR, etc.) Also have an "other" category that is not preset.

 

For each event, a coordinator is assigned from the 27 employees in the company. Then, depending on
the size of the event and availability of staff, one or more employees are assigned as support for the
coordinator.
 

Finally, the database needs to keep track of outside vendors. Will you need a DJ? Rent extra chairs?
Provide food from a caterer? The database needs to keep track of which companies Your Perfect Event
does business with and they need to be tied to....events.
 

The database needs to keep track of which events are scheduled, where they're scheduled, who's
working them, and which outside vendors are needed.

 

HINT: There are many M:N relationships here that need to be broken down with a bridge/join table.
You will get some points without recognizing these and resolving them but most of the points come
from demonstrating your understanding of this.
 

Question:

Draw an ERD showing the design of the database you intend to build. Use Crow's Foot design for
the ERD and indicate known cardinality where appropriate in parentheses. Explain any business
rules/limitations that might affect the design of your database in a text box on your ERD