System requirements

Functional:

List functional requirements for the system (Ask the chat bot for hints if stuck.)...

• allow users to park close to their destination
• maximize cars parked in a given space
• maximize revenue from parked cars
• minimize security incidents
• minimize traffic encountered during entry / exit

Non-Functional:

List non-functional requirements for the system...

• very high availability
• reasonably fast throughput
  • should handle bursts (e.g. arena event ends and everyone wants to leave)

Capacity estimation

Estimate the scale of the system you are going to design...

100s of cars. In general would estimate single digit cars moving in or out every minute during the daytime, let's say 10 * 10 hours = 100 cars / day moving

API design

Define what APIs are expected from the system...

getEntryTicket - stores the ID with a timestamp. Might also gather license plate from a photo, size of the vehicle from a photo, or weight of vehicle from a scale

chargeExit - based on ID and associated timestamp, charge a user

nextAvailableSpot - give the next most convenient spots that are available, helps direct users. Could intake data from a scale or image processing or user-inputted destination to inform the spot

Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...

Floor: id, floor_number

Space: id, floor_id, is_occupied, x_coordinate, y_coordinate

reservation: id, barcode, , entry_timestamp, , space_id

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?