Requirements

Functional Requirements:

• Assign parking spots based on vehicle size, allowing motorcycles to park in small spots, cars in medium spots, and trucks in large spots, with the option to park in larger spots if needed.
• Issue a ParkingTicket upon vehicle entry, which records the vehicle information, assigned parking spot, and entry timestamp.
• Compute the parking fee upon vehicle exit based on the duration of stay and a configurable pricing strategy.
• Handle scenarios where the parking lot is full by rejecting entry and displaying a lot-full indicator to the driver.
• Support multiple floors in the parking lot, with each floor containing a mix of small, medium, and large parking spots.

Non-Functional Requirements:

• List the key non-functional requirements (eg thread safety, extensibility, maintainability, etc.)...

Core Objects & Relationships

Vehicle can be a base interface, which can be extended to Bike, Car and Truck.

ParkingSpot can be a class which defines the size of the spot and also defines if the spot is avaialable.

Floor can be a class. Floor will have a list of parking spots.

ParkingLot can be a class. ParkingLot will have a list of floors, and list of tickets.

ParkingTicket can be a class. It will contain information about the spot, the vehicle type and the time of parking.

We can have another interface PricingStrategy. We can extend this for different pricing algorithms for bike, car and truck.

Parking ticket will have reference for this interface and while we create any ticket instance, we can pass the concrete pricing strategy reference.

APIs & Class Members

For each class, define the attributes (data) it will hold and the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation. Write your code in the code editor below.

Deep Dive

Explain design tradeoffs you considered. Check and explain whether your design adheres to SOLID principles. Explain how your design can handle changes in scale and whether it would be easy to extend with new functionalities. Identify areas for future improvement...

Future improvement:

1. We can add implementation to handle concurrency.

Trade-offs:

1. We can consider adding floor as an int in Spot class itself. By doing this we don't need a separate class for floors. But having a separate floor class will make us have floor level attributes as well if required in future.