System requirements
Functional:
- User Registration/Login: Users should be able to register and log into the system.
- Parking Spot Reservation: Users can reserve a parking spot in advance through the system.
- Parking Spot Allocation: The system allocates available parking spots based on vehicle type and user requests.
- Payment Processing: Users must be able to pay for their parking either via the app or at a kiosk.
- Notifications: Users receive alerts about their reservation status and reminders for parking expiration.
- Spot Availability Display: A real-time display of available parking spots and their statuses.
- Search Functionality: Users should be able to search for available spots based on location and vehicle type.
- Security Camera Access: Users (and security personnel) can view live feeds from security cameras in the parking lot.
Non-Functional:
- Scalability: The system should be able to handle an increasing number of users and vehicles seamlessly.
- Performance: The system must provide quick responses to user requests, such as spot reservations and searches.
- Accessibility: The application should be accessible to users with disabilities, following WCAG guidelines.
- Security: The system must protect user data and transactions with proper encryption and secure payment gateways.
- Reliability: The system should have high availability, meaning it should be operational and functional with minimal downtime.
- Usability: The user interface should be intuitive and easy to navigate for a diverse user group.
Capacity estimation
Estimate the scale of the system you are going to design...
API design
Define what APIs are expected from the system...
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?