Database Name: BusTrackCentralDB

Entities and Attributes:

BusCompany

CompanyID (Primary Key)

CompanyName

RegistrationNumber

Bus

BusID (Primary Key)

CompanyID (Foreign Key)

RegistrationNumber

Route

GPSLatitude

GPSLongitude

LastUpdatedTime

Driver

DriverID (Primary Key)

Name

LicenseNumber

BusID (Foreign Key)

Passenger

PassengerID (Primary Key)

Name

Origin

Destination
Schedule

PaymentInfo

Booking

BookingID (Primary Key)

PassengerID (Foreign Key)

BusID (Foreign Key)

BookingDateTime

Journey

JourneyID (Primary Key)

BusID (Foreign Key)

DriverID (Foreign Key)

JourneyDateTime

JourneyStatus (e.g., ongoing, completed)

Latra

LatraID (Primary Key)

ReportID

ActionTaken

Remarks

Date

Relationships:

One BusCompany can have Many Buses (One-to-Many relationship)

One Bus can have Many Bookings (One-to-Many relationship)

One Driver can drive Many Buses (One-to-Many relationship)

One Bus can have Many Journeys (One-to-Many relationship)

One Passenger can make Many Bookings (One-to-Many relationship)

One BusCompany can have Many Reports (One-to-Many relationship)

Connections:

BusCompany (1) -----< (Many) Bus

BusCompany (1) -----< (Many) Reports

Bus (1) -----< (Many) Bookings

Bus (1) -----< (Many) Journeys

Driver (1) -----< (Many) Buses

Booking (1) -----< (Many) Passengers

Summary:

 You can use above table to draw the useCase and class Based Diagram

The BusTrackCentralDB database is designed to serve as a centralized system for the Unified Latra Bus
Booking and Tracking System. It allows for efficient management of bus companies, drivers, passengers,
bookings, journeys, and oversight by Latra. The database schema ensures data integrity and supports
various relationships between entities, enabling smooth operations and regulatory support.