Step $1$: Read the Case Scenario.

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:

a$.$ At least one supertype$-$subtypes entity.

b$.$ 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$)$ in Oracle

Create a physical Relational Database $($Schema$)$ in Oracle, and you must address the following issues:

All supertypes and subtypes must be resolved and can be implemented within a relational database structure.

You can introduce a surrogate key but must justify your decision.

Most importantly, ensure that the keys and relationships are correctly identified.