Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Record each time when a vehicle enters/leaves the parking lot.
Being able to quickly identify empty slots when a new vehicle comes in.
Being able to quickly allocate empty slots when a new vehicle comes in.
The system should be able to prioritize convenience for the user.
The system should be safe.
List non-functional requirements for the system...
The system should have the up-time about 99.99 percent.
The system should encrypt private data such as license number.
The system should be available 24/7.
The response time should be within 2 seconds.
Estimate the scale of the system you are going to design...
Since we only have 200 users daily in average so we should not be too worried about scalability.
Define what APIs are expected from the system...
GET: users/login
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...
Since we are not too frequently updating the records, I think using SQL database is the best, since we can create relations between data and enhance data-integrity.
I think the users will need to register on the platform/website and we will need to record the user informations. For the vehicles, we should definitely record the license and type.
We also need to create a mapping between users and vehicles which is a one-to-many relationship because users can have multiple cars.
We will also have a parking lot table that reflects that currently which spot is used by which vehicle.
users:
key, email, phone,
vehicle:
license, type, color
parking lot:
Id, license
users-vehicle:
key, license
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?