0% found this document useful (0 votes)
6 views

bus 1

Uploaded by

tito.hema42
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views

bus 1

Uploaded by

tito.hema42
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Bus reseration system

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.

The system provides users with overall operations


management, while the verification manager verifies
the validity of tickets to ensure that approved tickets
are correct. Accountants process ticket prices and
conduct financial operations
Requirements Analysis
- Functional Requirements
1. Customer
- 1-Check Ticket: The system must allow customers to check the availability and
details of tickets.
- 2-Book Tickets: The system must enable customers to book tickets. This
includes entering personal details and verifying traveling details.
- 3-View Tickets: The system must allow customers to view their booked tickets.
This also includes entering personal details and verifying traveling details.
- 4-Cancel Tickets: The system must provide customers with the ability to cancel
their booked tickets. This includes entering persona details and verifying traveling
details.-

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.

- The system must respond to user requests within 2 seconds or less.

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.

- Strong security measures such as encryption and two-factor authentication must be in


place.

4.Maintainability:

- The system must be designed for easy maintenance and updates without disrupting
service.

- The code should be well-organized and clear, with appropriate documentation.

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:

- The system must be compatible with various browsers and devices.


Use Case Diagram

You might also like