Design a VIT Ride Management System using UML$($class $)$diagram$.$

The system should allow administrators to manage users, drivers, and ride requests. The

application should include the following classes:

$1.$ User:

Design a class representing the user entity in the system. Include attributes such as user ID$,$ name,

contact information, and any other relevant information. Methods: Constructors, getters, and

setters. Methods for user$-$related functionalities $($e$.$g$.,$ registering, removing, displaying$).$

$2.$ Driver:

Design a class representing the driver entity.

Include attributes like driver ID$,$ name, license number, vehicle information, and availability

status. Methods: Constructors, getters, and setters. Methods for driver$-$related functionalities

$($e$.$g$.,$ registering, removing, displaying$).$

$3.$ Ride:

Design a class representing a ride request or allocation. Include attributes such as ride ID$,$ user

ID$,$ driver ID$,$ pickup location, destination, and status. Methods: Constructors, getters, and

setters, Methods for ride$-$related functionalities $($e$.$g$.,$ requesting, allocating, displaying$).$

$4.$RideManager:

Design a class to manage users, drivers, ongoing rides, and ride history. Include appropriate

methods for registering, removing, and displaying users and drivers.Include methods for ride

management, such as requesting rides, allocating drivers, and displaying ride history. Methods

for ride management $($e$.$g$.,$ requesting rides, allocating drivers, displaying ride history$).$

Page $|12$

Victorian Institute of Technology www$.$vit.edu.au CRICOS Provider No$.02044$E$,$ RTO No: $20829$

$5.$ Main:

Contains the main method for testing the functionalities. Creates an instance of the Ride

Manager class and provides a menu system to allow administrators to interact with the system.

Create Relationships:

User$-$Driver Relationship:

Define the relationship between the User and Driver classes to represent the association

between users and drivers.

Ride$-$User$-$Driver Relationship:

Establish relationships between the Ride, User, and Driver classes to represent the associations

between ride requests, users, and drivers. You may add some more relationships from your

understanding.

The classes should be designed using object$-$oriented principles such as inheritance,

encapsulation, and polymorphism. The application should allow to perform the following tasks:

$1.$ Register New Users:

Implement a method to register new users for the ride service, including details such as

name, student ID$,$ and contact information.

$2.$ Remove Users:

Implement a feature to remove users from the system based on their student ID$.$

$3.$ Display All Users:

Develop a method to display a list of all users registered for the ride service.

$4.$ Register New Drivers:

Implement a feature to register new drivers for the ride service, including details such as

name, driver's license number, and vehicle information.

$5.$ Remove Drivers:

Page $|13$

Victorian Institute of Technology www$.$vit.edu.au CRICOS Provider No$.02044$E$,$ RTO No: $20829$

Develop functionality to remove drivers from the system based on their driver's license

number.

$6.$ Display All Drivers:

Implement a method to display a list of all registered drivers available for rides.

$7.$ Request a Ride:

Design functionality that allows users to request a ride by providing their current

location and desired destination.

$8.$ Allocate Drivers to Rides:

Implement a method to allocate available drivers to ride requests based on factors such

as proximity and availability.

$9.$ Display Ongoing Rides:

Develop a feature to display a list of all ongoing rides, including details about the user,

driver, and current status.

$10.$ Display Ride History:

Implement functionality to display a list of all completed rides, including information

such as starting point, destination, and feedback.

give me Assumptions $/$ Constraints and Class Diagram?