SOFTWARE REQUIREMENT

SPECIFICATION

SUBMITTED BY,

ARAV V DAS
 ABSTRACT
The project entitled is used to implement the activities in online bus ticket booking
management for travel agency. The passengers travelling by bus is increasing day by day ,So
online bus ticket booking management system will increase the booking process fast convenient
and comfortable .The transactions like booking ticket ,pick up ,and drop off as per the passengers
demand ,keeping the records of passengers etc .When processed manually take up lot of time to
keeping the track of transactions of travel agency on online computerized system seems to be the
best way as it will speed up the work chain and it reduces the complexities in the management.
In simple language the online computerized system provides user friendly online system.

MODULE DESCRIPTION

 BOOKING MODULE
This module deals with booking process of bus agency .The booking is done in
accordance to the customer preferences. It can also perform the cancellation process in which
tickets booked is cancelled by the customer.

 ADMINISTRATION MODULE
The administration module contains the administration processes like viewing or
searching of booking details of every passenger, generating reports of the tickets booked,
checking number of remaining seats, adding new route, stops and schedules, adding of a new
employee and creation of their profile. The admin can also manage ticket rate and bus
scheduling.

 CUSTOMER MANAGEMENT MODULE

This module is completely dedicated to the customer. It includes processes like customer
login and registration in which customer is assigned to a unique id and maintains the booking
history of the customer. Moreover this module also provides the facility for posting feedback.
HOME PAGE
The first page has a navigation bar that contains the following buttons:

 About Us: details about the hospital administration

 Contact Us: the contact details
 Sign Up: to sign up to the website
 Login: to login to your registered page

REGISTERATION PAGE
The home page has a registration button .On clicking this button, it will redirect
to webpage for registering the user. The registration will have the following text boxes and the
save button:

 Email-Id- To enter the email id of the customer and this email id.

On clicking the next button the user will be re-direct to new page to enter their
details. The webpage will have textboxes for the following

 Password - To enter the Password. Password can be alphanumeric, can contain special
characters and must be at least 8 characters in length.

 Re-enter password – To enter the password again to confirm the same given in
password textbox.

 Name – To enter the name this can be alphabets.

 Gender – To enter the gender is either Male or Female as specified in the sex choice.

 Age- To enter the of the customer. It must be entirely numeric with a specified default
value.

 Date Of Birth- To enter the date of birth, this should be a date.

  Mobile-Number – To enter the mobile number of customer. It must be 10 characters
long.

 Profile Picture- To insert a image in the image field.

Once registration is completed successfully, an acknowledgement mail will be sent to

respective customer.

LOGIN PAGE
All the users can login, the admin, staff and customers. When the admin login to the
website then admin is redirected to admin page. When the staff does the login then they are
redirected to staff form page and when the customer login then they will be redirected to home
page after logging in and the customer can book the tickets there . In the login page itself we
implement Google captcha.

BOOKING PAGE
By selecting their destination, boarding point and the desired date in home page after
logging in, the user will be directed to the booking page. In the booking page the patient can book
the ticket to their desired destination in the desired class at affordable rates.
DATABASE DESIGN

1. LOGIN

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

1.ADMIN
1 USER_TYPE INT(20) NOT NULL 2.EMPLOYEE
3.CUSTOMER
UNIQUELY
2 USER _NAME INT(20) PRIMARY KEY IDENTIFIES THE
USER.

3 PASSWORD VARCHAR(30) NOT NULL PASSWORD.

2. REGISTRATION

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

UNIQUELY
1 CUSTOMER_ID INT(20) PRIMARY KEY, IDENTIFIES THE
AUTO CUSTOMER.
INCREMENT

2 F_NAME VARCHAR(20) NOT NULL FIRST NAME OF

CUSTOMER.

3 L_NAME VARCHAR(20) NOT NULL LAST NAME OF

CUSTOMER.
UNIQUELY
4 USER_NAME VARCHAR(20) FOREIGN KEY IDENTIFIES THE
(USER_LOGIN) USER.

5 AGE INT(20) NOT NULL AGE OF THE

CUSTOMER.
HOUSE NAME
6 HOUSE_NAME VARCHAR(50) NOT NULL OF THE
CUSTOMER.

7 LAND_MARK VARCHAR(40) NOT NULL NEAREST LAND

MARK
THE CITY/TOWN
8 CITY_TOWN VARCHAR(30) NOT NULL TO WHICH
HOUSE
BELONGS.
POSTAL INDEX
9 PIN_CODE INT(20) NOT NULL NUMBER OF
THE LOCATION.
PHONE NUMBER
10 MOBILE_NUMBER INT(20) NOT NULL OF THE
CUSTOMER.
3. ROUTE

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

PRIMARY UNIQUELY
1 ROUTE_ID INT(20) KEY,AUTO IDENTIFIES THE
INCREMENT ROUTE.

2 START_LOC INT(20) FOREIGN KEY STARTING

( SERV_POINT) LOCATION.

3 END_LOC INT(20) FOREIGN KEY ENDING

( SERV_POINT) LOCATION.

3. BUS DETAILS

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

PRIMARY KEY, UNIQUELY

1 BUS_ID INT(20) AUTO IDENTIFIES THE
INCREMENT BUS.
BUS
2 BUS_REG_NO VARCHAR(20) NOT NULL REGISTERATION
NUMBER.
NUMBER OF
3 TOTAL_SEATS INT(20) NOT NULL SEATS IN THE
BUS.
5. SCHEDULE

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

PRIMARY UNIQUELY
1 SCHEDULE_ID INT(20) KEY,AUTO IDENTIFIES THE
INCREMENT SCHEDULE.
UNIQUELY
2 ROUTE_ID INT(20) FOREIGN KEY IDENTIFIES THE
(ROUTE) ROUTE.
UNIQUELY
3 BUS_ID INT(20) FOREIGN KEY IDENTIFIES THE
(BUS DETAILS) BUS.

4 START_TIME TIME NOT NULL STARTING TIME.

5 END_TIME TIME NOT NULL ENDING TIME.

6. STOP_INFORMATION

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

PRIMARY UNIQUELY
1 STOP_ID INT(10) KEY,AUTO IDENTIFIES THE
INCREMENT STOPS.

2 STOP_NAME VARCHAR(30) NOT NULL STOP NAME.

7. SCHEDULE_TIME

SL.NO FIELD NAME DATATYPE CONSTRAIN DESCRIPTION

UNIQUELY
1 ROUTE_ID INT(20) FOREIGN KEY IDENTIFIES THE
(ROUTE) SCHEDULE.
UNIQUELY
2 STOP_ID INT(20) FOREIGN KEY IDENTIFIES THE
(ROUTE) POINTS.

3 TIME TIME NOT NULL TIME.

4 CHARGE INT(20) NOT NULL CHARGES OF

BOOKING.

8. CARD DETAILS

SL.NO FIELD NAME DATA TYPES CONSTRAINT DESCRIPTION

1.ADHAR CARD
1 ID_TYPE INT(20) PRIMARY KEY 2.VOTE ID
3.PAN CARD
9. BOOKING CHART

SL.NO FIELD NAME DATA TYPES CONSTRAINT DESCRIPTION

PRIMARY UNIQUELY
1 BOOKING_ID INT(20) KEY/AUTO IDENTIFIES
INCREMENT THE BOOKING

2 DATE DATE NOTNULL DATE OF

BOOKING

3 SCHEDULE_ID INT(20) FOREIGN KEY UNIQUELY

(SCHEDULE) IDENTIFIES THE
SCHEDULE

4 CUSTOMER_ID INT(20) FOREIGN KEY UNIQUELY

(CUSTOMER_ IDENTIFIES THE
REGISTRATION) CUSTOMER
1.ADHAR CARD
5 ID_TYPE INT(20) FOREIGN KEY 2.VOTER_ID........
(CARD TYPE) ETC.

UNIQUELY
6 ID_NUMBER VARCHAR(30) NOTNULL IDENTIFIES THE
ID.

7 TOTAL_NO_OF_SEAT INT(20) NOTNULL NUMBER OF

S_BOOKED SEATS BOOKED.
10. BOOKING DETAILS

SL.N FIELD NAME DATA TYPES CONSTRAINT DESCRIPTION

O
UNIQUELY
1 BOOKING_ID INT(20) FOREIGN KEY IDENTIFIES
(BOOKING_ THE BOOKING.
CHART)

THE SEAT
2 SEAT NO INT(20) PRIMARY KEY SELECTED BY
CUSTOMER.
UNIQUELY
3 SCHEDULE_ID INT(20) FOREIGN KEY IDENTIFIES
(SCHEDULE) THE
SCHEDULE.

11. FEEDBACK

SL.NO FIELD NAME CONSTRAINT DESCRIPTION

DATA TYPES
PRIMARY UNIQUELY
1 FEEDBACK_ID INT(20) KEY/AUTO IDENTIFIES
INCREMENT THE
FEEDBACK.
UNIQUELY
2 BOOKING_ID INT(20) FOREIGN KEY IDENTIFIES
(BOOKING_CHART) THE
BOOKING
COMMENT
3 COMMENT VARCHAR(30) VARCHAR ABOUT THE
SERVICE.