You are asked to design part of a database about stage performers on sea-cruise shows, including information as follows:

A performer has an employee number, given name, contact address, bank account number and a list of shows that they are ready to perform. Note being ready to perform on a show doesnt mean they actually will perform it (they could be in the capacity of an understudy). It is also desired to be able to list the IDs of cruises that the performer has actually performed on.

A show has a unique title, a duration and type. A show may require multiple performers.

A cruise has a cruise ID, a start and destination port and associated start and end dates, and a list of shows scheduled for during the cruise.

Based on the above information, model the database requirements as an Entity-Relationship (ER) diagram. Carefully state any assumptions that you make. In your ER diagram, you must properly denote all applicable concepts, including weak or strong entities, keys, composite or multi-valued attributes; relationships and their cardinality and participation constraints.

After presenting your ER model to management, you are asked if it can be used to perform the following additional task: produce, for each cruise, a list of scheduled shows and, for each such show, a list of the performers who performed on it.

Explain, referring to your ER model how to produce the requested list. If it is not possible to produce the list from the model, state why, modify the model and provide the modified ER diagram (in addition to your original ER diagram), explaining how it can accommodate this requirement.