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

Abstract Vehicle Class. Bike, Car and Truck inherit from the Vehicle class. The Vehicle class will have common properties like vehicleNumber, make, colour, etc. Each specialised class sets the vehicleType during instantiation.

The ParkingSlotSize and VehicleSize enum signifies the size of the parking slot (small, medium and large) and Vehicle

The ParkingSlot class represents the attributes and methods owned by the slot where cars would be parked. This class would provide methods like assignVehicle() and removeVehicle(). This class will also maintain a property or provide a method to signify if the slot is occupied or not.

The ParkingTicket class contains the in and out times. This will also have a reference to the parking spot and vehicle to which the parking ticket is issued.

ParkingController

For FareCalculation, I would follow the strategy pattern to define multiple fee calculation strategies (time-based calculation, monthly pass, staff parking, peak-time parking, weekend parking, holiday parking etc.)

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