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...

classDiagram

ParkingLot : +String name

ParkingLot : +String address

ParkingLot : +List<ParkingFloor> parkingFloors

ParkingLot : +List<Gate> gates

class ParkingLot{

+ParkingLotStatus status

+SpotAssignmentStratergy spotAssignmentStratergy

+FeeCalculationStratergy feeCaluclationStratergy

-Ticket parkVehicle(Vehicle vehicle,Gate entryGate)

-boolean isFull(VehicleType type)

}

class ParkingFloor{

+int id

+int floorNumber

+List<ParkingSpot> parkingSpots

-void markSpotOccupied(ParkingSpot parkingSpot)

-void markSpotAvailable(ParkingSpot parkingSpot)

}

class ParkingSpot{

-int id

-int spotNumber

-ParkingSpotType type

-ParkingSpotStatus status

-Vehicle parkedVehicle

-boolean canFitVehicle(Vehicle vehicle)

-void assignVehicle(Vehicle vehicle)

-void removeVehicle()

-boolean isAvailable()

}

class Vehicle{

+int id

+String vehicleNumber

+VehicleType type

+String ownerName

}

class Gate{

+int id

+int gateNumber

+Operator operator

+GateType type

}

class Operator{

+int id

+int empId

+String name

}

class Ticket{

+int id

+LocalDateTime entryTime

+Vehicle vehicle

+ParkingSpot spot

+Gate gate

+Operator issuedBy

+TicketStatus status

}

class Bill{

+int id

+LocalDateTime exitTime

+double amount

+Ticket ticket

+Gate exitGate

+Operator genratedBy

+List<Payment> payments

}

class Payment{

+int id

+double amount

+LocalDateTime time

+PaymentMode mode

+PaymentStatus status

+double refernceNumber

}

class SpotAssignmentStratergy{

<<interface>>

-Optional<ParkingSpot> assignSpot(List<ParkingFloor> floors,Vehicle vehicle)

}

class NearestSpotAssignmentStartergy{

-Optional<ParkingSpot> assignSpot(List<ParkingFloor> floors,Vehicle vehicle)

}

class FeeCalculationStartergy{

<<interface>>

-double calculateFee(Ticket ticket, LocalDateTime exitTime )

}

class HourlyFeeCalculationStrategy {

-double calculateFee(ParkingTicket ticket, LocalDateTime exitTime)

}

ParkingLot "1" o-- "*" ParkingFloor

ParkingFloor "1" o-- "*" ParkingSpot

ParkingLot "1" o--"*"Gate

Gate "1"--> "1" Operator

Ticket "1" --> "1" Vehicle

Ticket "1" --> "1"ParkingSpot

Ticket "1" --> "1"Gate

Bill "1" --> "1"Ticket

Bill "1"-->"*" Payment

ParkingLot --> SpotAssignmentStratergy

ParkingLot --> FeeCalculationStartergy

SpotAssignmentStratergy <|.. NearestSpotAssignmentStartergy

FeeCalculationStartergy <|.. HourlyFeeCalculationStrategy

The ParkingLot contains multiple ParkingFloor objects. It manages the overall parking facility and delegates the task of finding an available spot to the appropriate floor.

Each ParkingFloor contains multiple ParkingSpot objects. The floor finds and assigns an available spot to a vehicle based on its size.

A ParkingSpot is either occupied by a Vehicle or is vacant. When occupied, the spot stores a reference to the vehicle.

When a vehicle is parked, a Ticket is generated, recording the entry time, the assigned spot, and the vehicle. The ticket is used to calculate the parking fee.

Bill is generated using ticket and payment is made for the bill

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10