Vehicle Rental Management System
Functional Requirements
1. User Management
• The system shall allow users to register using valid details.
• The system shall allow registered users to log in and log out securely.
• The system shall allow users to update their profile information.
• The system shall provide password recovery functionality.
2. Vehicle Management
• The system shall allow the admin to add new vehicle details.
• The system shall allow the admin to update existing vehicle information.
• The system shall allow the admin to remove vehicles from the system.
• The system shall display vehicle availability status.
3. Vehicle Search and Booking
• The system shall allow users to search vehicles based on type and availability.
• The system shall allow users to view detailed vehicle information.
• The system shall allow users to book vehicles for a selected date and time.
• The system shall prevent double booking of the same vehicle.
4. Payment Management
• The system shall calculate the total rental cost automatically.
• The system shall allow users to make online payments.
• The system shall generate payment receipts.
• The system shall store payment transaction details.
5. Booking Management
• The system shall allow users to view booking history.
• The system shall allow users to cancel bookings as per policy.
• The system shall update vehicle availability after booking or cancellation.
6. Admin Functions
• The system shall allow the admin to manage users.
• The system shall allow the admin to view all bookings.
• The system shall allow the admin to generate rental and revenue reports.
Non-Functional Requirements
1. Performance
• The system shall respond to user requests within acceptable time limits.
• The system shall support multiple users simultaneously.
2. Security
• The system shall ensure secure authentication and authorization.
• The system shall encrypt sensitive user and payment data.
3. Reliability
• The system shall be available 24/7 with minimal downtime.
• The system shall ensure data integrity during failures.
4. Usability
• The system shall provide a user-friendly interface.
• The system shall be easy to use for non-technical users.
5. Scalability
• The system shall support future expansion.
• The system shall handle increased workload efficiently.
6. Maintainability
• The system shall be easy to maintain and update.
• The system shall follow modular design principles.
7. Compatibility
• The system shall work across different devices and browsers.
ER - Diagram