Create a logical data model documented with an ERD using the crow’s foot format. Be sure that each entity has the entity name at the top of the box, the primary key attribute or attributes in the middle of the box, and the non-key attributes in the bottom of the box. Lines should separate each part of the entity box. Follow these instructions about each ERD: ● The ERD must not have any many-to-many (m:n) relationships.● All attributes must be placed within an entity.● Each entity must have a primary key defined. A primary key can consist of one or more attributes.● Each relationship must have a foreign key. Denote the foreign key(s) with the notation (FK) on the ERD. Remember that in a one-to-many relationship, the foreign key is placed in the entity that is on the many side of the relationship.● Each relationship must include both a maximum and minimum cardinality for both sides of the relationship.● Each relationship should have a verb or verb phrase to describe it.Question: Application Scenario: Create a database for a company that provides streaming content to customers (a company such as Netflix). While the customer delivery database for Netflix would be quite complex because it includes physical disks and inventory as well as streaming content, we are going to design just one small part of it – the customer streaming list. This database should keep track of the data required in the columns shown in the Excel workbook “MediaContentList.xlsx.” There are two worksheets in the workbook – the first (StreamingEvent) provides data about each streaming event, and the second (CustomerSubscription) gives an example of the changes that can occur in a customer’s subscription to the service. The attributes in both worksheets should be included on your data model. Sample data values are provided in the Excel workbook to help you understand what needs to be stored for this application. The number of columns in the sample data is small to limit the complexity of the design. Here is some additional information about the application:• Each row in the StreamingEvent worksheet represents a single streaming event or a saved “favorite” content for a customer. • Each content title has its own ContentID. Each unique episode of a given type of content has its own ContentID.• The data values for the “status” of a video title in the list for a given customer can be as follows:Started: A content title has been started but not finished. The position is the number of minutes into the content title last viewed by the customer. Netflix keeps track only of the most recent last position for a content title for a customer.Favorite: A content title a customer intends to stream in the future. Netflix does not keep track of the date and time that a customer creates a favorite but does keep track of the declaration.Watched: A content title that has been streamed and watched is noted with this status. If a video has been streamed and watched, then the date it was watched is stored in the "date video returned" column. The database stores only the last time that a content title is watched.• Assume each content title has only one video category.• Assume there is a group of pre-defined video categories that must be stored in the database.• Customers can join, quit, and then re-join Netflix at will. Each time a customer joins, or re-joins, Netflix, the customer must indicate what type of subscription he/she wants. Netflix wants to keep track of the different times a customer joins/quits and then re-joins. Netflix offers a variety of different types of customer subscription. A type of subscription includes a subscription typeID, which is a unique value for the type of subscription and a description of the type of subscription. A customer can be of only one customer subscription type at a given point in time. A customer subscription type could be related to many customers. Even though we are keeping track of only streaming content in this scenario, we are going to keep track of the different types of subscription for a given customer over time. Please refer to the CustomerSubscription worksheet for sample data values. (it does not allow m to upload the excel file. My hope is you will have it)

Question

Create a logical data model documented with an ERD using the crow’s foot format. Be sure that each entity has the entity name at the top of the box, the primary key attribute or attributes in the middle of the box, and the non-key attributes in the bottom of the box. Lines should separate each part of the entity box. Follow these instructions about each ERD: ● The ERD must not have any many-to-many (m:n) relationships.● All attributes must be placed within an entity.● Each entity must have a primary key defined. A primary key can consist of one or more attributes.● Each relationship must have a foreign key. Denote the foreign key(s) with the notation (FK) on the ERD. Remember that in a one-to-many relationship, the foreign key is placed in the entity that is on the many side of the relationship.● Each relationship must include both a maximum and minimum cardinality for both sides of the relationship.● Each relationship should have a verb or verb phrase to describe it.Question: Application Scenario: Create a database for a company that provides streaming content to customers (a company such as Netflix). While the customer delivery database for Netflix would be quite complex because it includes physical disks and inventory as well as streaming content, we are going to design just one small part of it – the customer streaming list. This database should keep track of the data required in the columns shown in the Excel workbook “MediaContentList.xlsx.” There are two worksheets in the workbook – the first (StreamingEvent) provides data about each streaming event, and the second (CustomerSubscription) gives an example of the changes that can occur in a customer’s subscription to the service. The attributes in both worksheets should be included on your data model. Sample data values are provided in the Excel workbook to help you understand what needs to be stored for this application. The number of columns in the sample data is small to limit the complexity of the design. Here is some additional information about the application:• Each row in the StreamingEvent worksheet represents a single streaming event or a saved “favorite” content for a customer. • Each content title has its own ContentID. Each unique episode of a given type of content has its own ContentID.• The data values for the “status” of a video title in the list for a given customer can be as follows:Started: A content title has been started but not finished. The position is the number of minutes into the content title last viewed by the customer. Netflix keeps track only of the most recent last position for a content title for a customer.Favorite: A content title a customer intends to stream in the future. Netflix does not keep track of the date and time that a customer creates a favorite but does keep track of the declaration.Watched: A content title that has been streamed and watched is noted with this status. If a video has been streamed and watched, then the date it was watched is stored in the &#34;date video returned&#34; column. The database stores only the last time that a content title is watched.• Assume each content title has only one video category.• Assume there is a group of pre-defined video categories that must be stored in the database.• Customers can join, quit, and then re-join Netflix at will. Each time a customer joins, or re-joins, Netflix, the customer must indicate what type of subscription he/she wants. Netflix wants to keep track of the different times a customer joins/quits and then re-joins. Netflix offers a variety of different types of customer subscription. A type of subscription includes a subscription typeID, which is a unique value for the type of subscription and a description of the type of subscription. A customer can be of only one customer subscription type at a given point in time. A customer subscription type could be related to many customers. Even though we are keeping track of only streaming content in this scenario, we are going to keep track of the different types of subscription for a given customer over time. Please refer to the CustomerSubscription worksheet for sample data values. (it does not allow m to upload the excel file. My hope is you will have it)

Accepted Answer

Answer:
The below is the answer:
ER diagram: