CERTIFICATE OF THE PROJECT

To
The Controller of Examinations
Government College University
Faisalabad.
We, the project evaluation committee, certify that the contents and form of this project
submitted by have been found satisfactory and thus recommended for the award of Degree.

Project Evaluation Committee:

1. Prof. Muhammad Saleem Raza __________________

2. Prof. Umar Hayat _____________________________

3. Prof. Nasrullah Nazir __________________________

Department of Computer Science

GOVERNMENT GRADUATE COLLEGE JHANG

Page | 1
 DECLARATION

The work reported in this Documentation was carried out by us under the supervision of “Sir Umar
Hayat”, proficient teacher of department of Computer Science, Govt. Post Graduate College Jhang,
Pakistan. We hereby declare that the title of the project “Online Bus Ticket Reservation System”
and the contents of project is our own and no part has been copied from any project source code. We
further declare that this work has not been submitted for any award of any other degree diploma. The
college may take action for incorrect information.

Page | 2
 ACKNOWLEDGEMENT

No one alone can make such kind of project. The contributions of many people, in different ways,
have made it possible. We would like to extend our appreciation especially to the following. Thank
ALLAH for the wisdom and perseverance that he has been bestowed upon me during this project,
and indeed, throughout my life:
"I can do everything with His help who gives me strength in all my dealings."
Last but not least, we would like to thank my parents for their unconditional support not only
financially but also emotionally throughout our degree.

Page | 3
 ABSTRACT

Online bus reservation system is “web-based” project which provides a portal for bus ticket
reservation. This system will allow users to book bus tickets from anywhere and anytime. It
will provide the facility to reserve seats, cancellation of reservation and different types of
route enquiries used on securing quick reservations.

The user can easily book their tickets and cancel tickets. The user can view all the details of
the website, bus, and route. We observed the working of the Bus reservation system and after
going through it, we get to know that there are many operations, which they have to do
manually. It takes a lot of time and causes many errors. Due to this, sometimes a lot of problem
so occur and they were facing many disputes with customers . To solve the above problem,
and further maintaining records of items, seat availability for customers, price of per seat, bill
generation and other things, we are offering this proposal of online bus reservation system.

Page | 4
 Table of Contents

INTRODUCTION ............................................................................................ 10

1.1 Purpose of Project .................................................................................................................... 11

1.2 Project Scope .............................................................................................................................. 11

1.3 Project Planning ....................................................................................................................... 12

1.4 Risk Management .................................................................................................................... 12

1.5 Project Risk ................................................................................................................................ 13

1.6 Product Risk ............................................................................................................................... 13

SYSTEM ANALYSIS .................................................................................................................. 14

2.1 System Analysis ........................................................................................................................... 15

2.2 Feasibility Study .......................................................................................................................... 15

2.3 Existing System ............................................................................................................................ 16

2.4 Proposed System .......................................................................................................................... 17

2.5 Tools………………………………………………………………………………………18

SYSTEM REQUIRMENETS…………….......................................................... 19

3.1 Objective of project..................................................................................................................... 20

3.2 Available Models ......................................................................................................................... 21

3.3 Adapted Methodology .............................................................................................................. .22

3.4 System Functional Requirements .......................................................................................... 24

3.5 Interface Specifications ............................................................................................................ 25

3.6 Software Requirements…………………………………………………………………25

3.7 Hardware Requirements………………………………………………………………...26

3.8 Literature Survey ...................................................................................................................... 26

Page | 5
SYSTEM DESIGN..................................................................................................... 28

4.1 Use Case Diagram ..................................................................................................................... 29

4.2 Class Diagram ............................................................................................................................ 31

4.3 Activity Diagram ....................................................................................................................... 32

4.4 Sequence Diagram..................................................................................................................... 34

4.5 Entity Relationship Diagram………………………………………………………….36

IMPLEMENTATION & TESTING................................................................ 37

5.1 Implementation .......................................................................................................................... 38

5.2 User Training ............................................................................................................................. 38

5.3 Security & Maintenance .......................................................................................................... 39

5.4 System Testing ........................................................................................................................... 41

5.5 Test Cases……………………………………………………………………………….42

5.6 Integration Testing………………………………………………………………………44

MANUAL................................................................................................................ 46

6.1 Screen Shots of Project Modules ........................................................................................... 47

6.2 Conclusion and future extensions ................................................................................... 56

6.3 References……………………………………………………………………….57

Page | 6
 List of Figures

FIGURES ..........................................................................................................

Figure no. 1: Waterfall Model ........................................................................................................... 22

Figure no. 2: Use Case Diagram ...................................................................................................... 29

Figure no. 3: Activity Diagram ........................................................................................................ 32

Figure no. 4: Sequence Diagram ..................................................................................................... 34

Figure no. 5: Class Diagram............................................................................................................. 31

Figure no. 6: Entity-Relationship Diagram .................................................................................. 36

Figure no. 7: Login (Admin & User) .............................................................................................. 47

Figure no. 8: Registration (Admin & user) .................................................................................. 48

Figure no. 9: View Schedule ............................................................................................................. 49

Figure no. 10: Delete Schedule......................................................................................................... 49

Figure no. 11: Upload Schedule by Admin ................................................................................... 49

Figure no. 12: Approve Ticket by Admin ..................................................................................... 54

Figure no. 13: Generate Receipt...................................................................................................... 52

Figure no. 14: Download/print Receipt ......................................................................................... 52

Page | 7
 List of Tables

TABLES ............................................................................................................

Table no. 1 Test Case: 1..................................................................................................................... 42

Table no. 2 Test Case: 2..................................................................................................................... 43

Page | 8
CHAPTER 1
INTRODUCTION

Page | 9
What are we aim for through this idea? The main objective of the project entire activity is to
automate the ticket booking process of day to day activities of system like:

1. Ticket activities.

2. Creation of a Customer id.

3. Assign a bus Tickets according to customer’s demand.

4. Advance bookings.

5. Bus Ticket Cancellation.

6. Feedbacks.

1.1 Purpose of this Project

There is nothing in this world purposeless. So, our project also carries aim and goal. If any person
wants to make request for Online Bus Ticket Reservation he can also take the help of this system.
The Online Bus Ticket Reservation System is a web-based application that allows visitors check bus
ticket availability, buy bus ticket and pay the bus ticket online. This system is established for all the
home/office users after gaining access from the administrator.

1.2 Project scope

 User can buy bus ticket.

 User will be able to login to the system through their username and password.
 User can view schedule, bus route, availability of seats, can cancel reservation and make
enquiries.
 User can pay online (through QR code) or offline (through front desk officer).
 System will not work internationally.
 Bus will not wait for any passengers.
 Slow response about refunding.
 User can view his/her travel history.
 Our system will not increase bus ticket fares during festival time and public holidays.
 User can give feedback about services.
Page | 10
1.3 Project Planning
First of all, we consulted our supervisor and took guidelines in order to start the project. In this
analyzed project, we saw how the whole system works, and took synopses of each aspect of the
project. This system is said to be an automatic system and customers can select seats by
themselves.

We divided the project in three phases.

 Designing Database.
 Designing and Implementation User Interface Layouts.
 Development of Backend Programing.

1.4 Risk Management

The basic risks involved in the project were the “System Familiarity” and the “System Support”.
The elimination of such risks was made possible by making sure, the system was “User Friendly,
efficient and Interactive”, and by assuring there was adequate support for the system to work i.e. in
the form of the Windows operating system that could serve the purposes, without slowing down the
performance, otherwise the system would have been of no use. Upon the completion of the project,
we will analyze risks. Based on this analysis, the project supervisor will identify any improvements
that can be made to manage those risks and develop risk management process to minimize its impact
on project.

Page | 11
1.5 Project risk

Risk 1: User Authentication

The basic requirement of our website is User authentications either customer or employee. Both
have sperate profiling. This website will use for helping people to book online bus ticket when
they need so that website must have user authentication so that no one could misuse this
website.

Risk 2: MySQL Database

As you know that Database will act like backbone of the projects. To do that we have to choose
proper platform for our website backend, MySQL Database is best suitable for web development
projects. MySQL will act like backend server provided by Google itself.

Risk 3: Security Providing

Security measures consider as efficient part of the system, those system whose securities are high
people will trust them easily. In order to attract more users for our website we have to provide
more high security than other systems. We will use Google Chrome Authentications so that people
feel save file entering their personal data. It is more secure way to handle security measures of
website.

1.6 Product Risk

There are some constraints of this project e.g. website will work in following circumstances
 Mobile Data / Wi-Fi
 Operating System e.g. windows X
 Laptop / Tab
 Google Chrome

Page | 12
CHAPTER 2
SYSTEM ANALYSIS

Page | 13
2.1 SYSTEM ANALYSIS
System Analysis is a management technique, which helps in designing a new system or
improving an existing system. System Analysis is the process of gathering and
interpreting facts, diagnosing problems (if any), using information to recommend
improvements to the system. There are four basic elements of system analysis: - Output,
Input, Files, processes. For computerization of any system, the existing system must be
thoroughly being understood to determine ³how the computer can be best used to make
its operation most effective´. This is acquired by analyzing existing system.

2.2 FEASIBILITY STUDY

Feasibility study is the process of determination of whether or not a project is worth
doing.
Feasibility studies are undertaken within tight time constraints and normally culminate
in a written and oral feasibility report. The contents and recommendations of this
feasibility study helped us as a sound basis for deciding how to precede the project. It
helped in taking decisions such as which software to use, hardware combinations, etc.

 Technical feasibility

 Behavioral Feasibility

 Economical feasibility

2.2.1 Technical feasibility:

Technical Feasibility deals with the hardware as well as software requirements. Technology is not a
constraint to type system development. We have to find out whether the necessary technology,
the proposed equipments have the capacity to hold the data, which is used in the project, should
be checked to carry out this technical feasibility.
The proposed system can run on any machines supporting Windows and Internet services and works
on the best software and hardware that had been used while designing the system so it would be
feasible in all technical terms of feasibility

 This software is running in windows Operating System, which can be easily installed.
 The hardware required is Pentium based server.
Page | 14
  The system can be expanded.

2.2.2 Behavioral Feasibility:

This feasibility test asks if the system will work when it is developed and installed. Operational
feasibility in this project:

 The proposed system offers greater level of user-friendliness.

 The proposed system produces best results and gives high performance. It can be
implemented easily. So this project is operationally feasible.

2.2.3 Economical feasibility:

Economical Feasibility deals about the economical impact faced by the organization to implement
a new system. Financial benefits must equal or exceed the costs. The cost of conducting a full
system, including software and hardware cost for the class of application being considered should
be evaluated. Economic Feasibility in this project:

 The cost to conduct a full system investigation is possible.

 There is no additional manpower requirement.

 There is no additional cost involved in maintaining the proposed system.

2.3 EXISTING SYSTEM

Existing system refers to the system that is being followed till now. In the present Bus Ticket
Reservation System, the work is maintained by the manual process, so the user needs to contact the
person related to each branch for the inquiry to get the details such as the schedule of a bus, seat
availability, bus facility, cost, etc. In the current Bus Ticket Reservation System, the time is limited
by the working hour of the branch and the person who want to buy the ticket has to go to the
branch. The company keeps all the records related to bus ticket manually to calculate the income
which is not an easy process. While there will be a probability of error in calculation.

So, a detailed study of existing system is carried along with all the steps in system analysis.

Page | 15
2.3.1 Draw backs of existing system:
 Lack of security of data.

 More man power.

 Time consuming.

 Consumes large volume of pare work.

 Needs manual calculations.

 No direct role for the higher officials.

 Damage of machines due to lack of attention.

To avoid all these limitations and make the working more accurately the system needs to

be computerized.

2.4 PROPOSED SYSTEM

The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The system provides
proper security and reduces the manual work. The existing system has several
disadvantages and many more difficulties to work well. The proposed system tries to
eliminate or reduce these difficulties up to some extent.
The proposed online Bus Ticket Reservation System will provide an easy way to access
the information of any bus. By use of this system a user can check the ticket availability,
can know the time of bus departure, will get the notification if the bus is late. While it
will provide options such as a user can buy the ticket online, can make payments, can
cancel the tickets. As the ticket is online generated it cannot be lost while the user can
access the system 24 hours and seven days in a week which make the system user-
friendly. It will also manage the information of the user and the bus expense so that a
company can use these to analyze the profit from it.

Page | 16
2.5 Tools
Tools are the backbone of any system. If there is no tool to develop the system, there is no meaning
of any system. Tools are very necessary for any system. That’s why we also have a combination of
tools like:
 Windows X
 XAMPP
 HTML/CSS
 PHP (My Sql for DB)
 Sublime Text
 Visual Paradigm

Page | 17
CHAPTER 3
SYSTEM REQUIRMENT

Page | 18
3.1 Objectives of the Project

Online bus reservation system is web-based project which provides a portal for bus ticket
reservation. This system will allow users to book bus tickets from anywhere and anytime. It
will provide the facility to reserve seats, cancellation of reservation and different types of
route enquiries used on securing quick reservations. The user can easily book their tickets
and cancel tickets. The user can view all the details of the website, bus, and drive. The user
can also view the details of the journey and the details of the journey timings. We observed
the working of the Bus reservation system and after going through it, we get to know that
there are many operations, which they have to do manually. It takes a lot of time and causes
many errors. Due to this, sometimes a lot of problem so occur and they were facing many
disputes with customers. To solve the above problem, and further maintaining records of
items, seat availability for customers, price of per seat, bill generation and other things, we
are offering this proposal of online bus reservation system.

In the existing system, all the booking process and the maintenance of the records is done
manually. Users who are interested in inquiring about the bus type, tickets price, available
seats, facility of the bus etc. have to walk to the booking office. This creates a lot of time
waste for the users. The proposed system is a new system which is helpful to employees as
well as the users. This system provides help to the users as they can inquire about the bus
model, its ticket price, available Seats, facility of the bus etc. and they don’t need to walk to
the office. There are login and password service for employee and regular customers to use
this system.

Page | 19
3.2 Available Models

 Waterfall model
 V-shaped model
 Evolutionary prototyping mode
 Spiral method
 Iterative and Incremental method
 Agile development

3.2.1 Waterfall Model:

The waterfall approach does not allow us to backtrack to make changes in

previous phases.

3.2.2 V-shaped model:

It is an extension of waterfall model. The difference between v-shaped and

waterfall is that it provides early test planning in v-shaped model.

3.2.3 Evolutionary prototyping model:

It refers to the activity of creating prototypes of software applications, for

example incomplete version of the software program being developed.

3.2.4 Spiral method:

It is an effort to combine advantages of top-down and bottom-up concepts.

The spiral model is favored for large, expensive and complicated projects.

3.2.5 Iterative and Incremental method:

Page | 20
 It is developed to overcome the weakness of waterfall model. It starts with an
initial planning and ends with deployment with the cyclic interactions in
between.

3.2.6 Agile development:

It is based on incremental and iterative development, where requirements

and solutions evolve through collaboration between cross functional items.

3.3 Adapted Methodology:

Waterfall approach was first SDLC Model to be used widely in Software Engineering to
ensure success of the project. In "The Waterfall" approach, the whole process of software
development is divided into separate phases. In this Waterfall model, typically, the outcome of
one phase acts as the input for the next phase sequentially.
The following illustration is a representation of the different phases of the Waterfall Model.

Page | 21
3.3.1 The sequential phases in Waterfall model are −

 Requirement Gathering and analysis – All possible requirements of the system to be

developed are captured in this phase and documented in a requirement specification
document.
 System Design − The requirement specifica ons from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.
 Implementation − With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality, which is referred to as Unit Testing.
 Integration and Testing − All the units developed in the implementa on phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
 Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

Page | 22
3.4 System Functional Requirements

Functional requirements Actors System response

Registration will be done User System will allow the user to add
by user an account
Customer can Login Customer system will demand account
information
Admin can Login Admin Successfully login
Admin can add buses Admin System will update the schedule
Admin can add Routes Admin System will update the routes
Admin can add employee Admin System will add employees
Admin can Remove Admin System will remove employees
employee
Admin can Remove buses Admin System will remove the bus
Admin can update Admin Information in the system will be
information updated
Admin can manage Admin System will allow admin to have
accounts access to the accounts of their
employees
Admin can generate Admin System will generate report
Weekly, monthly reports
Customer can view Customer System will show the schedule
schedule
Customer can View Bus Customer System will show available bus
status details
Customer will Select Customer System will show available
destination departures
Customer can Select Customer System will show date schedule
departure date
Customer can view Customer System will show available seats
Availability of seats
Customer can Select bus Customer System will save bus details
Customer can reserve Customer System will confirm the
ticket reservation
Customer can Select Customer System will show two payment
payment method methods 1) Online 2) offline
Customer will make Customer System will store the account
Payment information

Page | 23
 Notification
User can cancel booking
Admin can cancel booking
User can reschedule their
tickets
Report
User can give feedback
User can view travel
history
Automated Any type of notification is sent
automatically
User System will allow the customer
to cancel their bookings
Admin System will allow admin to
cancel bookings if soiled weather
or any type of disaster
User System will allow user to
reschedule their tickets
according to their needs
Automated System will generate the report
about user ticket status
Customer System will allow customer to
add feedback
Customer System will show history

3.5 Interface specifications

The Interface Requirements Specification (IRS) specifies the requirements imposed on one or
more systems, subsystems, Hardware Configuration Items (HWCIs), Computer Software
Configuration Items (CSCIs), manual operations, or other system components to achieve one or
more interfaces among these entities. Interface design often assumes the status of
requirements when the design is baselined, e.g. prior to release into production or purchasing.

This is a unique phenomenon, brought about because, once a product is released into
production or purchasing, any replacement will need to retain the interface design
characteristics of the original (fully or partly), not just satisfy the interface requirements.

This is because the thing at the other end of the interface is relying an mutual consistency from
the SoI.

3.6 Software requirements

Operating system window 7 or above

Sublime text
Front end: HTML, CSS, bootstrap
Backend: MYSQL, PHP, JAVASCRIPT

Page | 24
 3.7 Hardware requirements

PC with core 2 duo or more processor

512 MB RAM or above
1 GB hard disk or above

3.8 Literature survey

A literature review is a survey of scholarly sources (such as books, journal articles, and thesis)
related to a specific topic or research question. It is often written as part of a thesis, dissertation, or
research paper, in order to situate your work in relation to existing knowledge. The purpose of
a literature review is to Identify areas of prior scholarship to prevent duplication and give credit to
other researchers. ... Identify need for additional research (justifying your research) Identify the
relationship of works in context of its contribution to the topic and to other works. Over the years,
numerous types of literature reviews have emerged, but the four main types are traditional or
narrative, systematic, meta-analysis and meta-synthesis.
We did literature survey and found these websites related to our project

 BOOKME.PK
This website is easily available on google. We have studied a lot about this website. We have
attached picture of this website interface. This website helps you find schedule and to book ticket.
You can contact them through phone number or email address. This information is added on their
website. It will give us the list of all schedules and available tickets.

Page | 25
 Daewoo
This website is also easily available on google. We have studied a lot about this website. We
have attached picture of this website interface. This website helps you find schedule and to
book ticket. You can contact them through phone number or email address. This information
is added on their website. It will give us the list of all schedules and available tickets.

Page | 26
CHAPTER 4
SYSTEM DESIGN

Page | 27
4.1 Use-Case Diagram (Customer):

Page | 28
4.1.1 Use-Case Diagram (Admin):

Page | 29
4.2 Class Diagram:

Page | 30
4.3 Activity Diagram (User):

Page | 31
4.3.1 Activity Diagram (Admin):

Page | 32
4.4 Sequence Diagram (User):

Page | 33
4.4.1 Sequence Diagram (Admin):

Page | 34
4.5 Entity-Relationship Diagram (ERD):

Page | 35
CHAPTER 5
IMPLEMENTATION & TESTING

Page | 36
5.1 IMPLEMENTATION

After you have carefully planned your project, you will be ready to start the project implementation
phase, the third phase of the project management life cycle. The implementation phase involves
putting the project plan into action. That’s what happens in the implementation phase of the project
life cycle: you follow the plan you’ve put together and handle any problems that come up. The
implementation phase is where you and your project team actually do the project work to produce
the deliverables. The word “deliverable” means anything your project delivers. The deliverables for
your project include all of the products or services that you and your team are performing for the
client, customer, or sponsor, including all the project management documents that you put
together. The steps undertaken to build each deliverable will vary depending on the type of project
you are undertaking, and cannot therefore be described here in any real detail. For instance
computer software projects may require the development and implementation of software code
routines to produce each project deliverable. The activities required to build each deliverable will
be clearly specified within the project requirements document and project plan. The
implementation phase keeps the project plan on track with careful monitoring and control
processes to ensure the final deliverable meets the acceptance criteria set by the customer. This
phase is typically where approved changes are implemented.
Most often, changes are identified by looking at performance and quality control data.
Routine performance and quality control measurements should be evaluated on a
regular basis throughout the implementation phase. Gathering reports on those
measurements will help you determine where the problem is and recommend changes
to fix it.

5.2 User training

Training of the end users is one of the most important steps for a successful system
implementation. The end users should be utilized during parallel testing, so training will need to be
rolled out prior to that. Getting the end users involved at this point is also a good way to get them
excited about the system, as many of them may not have been involved with the project prior to
training.

Page | 37
 Their assistance in parallel testing will help them prepare for when the system goes live. End users
are good at using the system in more of a "real world" situation and can judge when process flows
are not working. When everyone involved with using the system is included in the training, they
will feel more confident about using it as they go into production and the user community will view
the implementation as successful.

The system may have been tested for functionality and all customizations are working accurately,
but if the end users do not know how to use it or feel comfortable with it, then the launch of the
new system will be viewed as unsuccessful. Therefore, the timing of the end user training is critical
and must be planned for and implemented prior to the start of the parallel test phase to ensure a
successful implementation.

There are two possible solutions for training. The first is to use project team members to
develop and deliver the end user training and the second is to identify a training partner
to support the development and delivery of end user training, including a train the
trainer component.

5.3 Security and Maintenance

Maintenance means restoring something to its original conditions.
System maintenance conforms the system to its original requirements. Thus,
maintenance changes the existing system, and development replaces the existing
system. It is an important part of system development that includes the activities which
corrects errors in system design and implementation, updates the documents, and tests
the data.
System maintenance can be classified into three types −
 Corrective Maintenance − Enables user to carry out the repairing and correcting
leftover problems.
 Adaptive Maintenance − Enables user to replace the functions of the programs.
 Perfective Maintenance − Enables user to modify or enhance the programs
according to the users’ requirements and changing needs.

5.3.1 Security

A considerable amount of applications and systems have been faced serious security
threats due to the large number of new available technologies and the lack of
knowledge and investigation about them. In the past, security concerns were basically
Page | 38
around network infrastructure layers. Currently, due to the growing use of networks and
the Internet concept dominance, such as cloud computing, Software as a Service (SaaS),
serious vulnerabilities are being discovered by attackers in the application layer.
Therefore, the concept of application security layer emerged as an essential task in the
development process.
According to Federal Information Processing Standard (FIPS) (The National Institute of
Standards and Technology (NIST), 2010) there are three security core principles that
guide the information security area:

 Confidentiality: preserve the access control and disclosure restrictions on information.

Guarantee that no one will be break the rules of personal privacy and proprietary information;
 Integrity: avoid the improper (unauthorized) information modification or destruction. Here is
included ensure the non-repudiation and information authenticity;
 Availability: the information must be available to access and use all the time and
with reliable access. Certainly, it just must be true for those who have right of access.

Page | 39
5.4 SYSTEM TESTING
5.4.1 Unit testing:

This is the testing process which we can do manually because in this testing program is a
tested individually using dummy record to see whether that program produce satisfied
output.

5.4.2 Validation Testing:

In this requirements established as part of software requirement analysis are validated

against the software that has been constructed validation testing provides final
assurance that software meets all functional, behavioral and performance requirements.
Validation can be define in many ways but a simple definition is that validation succeeds
when software function in a manner that can be reasonably by the customer.
 Validation test criteria
 Configuration review
 Alpha and beta testing (conducted by end user)

5.4.3 System testing:

System testing is actually a series of different test whose primary purpose is to full
exercise the computer base system. Where the software and other system elements are
tested as whole. To test computer software, we spiral out along streamlines that
broadens the scope of testing with each turn.
The last higher-order testing step falls outside the boundary of software Engineering and
in to the broader content of computer system engineering. Software , once validated
,must be combining with order system elements(e.g. hardware , people
,databases).System testing verifies that all the elements Mesh properly and that overall
system function/performance is achieved.
 Recovery testing
 Security testing
 Stress testing

Page | 40
5.5 Test cases:

Case id Test case Expected Actual output conclusion

output
1 Login test Login with Successfully This
proper details login function
and role works
effectively

2 Managing details Manage successfully This

information function
properly works
stored effectively

3 Add/ update bus information Add/ update successfully This

bus function
information works
properly properly

4 Add/update employee Add/update successfully This

information employee function
information works
properly properly

5 View ticket booking information View booking successfully This

info properly function
works
effectively

6 View payment information View successfully This

payment function
request works
properly effectively

7 Exception handling Proper error Not This

message successfully function
should does’nt
display works
effectively

8 Add/update schedule Add/update successfully This

information schedule function
information works
properly properly

Page | 41
 9 View customer information View successfully This
customer function
information works
properly effectively

10 View feedback View Successfully This

feedback function
properly works
effectively

5.5.1 Customer test case:

Case id Test case Expected output Actual Conclusion
output
1 Login test Login with proper details successfully This
function
works
effectively

2 Register test Proper register with successfully This

exception handling function
works
effectively

3 Update profile Change/update user profile successfully This

function
works
effectively

4 View bus View bus information successfully This

information properly function
works
properly

5 View schedule View schedule information successfully This

properly function
works
properly

6 Search Search information properly successfully This

information/schedu function
le works
properly

7 Book ticket Book bus ticket properly successfully This

Page | 42
 function
works
properly

8 Make payment Make payment successfully successfully This

function
works
properly

9 view booking View booking properly successfully This

function
works
properly

10 Cancel booking Give permission to cancel successfully This

booking function
works
properly

11 Give feedback back Give feedback properly successfully This

function
works
effectively
12 Ask question Ask question through contact successfully This
us page properly function
works
effectively

5.6 INTEGRATION TESTING

Integration testing is the phase of software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before validation testing.
Integration testing takes as its input module- that have been unit tested- groups them in larger
aggregate, applies tests defined in an integration test plan to those aggregates and delivers its
output that integrated system ready for system testing.

Two types of integration testing approach in software testing we used are:

Page | 43
 Top down

All top-level integrated modules are tested first and its sub modules tested from top to
bottom step by step.

 Bottom up

All bottom level integrated sub modules are tested first and its main modules are tested
from bottom to up step by step.

Page | 44
CHAPTER 6
USER MANUAL

Page | 45
 Manual
1. Signin & Signup:

Page | 46
Page | 47
2. Home & Add Post Activity:

Page | 48
3. Select route and Booking activities:

Page | 49
4. Select seat:

Page | 50
5. Generate & Download Receipt:

Page | 51
6. Admin panel & Dashboard:

Page | 52
7. Confirm/Approve Bookings:

Page | 53
8. About Us & Contact Us:

Page | 54
 9. Conclusion and Possible Extensions in Future:

ALS Travels is a company online system, which enable customer to check availability of bus ticket,
buy bus ticket & pay bus ticket online.
It makes the customer easy to get bus ticket online instead of queue up to buy the bus ticket.

Page | 55
References:

https://daewoo.com.pk/
https://bookme.pk/
https://www.redbus.in/
https://www.flaticon.com/

https://www.wikipedia.org/

https://www.lovelycoding.org/bus-reservation-system/

https://www.slideshare.net/stejinpaulson/online-bus-booking-system

https://www.google.com/

https://www.researchgate.net/publication/326468848_Online_Bus_Ticket_Reservat
ion_System

Page | 56