Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Ability to reserve parking spot in advance.
Payment with mobile app integration
See if parking row has free spots
send invoices after payment
financial record keeping
User registration is needed
Can do "drive-up parking" and pay on the spot
10% of spots are for ev with charging station
differrent pricing for car types
List non-functional requirements for the system...
Should always be able to pay
Should save the video footage for at least 6 months
durability
Estimate the scale of the system you are going to design...
This system will be used by a lot of parking lots.
Most of the client will leave after 2hours when movie ends so not a lot of events
about 200 parking spots per parking lot
Define what APIs are expected from the system...
Rest api. Main entities are user, spot, car.
So endpoints:
/users/signup
/users/authenticate
POST /lots/{id}/spots/{id}/reservation - reserve the spot
POST /lots/{id}/spots/{id}/pay - pay for the reservation
PATCH /lots/{id}/spots/{id}/reservation - update the reservation
GET /lots/{id} - return available spots and price
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...
An SQL database to store plate number, arrived time , left time and paid or no.
Also Store payment records for 6 months
Blob for video footage storing
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...
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...
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...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?