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.)...
- Thread Safety :- It should be handle in such way where one parking spot will be allotted to one vehicle in that particular time, or else it will go into a race condition.
- extensibility:- we can extend our parking lot in this way it support any kind of vehicle we can have , for that we should have that space so it handle bike, car , truck.
- maintainability:- our system should handle any kind of vehicle request at any time. and if space full it should make a waiting list showing space is full try again later.
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...
User{
id,
name,
email id,
phoneNo,
List
}
Vehicle{
id,
vehicleId,
vehicleName,
vehicleType,
userId,
}
Parking{
id,
parkingPlaceNo,
parkingPlaceType,
parkingStartTime,
parkingEndTime,
parkedVehicle,
}
ParkingPricing{
id,
transactionId,
parkingPlaceNo,
parkingPrice,
transactionType
}
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...