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

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


Main Objects of the system are:


Vehicle interface, it has 3 implementing classes bike, car, truck

vehicle has information like registration number


then we have a parkingspot interface with 3 implementations like small parking, medium parking, large parking, contains flag like occupied or free using boolean


We have a ticket interface that assigns a parking ticket on entry of vehicle containing timestamp, rate per hour etc


We have a parking class that has total number of floors, total number of parking per floor,


then we have a pricing strategy that takes parkingspot type to calculate pricing



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