BUS RESERVATION SYSTEM

Submitted by
M.Dhinakar babu-13mse1029
V.Kavinpradeep-13mse1046
Sudharsana Raja Murugan-
13mse1115
Existing System
 The work is done manually.
Those who are interested in inquiring about the Bus Type, its Tickets Price,
available seats, facility of the bus etc. has to walk to the Booking office.
This creates a huge Relief for the Customer of the Office on weekends to save
their time. A new system is helpful to both employees as well as the
customers.
New system provides help to the customer as they can inquire about the Bus
model, its Ticket price, available Seats, facility of the bus etc. and they dont
need to walk to the office.
There is login and password service for employee and Regular customers to
use this system .
Need for new system:
A new system is helpful to both employees as well as the customers.
New system provides help to the customer as they can inquire about the Bus
model, its Ticket price, available Seats, facility of the bus etc. and they dont
need to walk to the office.
There is login and password service for employee and Regular customers to
use this system .
 DATA DICTIONARY

In this project we handle Five databases through using the concept of Relational
database

First One is LOGIN Table: -

Field Name Storage Type Length

Constraint
Username varchar 25 primary key

Password varchar 20 -

Second is Hotel Booking Table: -

Field Name Storage Type Length

Constraint
Name varchar - -
E-mail varchar - -
Hotel varchar - -
Arrival_Date date - -
Departure_Date date - -
Number_guests integer 10 -
Adult integer 10 -
Rooms integer 10 -
Comments varchar 100 -

Third is ReservationTable: -

Field Name Storage Type Length Constraint

Ticket_no integer 10 primary key

Journey_date date - -
From_of varchar - -
To_of varchar - -
Bus_name varchar - -
Required_seats integer 8 -
Bus_no varchar - not null
Bus_fair integer 5 -
Total_amount integer 8 -
Name varchar - -
Age integer - -
Martial_status varchar - -
Sex varchar - -
Seat_no varchar - -
Address varchar 100 -
Street_no varchar - -
City_of varchar - -
State_of varchar - -
Country_of varchar - -
Pin_of integer 10 -
Phone_no integer 10 -
Email_of varchar - -

Fourth is Cancellation Table: -

Field Name Storage Type Length Constraint

Ticket_no integer 10 primary key
Journey_date date - -
From_of varchar - -
To_of varchar - -
Bus_name varchar - -
Bus_no varchar - not null
Name varchar - -
Age integer - -
Martial_status varchar - -
Sex varchar - -
Seat_no varchar - -
Address varchar 100 -
Street_no varchar - -
City_of varchar - -
State_of varchar - -
Country_of varchar - -
Pin_of integer 10 -
Phone_no integer 10 -
Email varchar - -

Fifth is Bus Entry Table: -

Field Name Storage Type Length Constraint

Bus_no varchar - not null
Bus_name varchar - -
Bus_fair integer 5 -
Destination varchar 100 -
Remarks varchar 100 -
TESTING

Testing is the activity where the errors remaining from all the
previous phases must be detected. Testing performs a very critical
role for ensuring quality. During testing, the software to be tested
is executed with a set of test cases, and the behaviour of the
system for the test cases is evaluated to determine if the system
is performing as expected.

UNIT TESTING

Unit testing is another approach for verifying the code that a programmer is
written. Unit testing is like regular testing where programs are executed with
some test cases expect that the focus is on testing smaller programs or modules
called units. A unit may be a function, a small collection or functions, a class, or a
small collection of classes. Most often, it is the unit a programmer is writing code
for, and hence unit testing is most often done by a programmer to test the code
that he or she has written. Testing, however is a general technique that can also
be used for validating complete systems.

Black-Box Testing
In black-box testing the structure of the program is not
considered. Test cases are decided solely on the basis of the
requirements or specifications of the program or module, and the
internals of the module or the program are not considered for
selection test cases. In black- box testing, the tester only knows
the inputs that can be given to the system and what output the
system should give. In other words, the basis for deciding test
cases in functional testing is the requirements or specifications of
the system or module. This form of testing is also called functional
or behavioral testing.

White-Box Testing

The black-box testing is concerned with functionality rather than implementation

of the program. White-box testing, on the other hand is concerned with testing
the implementation of the program. The intent of this testing is not to exercise all
the different input or output conditions but to exercise the different programming
structures and data structures used in the program. White-box testing is also
called structural testing and we will use the two terms interchangeably. To test
the structure of a program, white-box testing aims to achieve test cases that will
force the desired coverage of different structures. Various criteria have been
proposed for this. Unlike the criteria for functional testing, which are frequently
imprecise, the criteria for white-box testing are generally quite precise as they
are based on program structures, which are formal and precise.

ALPHA TESTING

The first test of newly developed hardware or software in a laboratory setting.

When the first round of bugs has been fixed, the product goes into beta test with
actual users. For custom software, the customer may be invited into the vendor's
facilities for an alpha test to ensure the client's vision has been interpreted
properly by the developer.

BETA TESTING

A test of new or revised hardware or software that is performed by users at their

facilities under normal operating conditions. Beta testing follows alpha testing.
Vendors of packaged software often offer their customers the opportunity of beta
testing new releases or versions, and the beta testing of elaborate products such
as operating system take months.