The Paris $2024$ Games will be supported by $45,000$ volunteers. To ensure the smooth management of such a big volunteer team, the Organising Committee of the $2024$ Olympic Games decided to develop a volunteer management system. They hired you as the business database consultant. You will oversee modelling and creating a database. Other IT teams will create the websites and write all the computer programs for the management system. Many system components must be addressed in a large and complex project. Although many issues were identified, you only must design and create a database model as listed above. That will be your part in this large project. For your role, $($a$)$ You do not need to write computer programs to capture the data or address purchasing ticketing processes. Other project teams will do these. $($b$)$ You do not have to worry about the interaction between the computer programs and the database. You can assume that the other project teams will take care of it$.($c$)$ You can assume that you have agreed with the other project teams before designing the database model. $($d$)$ You do not have to worry about how the system will be implemented, whether it is on a mobile app or a desktop. Requirements For the project, you need to create a database for a volunteer management system. You can start by using the volunteers' charter as a guide: Paris $2024$ Organising Committee. $(2023).$ Paris $2024$ Volunteers Charter. Here are some examples you might want to consider, and there may be more for consideration when you conduct further research. Alternatively, if you have been a volunteer for the Olympics or Commonwealth Games, you can leverage your experience for the project. $$ There are many functions and duties a volunteer can do$.$ Thus, the system can be very complex. You must decide and limit the scope of your project. For example, your focus could be logistics$,$ helping the athletes move around, or focusing on a sporting event such as swimming in an arena. $$ As a guide, you should have eight to ten entities $($Note: one supertype$-$subtypes entity is counted as one$)$ to demonstrate your understanding of entity modelling. You can have more than ten entities if needed. $$ There are different volunteer functions, e$.$g$.,$ guide, language assistant, medical assistant, field recorder, etc. Some function requires a certificate. For example, the medical assistant needs to have a medical degree. Some functions have access authority to specific systems or files. For example, the field recorder can access the game points recording system. $$ A volunteer can be assigned to more than one function, depending on his$/$ her ability. However, to ensure work efficiency, he$/$she cannot take multiple functions simultaneously. $$ Each Volunteer shall give notice of his$/$her availability during the Games regarding the specific period during which he$/$she is offering to volunteer. $$ There is a maximum daily and weekly on$-$duty time. $$ Since the Olympic Games sites are all over Paris, the schedule should clearly indicate where the event occurs.

Step $2$: Create an Entity Relationship Model $($ERM$)$

Create a suitable entity$-$relationship $($ER$)$ model for the above scenario. Firstly, you need to identify entities, relationships, keys, constraints, and cardinalities from the case study. Use Crow Foot$$s notation to draw the ER model based on what you have identified. Clearly label entities, relationships, cardinalities, and connectivities in your model. The clarity and readability of your diagrams are critical.

Next, review your diagram to justify whether the entities are correctly identified and if the relationships between the entities and keys are accurate. You can make reasonable assumptions that need to make sense in the context of the case study. Additionally, discuss any business or potential issues with the models.

The ER model must include:

At least one supertype$-$subtypes entity.

At least one header$-$detail entity.

Each entity must have at least four other attributes $($which can be $$standalone$$ foreign keys$)$ in addition to those attributes classified as primary keys.

You can outline reasonable assumptions when constructing the model. Avoid listing the obvious and refrain from justifying every primary key, foreign key, relationship, cardinality, and connectivity. Focus on discussing those aspects that you consider significant and worthy of mention.

Step $3$: Check for Normalisation

Check your relational model using normalisation and ensure that your model is at least in the Third Normal Form $(3$NF$).$ Verify that the model has no transitive and partial dependencies or multivalued attributes. Additionally, highlight any issues you might have encountered.

Step $4$: Check for denormalisation

Review if you need to denormalise your model in $($Step $3)$:

If yes $-$ you need to justify the reason for such an action, or you can modify your model as required.

If your answer is no$,$ you can skip this step.

Step $5$: Create a physical Relational Database $($Schema$)$