TASK 1

Tradie mates, a distinguished Ute rental firm, seeks an advanced database system to efficiently oversee
their extensive Ute fleet. The system meticulously records Ute details, including type ID, make, model,
doors, body, trim, fleet membership number, registration number, color, and type ID. Client specifics
such as name, address, contact phone, and driver's license number are documented with a unique client
identifier, allowing only registered clients to hire vehicles. The company maintains a list of pick-up
depots, each with a unique depot ID, address, and up to four phone numbers, along with real-time
tracking of available Utes.

To enhance operations, Tradie mates can introduce a vehicle tracking system aligned with (S2), utilizing
GPS technology. This system introduces a Tracking entity with attributes like Tracking_ID,
Fleet_Membership_Number, Latitude, Longitude, and Date_Time, ensuring security and efficient fleet
management. Additionally, a Rental Insurance entity (S12) can offer optional coverage for hired Utes.
This entity includes Insurance_ID, Contract_ID (Foreign Key), Coverage_Type, and Insurance_Cost.
Simultaneously, a Maintenance entity (D) is proposed for streamlined procedures, featuring
Maintenance_ID, Fleet_Membership_Number (Foreign Key), Maintenance_Date, and
Maintenance_Description.

These three entities seamlessly integrate with existing ones, addressing (S2), (N5), (D), and (S12)
parameters. The Tracking entity enhances security and transparency, Rental Insurance provides
customer options, and Maintenance ensures proactive fleet management. This comprehensive system
positions Tradie mates at the forefront, offering advanced features for customer satisfaction, security,
and operational efficiency. The integration reflects a holistic approach to Ute rental management,
ensuring Tradie mates' continued success in the competitive market.

TASK 3

1. Tracking Relation

Tracking (TrackingID, FleetMembershipNo, Latitude, Longitude, DateTime)

PRIMARY KEY (TrackingID)

FOREIGN KEY (FleetMembershipNo) REFERENCES Ute(FleetMembershipNo) ON DELETE NO ACTION ON

UPDATE CASCADE

Justification

- `TrackingID` is selected as the primary key for the Tracking relation.

 - `FleetMembershipNo` is a foreign key referencing the Ute relation, establishing a connection
between tracking information and specific Utes.
- ON UPDATE CASCADE is chosen to maintain referential integrity when updating Ute primary
keys. DELETE NO ACTION is selected to prevent accidental deletion of Ute records.

2.

Rental Insurance Relation

Rental_Insurance (InsuranceID, ContractID, CoverageType, InsuranceCost)

PRIMARY KEY (InsuranceID)

FOREIGN KEY (ContractID) REFERENCES Contract(ContractID) ON DELETE NO ACTION ON UPDATE

CASCADE

Justification

- `InsuranceID` is set as the primary key for the Rental Insurance relation.
- `ContractID` is a foreign key linking rental insurance to specific contracts.
- ON UPDATE CASCADE is chosen for the foreign key to maintain referential integrity when
updating Contract primary keys. DELETE NO ACTION is selected to prevent accidental deletion of
Contract records.

3.

Maintenance Relation

Maintenance (MaintenanceID, FleetMembershipNo, MaintenanceDate, MaintenanceType,

ServiceProvider)

PRIMARY KEY (MaintenanceID)

FOREIGN KEY (FleetMembershipNo) REFERENCES Ute(FleetMembershipNo) ON DELETE NO ACTION ON

UPDATE CASCADE

Justification

- `MaintenanceID` is designated as the primary key for the Maintenance relation.

- `FleetMembershipNo` serves as a foreign key, linking maintenance records to specific Utes.
- ON UPDATE CASCADE is chosen for the foreign key to maintain referential integrity when
updating Ute primary keys. DELETE NO ACTION is selected to prevent accidental deletion of Ute
records.