1. (2.5 points) Prepare an ERD based on the scenario. - Clearly show all other attributes of all the entities in the ERD If a scenario doesn't specify an identifier, make one for each entity. - Show all the cardinalities. - Please write down any assumptions you make. 2. (2.5 points) Convert the ERD you have drawn in section 1 into relational Schema. Indicate the primary key and foreign key in each table and show referential integrity constraints using arrows. You have been called upon to do some conceptual data modeling for the Purdue Summer Concert Series (PSCS). Purdue Summer Concert Series (PSCS) business scenario: - The concert season indicates the season when a series of concerts is performed. The attributes of concert season are seasonID and opening date. Season ID uniquely identify each concert season. - A concert is a performance that consists of one or more compositions. The primary key of concert is concert number, and an additional attribute is concert date. - The composition entity tracks the compositions to be performed at each concert. Information tracked on each composition includes compositionID (Primary Key), composer name (First name, Last name), and composition name. - Conductors conduct concerts. The PSCS tracks conductor names (First name, Last name) and conductor IDs. Conductor ID uniquely identifies each conductor. - Soloists perform compositions during concerts. The two attributes for soloists are soloist ID (Primary key) and soloist name (First name, Last name). - Each composition may need multiple soloists, or may not require any soloists. A soloist may perform multiple compositions, or may not perform any compositions. In each concert season, at least one or more concerts are scheduled. A particular concert is scheduled for only one concert season. For each concert there is one and only one conductor. A conductor may conduct many concerts, or may not conduct any at all. A concert includes the performance of one or more compositions. A composition may be performed at one or 1. (2.5 points) Prepare an ERD based on the scenario. - Clearly show all other attributes of all the entities in the ERD If a scenario doesn't specify an identifier, make one for each entity. - Show all the cardinalities. - Please write down any assumptions you make. 2. (2.5 points) Convert the ERD you have drawn in section 1 into relational Schema. Indicate the primary key and foreign key in each table and show referential integrity constraints using arrows. You have been called upon to do some conceptual data modeling for the Purdue Summer Concert Series (PSCS). Purdue Summer Concert Series (PSCS) business scenario: - The concert season indicates the season when a series of concerts is performed. The attributes of concert season are seasonID and opening date. Season ID uniquely identify each concert season. - A concert is a performance that consists of one or more compositions. The primary key of concert is concert number, and an additional attribute is concert date. - The composition entity tracks the compositions to be performed at each concert. Information tracked on each composition includes compositionID (Primary Key), composer name (First name, Last name), and composition name. - Conductors conduct concerts. The PSCS tracks conductor names (First name, Last name) and conductor IDs. Conductor ID uniquely identifies each conductor. - Soloists perform compositions during concerts. The two attributes for soloists are soloist ID (Primary key) and soloist name (First name, Last name). - Each composition may need multiple soloists, or may not require any soloists. A soloist may perform multiple compositions, or may not perform any compositions. In each concert season, at least one or more concerts are scheduled. A particular concert is scheduled for only one concert season. For each concert there is one and only one conductor. A conductor may conduct many concerts, or may not conduct any at all. A concert includes the performance of one or more compositions. A composition may be performed at one or