Management excellence inc

Question 1 - Create a data dictionary, For each table in the relational schema developed earlier, provide the following information for each field/ data element: field name, definition/description, data type, format, allowable values, whether the field is required or optional, whether the field is indexed and the type of index, whether the field is a primary key, whether the field is a foreign key, and the table that is referenced by the foreign key field.

Question 2 - Create the physical data model for the relational schema developed earlier, clearly indicating data types, primary keys, and foreign keys.

You can use the below document, to complete these two questions.Forondo Artist Management Excellence Inc. Question 4-63 Step 1: EER diagram to relational schema: The following diagram below shows the relational schema mapped from ER diagram 1 Forondo Artist Management Excellence Inc. Step 2: In the above schema: • The strong entities are mapped to relation and their attributes are also shown • The underline attributes are the primary key for the give relation and the dotted underline is the foreign key referenced from the relation mapped by an arrow. • The compound entities are also mapped from the mapped relations Question 4-64 Step 1: Consider the relational schema given in 4-63. In this construction, the Customer and Event_organizers store similar points of interest of them. Be that as it may, it's smarter to store in one table and naming the one connection as client. Normalization from 2NF to 3NF The Artist Account and the Payment relations are interconnected. Similar points of interest are put away in both the relations as A_id, A_pay, A_net_Sal. As it were, the table is in 2NF yet not in 3NF. - When the table is in 3NF the useful reliance ought to be evacuated. - The useful reliance can be evacuated by part the traits into two tables of which the reliance is made. 2 Forondo Artist Management Excellence Inc. Step 2: The functional dependency is made between the Payee_id An id A_pay. At the end of the day, the artist id isn't essential key for installment connection however the installment made to a craftsman can be known by which payee paid to which craftsman. - So functional dependency can be expelled by making a_id as an essential key in craftsman record and afterward referenced it to remote key in Payment connection. - It's smarter to store the points of interest in the Artist_Account and after that referencing the copy elements in the installment connection. 3 Forondo Artist Management Excellence Inc. The relational schema is now revised and can be drawn as below: There is no functional dependency existing in this relational schema, Hence the table is in 3NF. 4 Forondo Artist Management Excellence Inc. Question 4-65 Step 1 – Enterprising Keys FAME should utilize the enterprising keys which are portrayed as follows. The ER outline incorporates the supertype/subtype connection. The supertype is protest which can be client, occasion organizaer, trough or a craftsman. So the connection is Object is made with characteristic - obj_id and obj_type. Thus the relation customer, manager and artist are modified as follows including the obj_id as a superkey. Step 2: Presently, the statistic points of interest of the customer manager and artist store indistinguishable subtle elements from the name and address subtle elements and contact points of interest. So the enterprise keys can be utilized here by including the connection PERSON with characteristics Obj_id, Name, Address, City, State, Phone_no. 5 Forondo Artist Management Excellence Inc. This can be given as follows.