$2\mathrm{.}2.$ The tables illustrated below$-$WASH$\_$INV$\_$GENERATOR$\_$STUDENT NUMBER,

CARWASH$\_$SERVICE$\_$STUDENT NUMBER, INVOICE$\_$STUDENT NUMBER, and

VEHICLE$\_$REG$\_$STUDENT NUMBER $-$ are based on the shopping mall's car cleaning service.

Note the following: although the car cleaning service exists, patrons are not required to use

it$.$ Conversely, some patrons regularly make use of the cleaning service.

Database name: TMSC$\_$SHOPPING

Table name: INV$\_$GENERATOR$\_$STUDENT NUMBER

Primarykey: Irw$\_$number $+$ Line$\_$number

Forelgn key: Inv$\_$number, Service$\_$code

Table name: CLEANING$\_$SERVICE$\_$STUDENT NUMBER

Primary key: Service$\_$code

Foreign key, none

Table name: VEHICLE$\_$REG$\_$STUDENTNUMBER

Primary key: Vehicle$\_$reg

Foreigr key: none

$2\mathrm{.}2\mathrm{.}1.$ Mariaan De Wet, the database designer with more than $10$ years' experience in

database design, deployed the relational model $($see page $41$ Coronel et al$.,2020)$ to

conceptualise the tables. Sanjay instructs you to convert the tables into

corresponding business rules for documentation purposes.

Examine each table's attributes, records, primary key allocation, and foreign key

allocation. Formulate the business rules that underpin the relationships between

the tables.

$(34)=(12)$