Core Objects & Relationships

Based on the requirements and use cases, identify the main objects of the system and analyze how they interact and relate to each other...

Vehicle	id: UUID [PK]	vehicleType: ENUM (bike, car, truck etc)	licensePlate: STRING
ParkingSlot	id: UUID [PK]	slotType: ENUM (bike, car, truck etc)	isOccupied: BOOLEAN	floorNumber: INT
Floor	id: UUID [PK]	floorNumber: INT	slots: List<ParkingSlot>
Ticket	id: UUID [PK]	vehicleId: UUID [FK → Vehicle.id]	slotId: UUID [FK → ParkingSlot.id]	entryTime: TIMESTAMP	isActive: BOOLEAN
Receipt	id: UUID [PK]	ticketId: UUID [FK → Ticket.id]	exitTime: TIMESTAMP	totalFee: Double	paymentStatus: ENUM (Pending, Failed, Success)
PricingRule	id: UUID [PK]	vehicleType: ENUM (BIKE, CAR, TRUCK, etc)	flatRate: DOUBLE	hourlyRate: DOUBLE	ruleType: ENUM (HOURLY, FLAT)
Payment	id: UUID [PK]	ticketId: UUID [FK → Ticket.id]	amount: DOUBLE	gateway: ENUM (STRIPE, PAYU etc)	status: ENUM (PENDING, SUCCESS, FAILURE)

DTO’s
EntryResult	success: boolean	ticket: Ticket (if successful)	message: String
ExitResult	success: boolean	recipt: Receipt (if successful)	message: String