3a) Draw an Entity-Relationship diagram by reverse engineering the two tables that were defined in Problem 1. Use the same diagram symbols that weve been using, like the ones in figure XXX. For the name of the Relationship, use Made_Recording. You can draw this freehand, or use PowerPoint or other software tool. Be sure to pay attention to stuff like the thickness of lines, underlining some items, etc. If you draw it freehand, you can scan it or take a photo with your phone. Paste your E-R diagram image in here:

3b) Embellish your E-R diagram by adding some Attributes to it. (Dont add any new entities.) Add at least two attributes to each of the two existing entities. They could be plausible, like Publisher or Record Label, or Genre, or perhaps whimsical. Indicate on the diagram that at least one attribute is a plausible Key to its entity.

3c) Thought experiment: (Dont actually implement it as a diagram or in SQL.) Suppose you wanted to add a Publisher entity (or Record Label or something similar) to the two-table schema you already have with Artists and Recordings. Suppose that this new entity has a bunch of attributes of its own, like address, phone number, etc. Describe how you would add this table into your schema.

3d) In item (3c) above, why would it be a bad idea to just put that extra information (like publisher name, publisher address, etc.) as new columns in the Recordings table, rather than making publisher its own entity type and table? Explain:

3e) Now add 25 more attributes and 5 more entities to your diagram, define and create corresponding tables for each of the new entities

Table: Artists ArtistID ArtName Elvis Ham Kool Kardash Make up a name heremake up popu Joe Nothingburger ArtPopu 62 200 0 Table: Recordings RecordingID RecPopu RecName You Hound Dog, You You Named Me Be my Valentine I am so Kool RecArtlD 30 82.3 39 13