The Music For All would like to design a database to support the informational requirement of their Orchestra. Music For All contracted with GreenIT services to design the database. GreenIT services conducted series of interviews with the management of Music For All to extract information about the operations of the Orchestra. Finally, they identified following requirements. User view 1 requirement: The database should have information about the SEASONS (during which season) the concert will be performed. The Seasons are identified by a text field called SeasonID. Organisers also want to know the number of advance tickets sold, total number of tickets sold and total incomes and expenses for each season. User view 2 requirements: Each concert is identified by a concert_Number. The concert number represents the place of the concerts within the season in a chronological order. User view 3 requirements: A concert season schedules one or more concerts. A particular concert is scheduled for only one season. User view 4 requirements: Another important feature of a concert is, PERFORMANCE, which consists of a performance date, performance time. Each concert typically has more than one performance. Organizers also want to record whether it is a paid attendance (for a given performance) or not. User view 5 requirements: Musical COMPOSITIONS or musical work such as a Beethoven Symphony or Rossini Overture to be performed at each CONCERT. A concert includes one or more musical compositions. A composition may be performed at one or more concerts, or may not be performed. User view 6 requirements: The identifier for a musical composition is a Composition_ID. For each Composition, Composition_Name, Composer_ID and Composer_Name will be recorded. User view 7 requirements: For each concert performance there is one CONDUCTOR, who will conduct the concert. The identifier is Conductor_ID. Another attribute is Conductor_Name. A conductor may conduct any number of concerts performances, or may not conduct any concerts. Complete the information-level design for the new database for Music For All that satisfies the constraints and user view requirements given above. In order to complete the information-level design you are required to answer questions given below 1(a) (e) a. Identify and list entities described in all user requirements given above. b. Add attributes to those entities and represent them as a collection of tables and attributes as given below. Eg. CONCERT (ConcertID, Concert_name,. NB: Select suitable primary key for each table and underline them. c. Outline at least 2 relationships between those entities. Eg. A concert season schedules one or more concerts. - One-to-many, 2. ER Diagram Represent the structure of your database visually by using the entity-relationship (ER) diagram. If you make any assumptions about data that are not explicitly given in the problem, these must be described. NB: You can use Visio, draw.io [1] or Lucidchart [2] or any other software tool to create the ER diagram.