bus 1
bus 1
Abstract
This system aims to facilitate the process of booking
tickets through the website.
It allows customers to create accounts, log in, and
perform operations such as booking tickets, viewing
reserved tickets, and canceling them when needed.
Each interaction with the system requires the
customer to enter their personal details and verify the
flight information before confirming the reservation.
2. Verification Manager
- 5-Check Booked Tickets: The system must allow the verification manager to
check and verify the details of booked tickets.
3. Admin
- 6-Login Personal Details: The system must require the admin to log in with
personal details for access.
- 7-Verify Traveling Details: The system must allow the admin to verify the
traveling details provided by customers.
4. Accountant
- 8-Ticket Price: The system must provide the accountant with the ability to view
and manage ticket prices.
- 9-Wallet: The system must provide the accountant with features related to the
wallet, such as managing transactions and balances. The "Ticket Price" use case
extends to the "Wallet" use case.
Non-Functional Requirements
1.Performance:
- The system must be capable of handling a high number of user requests simultaneously
without performance degradation.
2.Scalability:
- The system must be easily scalable to handle an increasing number of users and data over
time.
3.Security:
- The system must protect user data and sensitive information from unauthorized access.
4.Maintainability:
- The system must be designed for easy maintenance and updates without disrupting
service.
5.Usability:
- The system must be user-friendly and provide a seamless and intuitive user experience.
- The user interface should be designed to be understandable and accessible to all users.
6. Reliability*:
- The system must be reliable and have a high availability (99.9% uptime).
7. Compatibility: