System requirements


Functional:

  • handle online reservations
    • keep track of info (license plate, reservation time (start/end), parking spot id, vehicle size, handicap)
  • handle walk-in
    • maybe pre-emptively shoo the car away if no spots available
    • license plate, reservation time, parking spot id, vehicle size, handicap
  • two vehicles can't occupy the same spot
  • vehicle size is also a factor
    • smaller cars can fit into larger spots, only if all spots of the same size are occupied
  • handicap are hard-reserved for handicap vehicles
  • payment after reserve
  • multiple garages: garage_id


Non-Functional:


Capacity estimation

  • prob not very big
  • 10-floor * 200 spots * 5000 parking lots max




API design


/reserve:

  • input:
    • string: license_plate
    • string: start_time, end_time
    • string: vehicle_size
    • boolean?: handicap
    • int: garage_id
  • return:
    • parkiing_spot_id


/parking_spot_allocation:

  • input:
    • vehicle_size
    • handicap
    • start_time, end_time
  • return:
    • parking_spot_id



/free_spots:

  • input:
    • vehicle_size
    • handicap
    • start_time, end_time
  • return:
    • Array<int> parking_spot_id


/create_account:

  • input:
    • email
    • password
    • name


/login:

  • input:
    • email
    • password


/add_vehicle:

  • license_plate
  • vehicle_type
  • handicap


Database design


vehicle:

  • id, primary_key: serial
  • license_plate: varchar
  • vehicle_type: enum
  • handicap: boolean

parking_spots:

  • id, primary_key: serial
  • vehicle_type: enum
  • occupied: boolean
  • handicap: boolean

garage:

  • id, primary_key: serial
  • postal_code: varchar
  • rate: decimal


users:

  • email: varchar
  • password: varchar
  • name: string
  • vehicle_id, foreign_key: int


High-level design

You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...







Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...






Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...






Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...






Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.






Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?