System requirements


Functional:

  • Vehicle entry system to capture vehicle and user details.
  • Identify the vehicle that works with barrier - prevent unauthorized access, better user experience and security. This would help for entry and exit.
  • Payment processing system that takes credit card information. With option to store credit card info for future processing.
  • Parking assign system. This has information on existing parking, reservations/timing, space size etc.
  • Vehicle Tracking system. This also has info about reserved/empty spaces.



Non-Functional:

List non-functional requirements for the system...




Capacity estimation

  • 500 parking spaces.
  • 350 spaces being used 2 hours max and 150 long term parking
  • System being booked fully during day and 40% long term that gets parked overnight
  • Total number of bookings during day time: 350 * (12/2) = 2100 bookings.
  • Long term booking = 150





API design

Define what APIs are expected from the system...

  • Client Registration
  • Vehicle Registration
  • Payment System
  • AvailableParkingSpaces
  • ReserveParkingSpace
  • GateAccess




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




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?