DRAW AN AUTHORIZATION MATRIX FOR THIS:

Lets analyse each entity closely. CONDUCTOR: Its a simple table with ID and name CONDUCTOR: Conductor_ID, Conductor_Name CONCERT SEASON: Lets give it an addition field ID or you may also use Season Open date as foreign key in other tables but for simplicity I would recomment having a new numeric autoincrement field Id CONCERT SEASON : Concert_Season_ID, Season_Open_date (unique) CONCERT: Here come entity with one-to many relationship that you are having difficulty in mapping. I will explain this in detail. Step 1 : First lets consider concert as single concert Number. Step 2 : Mapping with Conductor : Every concert have one and only one conductor. Hence we can add a foreign key of conductor in table concert. Step 3 : Mapping with Concert Season : Notice every concert have one and only one concert season, hence we can add foreign key of table concert season in table concert. Hence table becomes : CONCERT : CONCERT_NUMBER, CONDUCTOR_ID (fk), CONCERT_SEASON_ID (fk) Step 4 : Adding additional concert attributes. Notice there are many concert dates for a single concert number. If we add this column in concert table, it will require repeting concert number, conductor id, concert season id for every date. Hence we should create a separate table for storing this value. CONCERT_DATETIME : CONCERT_NUMBER(fk), CONCERT_DATETIME Note : a date time type field stores all required atomic values date, time, year, month. day SOLOIST : Its a simple table with Id and Name SOLOIST: Soloist_ID(pk), Soloist_Name, Date_Last_Performed COMPOSITION: i) Has a composite key comprising of Composer Name and Composition Name => Composition ID ii) Have multivalued Movement ID comprising of Movement Name, Movement Number. If we create a single table for all these attributes, it will lead to repitition of Composer Name and Composition Name for every Movement ID, and Movement Name, Movement Number for every Movement Id Hence we can create a separate tables for COMPOSITION and MOVEMENT and map them in separate tables via their foreign keys. COMPOSITION : Composition_ID(pk), Composer_Name,Composition_Name MOVEMENT : Movement_ID(pk), Movement_Number, Movement_Name COMPOSITION_MOVEMENT : COMPOSITION_MOVEMENT_ID (pk) , Composition_ID (fk), Movement_ID (fk) We have additionally added a pk so that we can use it in referencing table. This can be an autoincrement numeric field. PERFORMANCE: Performance is nothing but a combination of In which concert Which Soloist performed Which composition. Hence we can create a table containing foreign key of all these tables, with probably an additional autoincrement ID column PERFORMANCE : PERFORMANCE_ID, CONCERT_NUMBER (fk), SOLOIST_ID (fk), COMPOSITION_MOVEMENT_ID (fk) Please add in a comment if you want more details about any of the table mapping.

\begin{tabular}{|l|} \hline CONCERT SEASON \\ \hline Season Open Date \\ \hline (Year, Month, Day) \\ \hline \end{tabular} \begin{tabular}{|l|l|} \hline Soloist ID \\ \hline Soloist Name \end{tabular}