Requirements
- Search available spot by vehicle size
- Assign spot to vehicle
- Compute fee
Define Core Objects
- VehicleSize:
- Name: enum
- Vehicle
- licencePlate: string
- size: VehicleSize
- ParkingSpot
- ID: int
- MaxSize : VehicleSize
- occupied: boolean
- Parking
- { floor: int, parkingSpot: ParkingSpot }[]
- Reservation
- ParkingSpot
- Vehicle
- startDate: Date
- state: ReservationState
- endDate: Date
- ReservationState
- name: string
Analyze Relationships
Establish Hierarchy
Design inheritance trees where applicable to promote code reuse and polymorphism. This step involves identifying common attributes and behaviors that can be abstracted into parent classes...
Design Patterns
Consider using design patterns (e.g., Factory, Singleton, Observer, Strategy) that fit the problem...
Define Class Members (write code)
Attributes: For each class, define the attributes (data) it will hold...
Methods: Define the methods (functions) that operate on the attributes. Ensure they align with the object's responsibilities and adhere to the principle of encapsulation.
public class ReservationSystem {
reserveParkingSpot(Vehicle v):ParkingSpot || Error
isParkingSpotAvailable(VehicleSize vs):Boolean
computeFee(ParkingSpot ps):Float
freeParkingSlot(ParkingSlot ps):Boolean
}
Adhere to SOLID Guidelines
Check and explain whether your design adheres to solid principles (Ask interviewer what SOLID principle is if you can not recall it.)...
Consider Scalability and Flexibility
Explain how your design can handle changes in scale and whether it would be easily to extend with new functionalities...
Create/Explain your diagram(s)
Try creating a class, flow, state and/or sequence diagram using the diagramming tool. Mermaid flow diagrams can be used to represent system use cases. You can ask the interviewer bot to create a starter diagram if unfamiliar with the tool. Briefly explain your diagrams if necessary...
Future improvements
Critically examine your design for any flaws or areas for future improvement...