4 questions regarding database

There are 4 questions that need to be explained.

Please look for the attached files.

Let me know if you have any questions.

EVENT
MANAGER
PK
Manager ID
Name
PK
Event ID
FK
Organiser ID
FK
Artist ID
Location
Date
Assistant Name
Country
Location
Cancelled
ARTIST
Artist
PK
Artist ID
Name
Music Type
FK
Manager ID
Gender
SOURCE OF
RECOMMENDATION
PK
FK
PROSPECTIVE ARTIST
MUSIC SAMPLES
Recommendation
ID
PK
FK
PK
Address
Artist ID
email
Source File
Music File
Name
honors
Source Reference
Music File
Artist ID
INSTRUMENT
PLAYED
Phone Number
Music Sample
ID
ID
Artist ID
Instrument
Name
University Degree
Year of Birth
University Degrees
Source of
Recommendation
Organiser
PK
CONTRACT
Organiser ID
Organiser Name
PK
Contract ID
FK
Artist ID
BILLING
PK
Billing ID
Event ID
Signed Date
Location
Billing Date
Royalty
Tax
Artist Fee
ARTIST EXPENSE
MANAGER EXPENSE
PK
FK
Manager Expense ID
PK
Event ID
FK
Expenses
Artist Expense ID
ARTIST
SCHEDULING
PK
Schedule ID
Event ID
Priority Level
Expenses
Date
CASE
Forondo Artist Management Excellence Inc.
Case Description
Having reviewed your conceptual models (from Chapters 2
and 3) with the appropriate stakeholders and gaining their
approval, you are now ready to move to the next phase of the
project, logical design. Your next deliverable is the creation of a
relational schema.
Project Questions
4-63. Map the EER diagram you developed in Chapter 3, 3-44
to a relational schema using the techniques described in
this chapter. Be sure to appropriately identify the primary
and foreign keys as well as clearly state referential integ-
rity constraints.
4-64. Analyze and document the functional dependencies in
each relation identified in 4-63 above. If any relation
is not in 3NF, decompose it into 3NF, using the steps
described in this chapter. Revise your relational schema
accordingly.
4-65. Does it make sense for FAME to use enterprise keys? If
so, create the appropriate enterprise keys and revise the
relational schema accordingly.
4-66. If necessary, revisit and modify the EER diagram you
created in Chapter 3,3-44 to reflect any changes made in
answering 4-64 and 4-65 above.
3-45.
As the prospective artists information were needed, though some of the information were already were
common for established artists, I created inheritance where in artist is a super type and prospective
artist was a subtype.
As there were many entities pertaining to artist alone, I created a cluster called artist.
Created a separate entity for recommendation, where in source and web reference (optional) is created.
As music samples of prospective artists were needed, I created a common entity for artists in general
where in a artists music samples can be stored.
An entity for scheduling artists time based on priority level has also been created.
In billing entity, costs have been split up to accommodate countries tax details./
As the manager needed instruments information regarding each artist, a separate entity has been
created.
3-46.
The database was already designed with reports and details to be generated. I believe the ERR is
captures sufficient details to generate relevant reports.
3-47.
I would first approach the manager to discuss with him if all his requirements are met. Once that has
been discussed will make necessary changes.
Once this is done, I would approach the owner of the FAME to update to him regarding the changes that
has been made according to the demands of manager and prospective artist. I would not approach
prospective artist for discussion because he is still of part of FAME. After getting the approval of the
owner, I would approach my manager for requesting any further changes that would optimize my ERR
Once signature of approval has been taken from all these stake holders, only then would I go ahead to
the next phase of the project.