After completing the logical design phase, the database team transitioned to the physical database

design phase. This phase entails defining specific storage or access methods for the database. To

achieve this, the team translates the logical model into a set of DBMS specifications for storing and

accessing data. The database administrator utilizes SQL to create database and table structures,

perform data manipulation and administration tasks, and execute queries to extract useful

information. In this project, the database team adopted the agile scrum strategy $($Vijay$,2024),$ with

two database administrators $($yourself and Clarence Tshwete$),$ Mariaan De Wet as the database

designer, and Lindiwe Bhegu as the data scientist. Sunjay serves as the scrum master. Your primary

task for day $1$ of the sprint is to verify referential integrity by ensuring the correct primary keys and

foreign keys are in place. This involves enforcing referential integrity to prevent deletion of related

records until all associated data has been removed. For example, in a scenario where one table

contains information about each TMSC shopping centre and another table shows two Heads of

Maintenance $($HOMs$)$ working at each shopping centre, referential integrity would prevent deletion of

shopping centre information until all associated HOM records are deleted. A more illustrative

example of referential integrity is provided by Coronel et al$.(2020,$ pp$.601-602)$ in their explanation

of the $\text{'}$DVD$\text{'}$ and 'COPY' relation. In this scenario, a movie in the DVD relation should not be deleted

until all copies in the COPY relation have been removed. At the end of the sprint, you are expected to

produce an Entity$-$Relationship Diagram $($ERD$)$ to visually illustrate referential integrity. Clarence will

focus on checking and validating integrity constraints of domain datatypes and is expected to

produce a data dictionary that includes these constraints. Based on the focus area of each assigned

task, your sprint does not involve validating and checking integrity constraints. Therefore, the

forthcoming instructions specify 'VARCHAR$(2)\text{'}$ as a 'generic' datatype. Perform the actions below in

the ASS$2\_$STUDENT$\_$NUMBER schema in SQL Developer.

$4\mathrm{.}1.$ You are presently engaged in creating a table to capture the information of the HOMs.

$4\mathrm{.}1\mathrm{.}1.$ Use the CREATE TABLE SQL statement to create a table named HOM$\_$STUDENT

NUMBER.

$4\mathrm{.}1\mathrm{.}2.$ Use the column parameter to specify attributes in the bulleted list below, assigning

the VARCHAR$(20)$ datatype to each attribute:

HOM$\_$ID

HOM$\_$Name

HOM$\_$Surname

HOM$\_$Contact

MALL$\_$ID

$4\mathrm{.}1\mathrm{.}3.$ Use the PRIMARY KEY constraint to identify HOM$\_$ID as the primary key. Name the

constraint PK$\_$HOM$\_$ID$.$