Tranfer ER-Diagrams below to Data Table with Entity in Caps; Attribute - first l

Question

Tranfer ER-Diagrams below to Data Table with Entity in Caps; Attribute - first letters in caps.

NEWS RECOMMENDATION Is about PROSPECTIVE ITEM ARTIST Recommendation ID News Item ID PArtist ID Source EXPENSE Content Last Name Content First Name s about Description Becomes Is about Amount Account ARTIST COMMITMENT Start Date Has Is responsible ARTIST Start Time for End Date Last Name End Time Signs First Name for Commitment CONTRACT Catego ARTIST ARTIST MANAGER PAYMENT Belongs to Start Date End Date APayment ID Last Name Terms Date First Name Amount Works for Is based on Requires EVENT Agreement ADMIN Takes place at Covers a Admin ID Event Description Date performance at Last Name Date Amount Creates First Name Time Terms Create CUSTOMER VENUE PAYMENT Covers C Payment ID Is based Name Date CUSTOMER INVOICE On Address Amount tom ID Organizes Name Invoice Nbr Makes Date Address Total

Explanation / Answer

Steps to convert ER diagram to data table:

1. Convert all the Entities in the diagram into tables.

Hence, there are total 16 tables.

a. EXPENSE b. NEWS ITEM c. PROSPECTIVE ARTIST d. RECOMMENDATION e. ARTIST f. ARTIST COMMITMENT g. CONTRACT h. ARTIST PAYMENT i. ADMIN j. ARTIST MANAGER k. AGREEMENT l. INVOICE m. CUSTOMER PAYMENT n. CUSTOMER o. VENUE p. EVENT

2. All single valued attributes of the entites will be converted to a column of the table

hence, a. Expense table column: EXPENSE ID(PK), Description, Amount, Account,

b. NEWS ITEM: NewsItem ID(PK), Souce, Content

c. PROSPECTIVE ARTIST :PArtistID(PK), Last name, first name

d. RECOMMENDATION: RecommendationID(PK), source,content

e. ARTIST : ArtistID{PK), Last name, First name

f. ARTIST COMMITMENT : ACommitmentID(PK), Start date, End Date, End Time, End Date, Commitment, Category

g. CONTRACT :ContractID(PK), Start Date, End Date, Terms

h. ARTIST PAYMENT : APaymentID(PK), Day, Payment

i. ADMIN : AdminID(PK), Last Name, First Name

j. ARTIST MANAGER :AManagerID(PK), Last Name, First Name

k. AGREEMENT : Agreement nbr(PK), Day, Amount, Terms

l. INVOICE : Invoice nbr(PK), Date, Total

m. CUSTOMER PAYMENT : CPaymentID(PK), Date, Amount

n. CUSTOMER : CustomerID(PK), Name, Address

o. VENUE : VenueID(PK), Name, Address

p. EVENT: EventID(PK), Event Description, Date, Time

3.Key attributes in the ER diagram becomes the Primary keys of the table(already declared).

4. Need to Declare the foreign key column, if applicable.(not required in this one).

5. Any multi-valued attributes will be converted into new table.(not required in this ER diagram)

6. Any composite attributes are merged into same table as different columns(not required).

7. Derived attributes can be ignored, since it can be calculated at any time. here,commitment can be calcculated by taking the difference of start date and end date. hence, we can ignore it.

Hence, all 16 tables are ready

Related Questions

Navigate

• Browse (All)
• Browse T
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.