Requirements

Functional Requirements:

1. Manage vehicle entry and exit through parking gates.
2. Generate a unique parking ticket for each vehicle.
3. Identify the vehicle type and assign a suitable parking spot.
4. Track parking spots as available, occupied, reserved, or unavailable.
5. Support multiple floors, parking zones, and entry/exit gates.
6. Provide real-time parking availability by floor, zone, and vehicle type.
7. Record vehicle entry time, exit time, parking spot, and ticket details.
8. Calculate parking fees based on duration, vehicle type, and configurable pricing rules.
9. Support multiple payment methods such as cash, card, and digital payment.
10. Validate tickets and payments before allowing vehicle exit.
11. Release the parking spot after the vehicle exits.
12. Support parking spot reservations and prevent conflicts with existing reservations.
13. Allow administrators to add, remove, and manage parking spots and floors.
14. Allow administrators to configure parking rates and pricing rules.
15. Maintain parking, ticket, reservation, and payment records.
16. Provide occupancy and parking reports for administrators.

Non-Functional Requirements:

1. Availability – The system should be highly available, especially during peak parking hours.
2. Performance – Parking spot availability, ticket generation, and fee calculation should respond within a few seconds.
3. Scalability – The system should support increasing numbers of vehicles, parking spots, floors, and locations.
4. Reliability – The system should accurately track parking spots, tickets, vehicles, and payments without data loss.
5. Consistency – A parking spot should not be assigned to multiple vehicles at the same time.
6. Security – User, vehicle, ticket, and payment information should be protected from unauthorized access.
7. Fault Tolerance – The system should continue operating when individual components such as a parking gate, server, or database instance fails.
8. Data Durability – Parking and payment records should not be lost in case of system or hardware failures.
9. Maintainability – The system should be modular and easy to update, debug, and maintain.
10. Observability – The system should provide logs, metrics, monitoring, and alerts for failures, traffic, occupancy, and payment issues.
11. Disaster Recovery – The system should support backups and recovery mechanisms in case of major system failures.
12. Concurrency – The system should correctly handle multiple vehicles entering, exiting, or requesting parking spots simultaneously.
13. Extensibility – The system should allow new vehicle types, payment methods, pricing rules, and parking features to be added easily.
14. Usability – The system should provide a simple and intuitive experience for drivers, parking staff, and administrators.
15. Auditability – Important operations such as ticket creation, spot assignment, payment, and vehicle exit should be recorded for auditing and troubleshooting.

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10