A

CAPSTONE PROJECT REPORT ON

“ONLINE BUS RESERVATION SYSTEM USING WEB

APPLICATION”

PROJECT WORK SUBMITTED IN PARTIAL FULFILLMENT OF

THE REQUIREMENTS FOR THE AWARD OF DIPLOMA.
SUBMITTED BY

“DEV JAYESH PARMAR’”

UNDER THE GUIDANCE OF

“Mr. NILESH VISPUTE”

DEPARTMENT OF COMPUTER ENGINEERING

MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

ACADEMIC YEAR (2021-2022)

 CERTIFICATE

This is to certify that Mr. “DEV JAYESH PARMAR” from PRAVIN PATIL
COLLEGE OF DIPLOMA ENGINEERING AND TECHNOLOGY institute having
Enrollment no: 1905630056 has completed project of final year having title “ONLINE BUS
RESERVATION SYSTEM USING WEB APPLICATION” during the academic year 2021 –
2022.
The project completed in a group consisting of three persons under the guidance of the
faculty Guide.

Project Associates_____ Enrollment no Seat no

1 Dev Jayesh Parmar 1905630056

2 Siddhant Sanjay Jadhav. 1905630067
3 Romit Rajesh Doiphode 1905630070

_______________________ ______________________
__
Mr. Nilesh J. Vispute ______________________
__
Internal Examiner External Examiner

_______________________ ______________________
_
Mr. Nilesh J. Vispute Ms. Manjula Athani

Project Guide Head of Department

_______________________
 Dr. Ranjana B Patil
Principal

ACKNOWLEDGEMENT

We express our sincere thanks to Principal Madam Mrs. Ranjana Patil, Pravin Patil
Polytechnic, Bhayandar who has given us the opportunity to pursue our diploma in Computer
Engineering department. We also express our thanks to H.O.D Ms. Manjula Athani and other
staff of Computer department.

We would like to thank our guide “Mr. Nilesh J. Vispute” for his encouragement and guidance,
which helped us in completing the project. Finally we would like to thank our colleagues and
friends who helped us in completing the Project successfully.

We would also like to express our heartfelt gratitude to our parents, teachers and friends for
their direction, motivation and selfless support.

Project Associates

1 Dev Parmar

2 Siddhant Jadhav

3 Romit Doiphode
 ABSTRACT

Here We are going to discuss “ONLINE Bus Ticketing System” which is completely
a web application. As we already discussed above that internet has made the user's
interaction through the system easier, so this web application can connect to
respective servers for accessing data which will surely help users to purchase the bus
ticket or reserve their seats online without waiting in queue. Moreover, in recent
times people like to travel to get some relief from their monotonous life. So, they
want to travel without any hesitations. In this modern Tech Era they want a system
that will enhance the portability, accessibility as well as a user friendly interface. So
here, we are going to implement a web system, which we already stated above,
having all the features that will make it more user friendly and accessible.
 INDEX

Sr. Topic Page

No. No
1 INTRODUCTION 3

1.1 Problem statement 4

1.2 Proposed System 6

2 SOFTWARE AND HARDWARE SPECIFICATION 15

2.1 Hardware Details 15

2.2 Software Details 15

3. DESIGNING 19

3.1 Data- Flow Diagram / Flow Chart 19

3.2 ER diagram 25

3.3 UML diagram 27

3.3.1 Use case diagram 27

3.3.2 Activity diagram 28

3.3.3 Sequence diagram 31

3.4 GUI 33

4. Results and Analysis 41

5. Features and Applications 48

6. Advantages and Limitations 49

7. Future Enhancement 49

8. Conclusion 50

9. Bibliography 50

10. List of Figures 2

Sr.No Figure Title Page No

1 Software Development Life Cycle 11

 2 Waterfall Model 13

3 Gantt Chart 18

4 Test Case Diagram 46

5 Context - DFD Diagram 22

6 E R Diagram 25

7 Use Case Diagram 27

8 Sequence Diagram Activity Diagram 32

9 Activity Diagram 30

10 Screenshot view of Website 33

1 Introduction

Bus Reservation System will increase the booking process faster, convenient, and
comfortable. Customers can book their desired seats. They can check the availability of
posts on a specific date. The customer can check availability, book a ticket, or cancel a
ticket 24X7. The online system is available to use anytime. The user doesn’t require to
visit any office.
 “ONLINE Bus Ticketing System” which is completely a web application. As we already discussed
above that internet has made the user's interaction through the system easier, so this web application can
connect to respective servers for accessing data which will surely help users to purchase the bus ticket or
reserve their seats online without waiting in queue. Moreover, in recent times people like to travel to get
some relief from their monotonous life. So, they want to travel without any hesitations. In this modern
Tech Era they want a system that will enhance the portability, accessibility as well as a user friendly
interface. So here, we are going to implement a web system, which we already stated above, having all
the features that will make it more user friendly and accessible

They just need internet and device to use our system. They can check the route, price, class, etc. They
can pay the fare using a credit card, debit card, internet banking, online wallet like Paytm, and cash too.
Managing buses, employees, and salaries would be very comfortable using this system. This is a safe
and secure way to expand the business.

The system decreases human efforts and increases customer satisfaction.

1.1 Problem Statement

Currently, the type of system being used at the counter is an internal system
which is manually used in selling the bus tickets. The problems facing the company are that
customers have to go to the counter to buy bus ticket or ask for bus schedule, customers will
also have to queue up for a long time in order to secure a bus ticket and will also need to pay
cash when they buy the bus ticket.
 Existing System
By selling and buying of bus tickets manually, the customer have to visit the ticket counter
for buying tickets, so he/she couldn’t compare prices and only a limited customers can visit.
It’s also quite time consuming waiting in long queues for buying tickets. The scope of the
project is to provide approaches and strategies which have proved to be the suitable when
assessing the bus ticket booking system of the defined region. This collection will reduce the
waiting time for the customer. The fundamental aim of this website is convenient service to
the customer.

Solution Statement
The proposed solution to the client’s problem is that of an online bus booking system that
wouldn’t allow the purchase of bus tickets by customers from any point of their wish while
also solving the hassles involved with the manual system .

1.2 Proposed System

. Online Bus Ticket Reservation System is a Web based application that works within a
centralized network. This project presents a review on the software program "Online Bus
Ticket Reservation System" as should be used in a bus transportation system, a facility which
is used to reserve seats, cancellation of reservation and different types of route enquiries used
on securing quick reservations. OBTRS is built for managing and computerizing the
traditional database, ticket booking and tracking bus and travel made. It maintains all
customer details, bus details, reservation details. In order to achieve the design, Imo
Transport Company (ITC) was chosen as a case study because of its strategic importance to
Imo State. Structured Systems Analysis and Design Methodology (SSADM) was adopted. In
addition, PHP Hypertext Preprocessor (PHP) language was used for the front-end of the
software while the back end was designed using MySQL. The software achieved is capable of
improving the customer hand and relationship management in ITC operations. It is
recommended that despite the present functionality of the designed software, an additional
functionality such as the use of E-mail to send tickets and notifications to the customer and an
online payment using credit cards/debit cards should be implemented into the system.
Furthermore, other operations carried by ITC such as the courier services should also be
integrated in order to enhance the system
 PROJECT PLAN

Feasibility Study :

Feasibility study is totally depending upon the preliminary investigations &

requirements of the system. Hence we have to determine the system requested is feasible or
not. This helps us to check technical, operational & financial feasibility of requested system
against the current system.

Operational Feasibility:

It is a measure of how well a proposed system solves the problems, and takes
advantages of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development.

Technical Feasibility:

The time taken to develop this project is appropriate and is the minimum time
required to this size of a project hence this project is feasible with respect time.
In this the assessment is based on an outline design of system requirements in terms of Input,
Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of
volumes of data, trends, frequency of updating, etc. in order to estimate whether the new
system will perform adequately or not.
 Schedule Feasibility:

Schedule feasibility is a measure of how reasonable the project timetable is. This
means estimating how long the system will take to develop. Some projects are initiated with
specific deadlines. You need to determine whether the deadlines are desirable. This was done
using the Gantt & Pert Charts.

Financial and Economical Feasibility

The cost for H/W and S/W is feasible, as it requires investments at the start of the
system of computer, printer etc. But the Company already have computer system. So at the
start they don’t need to invest. The current manual system they require regular investments &
also require more storage space inform of cupboards etc. So the software system which we
are developing is feasible in financial and economical aspects.

Cost Benefit Analysis

Effort Estimation Using COCOMO Model:-

For any given set of the requirement it is essential to know how much it will cost
me to develop the application software and to satisfy the given requirements and how much
time it will take for the development .These estimate are needed before development is
initiated. The primary reason for cost and schedule estimation is to enable the client or
developer to perform a cost benefits analysis and for project monitoring and control.

We use Intermediate Constructive Cost Model for estimating the value of our
system. We use intermediate COCOMO model for two prime reasons, first it considers the
effect of more cost drivers. Second, in the Intermediate mode the system can be divided into
components. Hence Intermediate model produces better results than the Basic Model. Every
project is considered to be developed in one of three modes:

Steps of Analysis:-

1. Obtain an initial estimate of development efforts as follows:

Ei = a*(KSLOC) b
Where a and b are constants which are determined
depending on the type of project. KSLOC is thousand single lines of the
code.

2. Determine a set of 15 multiply factors from different attributes of the product which
are
 Computer Attributes:
Execution Time constraints, main storage, constraints, virtual machine volatility
and computer turnaround time.

Product Attributes: Required reliability, product complexity.

Personnel Attributes: Analyst capability, application experience,

programmer capability, virtual machine experience, programming language experience.

Project Attributes: Modern programming practices, use of software

tools, required development schedule. '

Following is a basic COCOMO model of the system based on the Organic Mode

Product Attributes Rating Value

Required Software Reliability High 1.15

Size of Application Database Nominal 1.00

Complexity of the Product High 1.15

Hardware Attributes
Run-time constraints Performance Very High 1.30
Memory Constraints Nominal 1.00

Volatility of the Virtual Low 0.87

Machine Environment Low 0.87
Computer Turn-around Time

Personnel Attributes
Analyst Capability Nominal 1.00
Applications Experience Nominal 1.00
Programmer Capability Nominal 1.00
Virtual Machine Experience Nominal 1.00
 Programming Language Experience Nominal 1.00

Project Attributes
Modern Programming Practices Very High 0.83
Very High 0.83
Use of Software Tools
Required Development Very High 1.08
Schedule

Based on the ratings for the specified cost drivers, the EAF (Effort Adjustment
Factor) for Online RTO Management can be calculated as follows:
= 1.15 × 1.00 × 1.15 × 1.30 × 1.00 × 0.87 × 0.87 × 1.00 × 1.00 × 1.00 × 1.00 ×
1.00 × 0.83 × 0.83 × 1.08 = 0.9681830574

The calculated EAF =

EFFORT = EAF*3.2*(KDSI) ^ 1.05= SM

TDEV=2.5* SM= Months

Average staffing: SM/Months= People

KLoC = 1.80

EFFORT = EAF*3.2*(KDSI) ^ 1.05

= 0.9681830574 * 3.2 * (1.80) ^1.05

=6.0 7713= 6 months (approximate)

Total time required to develop the project: 6 months (6 × 30 = 180 days)

Cost per day: Rs. 25
Number of developers:2
Therefore,
Total Cost = Number of developers × Cost per day × Number of days w orked
= 2 * 25 * 180
= Rs. 9000/-
 Life Cycle Phase (SDLC)
Software Development Life Cycle

Steps for software development: System Development Life Cycle (SDLC) is

the overall process of developing information systems through a multi-step process from
investigation of initial requirements through analysis, design, implementation and
maintenance. There are many different models:

1. Waterfall Model
2. Build and fix Mode
3. Fountain Model
4. Spiral Model
5. Rapid prototype Model
6. Incremental Model

In software engineering the SDLC concept underpins many kinds of software

development methodologies. These methodologies form the framework for planning and
controlling the creation of an information system. Waterfall model: Model used for proposed
system.

Fig. 1.1 Software Development Life Cycle

 Waterfall Model

The waterfall approach describes the software development process in a linear

sequential flow. This means that any phase in the development process begins only if the
previous phase is complete. The waterfall approach does not define the process to go back to
the previous phase to handle changes in requirement. Therefore, different projects may follow
different approaches to handle such situation.

The waterfall approach is the earliest approach that was used for software
development. Initially, most projects followed the waterfall approach because they did not
focus on changing requirements.

The waterfall approach defines software development process in six phases:

Feasibility Study: Triggers when a problem is perceived. This phase involves

identifying goals to be achieved after the problem is solved, estimating benefits in the new
system over the current system and identifying other areas that are affected by the solution.

Coding & User Testing : Involves converting the design into a machine readable
form. Involves integrating and testing all the modules developed in the previous as a solution.

Requirement Analysis & Specification: Involves a macro level study of the

customer requirements. This phase also involves defining alternative solutions to the
customer requirements and cost-benefit justification of these alternatives.

Design: Involves translating the identified requirement into a logical structure

called design that can be implemented in a programming language. This involves converting
the new system design into operation.

System Testing & Implementation: Involves carrying out a detailed study of

the customer requirements and arriving at the exact requirements of the proposed system. The
phase involves freezing the requirements before the design phase begins.

Maintenance : This may involve implementing the software system and training
the operating staff before the software system is functional.

Diagram of Waterfall-model:
 Fig. 1.2 Waterfall Model

Advantages of Iterative Waterfall Model

1. Easy to explain to the user.

2. Stages and activities are well defined.
3. Helps to plan and schedule the project.
4. Verification at each stage ensures early detection of errors / misunderstand
 Fact Finding Techniques - (Requirement Gathering)

Requirements gathering is an essential part of any project and project management.

Understanding fully what a project will deliver is critical to its success. Approach in this
project is to give gathering of information through various technologies to be used to develop
application Attendance Management System.

We learned the technologies to be used for development, during this phase by

listening to tutorials which helped us gain knowledge about the implementation of the
technologies. Project goals and objectives, the application goals and objectives for this
project will focus on implementing application Attendance Management System that will do
the following facilitates coordination and information sharing between both the
administrators and the users. Provides an open, flexible, reliable technology base which is
easy to use. Ensuring that end users have input into the design of the application through the
enquiry and feedback forms provided.

User requirements most typically described the relative needs, tasks, and goals of
the user of an individual application. There is therefore a need to define, document, and
describe the requirements of the end-user of this website. It should also be taken into
consideration that needs and requirements change over time and a website must be initially
designed to accommodate these changes through updates and further additions. It supports the
establishment of reliable strategies such as the clarification of any possible ambiguity, the
careful definition of the project scope, not allowing to merely assume what it is that the end-
user wants or needs, benefits such as savings can be enjoyed by clients, costs for development
can be approximated, competition is identified and improvement on their capabilities can be
subsequently offered. We have also give special attention to the website design, website
Features, website Layout and Search Engine Optimization Strategy.

Similarly, we have following area having unlimited option which are not easy to
overcome.

⮚ What is the most valuable information for the visitor, user from his/her point of view?
 ⮚ What area of rates. Prices user can afford?

⮚ What internet and related services would satisfy his needs?

⮚ What is likely to be the most common device for visitors to view the web page?

⮚ What type will be easy to read in each screen size?

⮚ What type of layout is easy to follow?

2 Software and Hardware Specifications

To be used efficiently, all computer software needs certain hardware components
or other software resources to be present on a computer. These prerequisites are known as
(computer) system requirements and are often used as a guideline as opposed to an absolute
rule. Most software defines two sets of system requirements: minimum and recommended.
With increasing demand for higher processing power and resources in newer versions of
software, system requirements tend to increase over time. Industry analysts suggest that this
trend plays a bigger part in driving upgrades to existing computer systems than technological
advancements. A second meaning of the term of System requirements, is a generalization of
this first definition, giving the requirements to be met in the design of a system or sub-
system. Typically an organization starts with a set of Business requirements and then derives
the System requirements from there. For development of our application Attendance
Management System we need following minimum system requirements:

2.1 Hardware Requirements

Processor: i5 processor 3.4 Ghz
Storage : HDD 240 GB Hard Disk Space and Above
Disc Drive: 1.44 FDD
Memory: 8 GB Ram

2.2 Software Requirements

Platform: Android
Operating System: OS X, Linux, Solaris and other platforms
Front End Tool: HTML, CSS, JAVASCRIPT;
Back End Tool: PHP.
 Front End: HTML, CSS .
The HyperText Markup Language or HTML is the standard markup languages for documents
designed to be displayed in a web browser. It can be assisted by technologies such as Cascading
style sheet, scripting languages (CSS) and such as Javascript.

Web browser receive HTML documents from a web browser or from local storage and render the
documents into multimedia web pages. HTML describes the structure of web page semantically
and originally included cues for the appearance of the document.
.
CSS is designed to enable the separation of presentation and content, including layout, colors,
and fonts. This separation can improve content acessibility; provide more flexibility and control
in the specification of presentation characteristics; enable multiple web pages to share
formatting by specifying the relevant CSS in a separate .css file, which reduces complexity and
repetition in the structural content; and enable the .css file to be cached to improve the page
load speed between the pages that share the file and its formatting.

Back End: PHP

Php is general purposed scripting language geared towards web development .It
was originally created by Danish-Canadian programmer Rasmus Lerdorf in1994 . The
PHP reference implementation is now produced by The PHP Group. PHP originally stood
for Personal Home Page, but it now stands for the recursive initialism PHP: Hypertext
Preprocessor PHP code is usually processed on a web server by a
PHP interpreter implemented as a module, a daemon or as Common Gateway Interface (CGI)
executable. On a web server, the result of the interpreted and executed PHP code – which
may be any type of data, such as generated HTML or binary image data – would form the
whole or part of an HTTP response. Various web template messages, web content
management, and web frameworks exist which can be employed to orchestrate or facilitate
the generation of that response. Additionally, PHP can be used for many programming tasks
outside the web context, such as standalone graphical representation and robotic
drone control. PHP code can also be directly executed from the command line.
 Gantt Chart
A Gantt chart is a type of bar chart illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements of a
project. Terminal elements and summary elements comprise the work breakdown structure of
the project. Some Gantt chart also shows the dependency (precedence network) relationships
between activities. Gantt Charts can be used to show current schedule status using percent-
complete shadings and a vertical “TODAY” line as shown here.

Although now regarded as a common charting technique, Gantt charts were

considered revolutionary when they were introduced. This chart is used also in Information
Technology to represent data that have been collected. It is helpful tool to analyze the
development process at stage of development and to find out problem in delays and mistakes.

Fig. 1.2 Gantt chart and Timelines

3.1 Data Flow Diagram

 A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modelling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be elaborated.

A data flow diagram (DFD) illustrates how data is processed by a system in terms
of inputs and outputs. As its name indicates its focus is on the flow of information, where
data comes from, where it goes and how it gets stored. Yourdon and Coad type data flow
diagrams are usually used for system analysis and design, while Gane and Sarson type DFDs
are more common for visualizing information systems.

A DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be stored. It does
not show information about the timing of process or information about whether processes will
operate in sequence or in parallel (which is shown on a flowchart)

External entity: an outside system that sends or receives data, communicating

with the system being diagrammed. They are the sources and destinations of information
entering or leaving the system. They might be an outside organization or person, a computer
system or a business system. They are also known as terminators, sources and sinks or actors.
They are typically drawn on the edges of the diagram.

Process: any process that changes the data, producing an output. It might
perform computations, or sort data based on logic, or direct the data flow based on
business rules. A short label is used to describe the process, such as “Submit payment.”

Data store: files or repositories that hold information for later use, such as a
database table or a membership form. Each data store receives a simple label, such as
“Orders.”

Data flow: the route that data takes between the external entities, processes
and data stores. It portrays the interface between the other components and is shown with
arrows, typically labeled with a short data name, like “Billing details.”
 LEVEL 0 DFD

Fig. 3.1.1 DFD Level 0

LEVEL 1 DFD
 Fig. 3.1.2 DFD Level 1

LEVEL 2 DFD
 Fig. 3.1.3
DFD Level 2

Context Diagram
Fig 3.1.4 Context Diagram
 Flow Chart

Fig. 3.1.5 Flow chart

ER Diagram

ERD is a model that identifies the concepts or entities that exist in a system and
the relationships between those entities. An ERD is often used as a way to visualize a
relational database: each entity represents a database table, and the relationship lines
represent the keys in one table that point to specific records in tables. ERD may also be more
abstract, not necessarily capturing every table needed. Within a database, but serving to
diagram the major concepts and relationships.

This ERD is of the latter type, intended to present an abstract, theoretical view of
the major entities and relationships needed for management of electronic resources. The
Entity Relationship Diagram (Model) is based on perception of a real world that consists of
collection of basic objects called as Entity and Relationship among these objects. Entities in
database is a described as set of attributes.

A Relationship is an association among several Entities.

The set of Entities of the same type are called as Entity Set.
The set of Relationships of same type are called as Relationship Set.
 Notations used in E-R diagram

E-R diagram (Online Bus Reservation System)

 Fig. 3.1.6 E-R Diagram

3.1 Use Case Diagram

Use-Case diagram represents graphical model that summarizes information about

actor and use-case. A Use case is a description of set of sequence of actions graphically it is
rendered as an ellipse with solid line including only its name. Use case diagram is a
behavioral diagram that shows a set of use cases and actors and their relationship. It is an
association between the use cases and actors. An actor represents a real-world object.
 An automation boundary is drawn around the entire set of use-cases.
Boundary denotes the boundary between the environment, where the actors reside
and the internal functions of the automated system.

Notations:

• USE CASE:-

This describes an activity that the system carries out in response

to an event. There are two input concepts in this analysis.
• A person is involved.
• The person uses the system.  This person
involved is called an actor.

• ACTOR:-

An actor is always outside the automation system boundary of the

system. An actor can play several roles.

• LINES:-

This indicates that which actor participates with which case.

Use Case Diagram

 Fig. 3.1.7 Use Case

3.2 Activity Diagram

The figure below demonstrates the activity flow for this scrap sell application.
The flow of the application is similar for both the user and administrator.

The flow begins when the user first runs the application home screen scrap sell
application that appears in the scrap sell app. The user can browse through the available list
of categories and can choose either to select a category or to directly view the cart. In the
category, a user can select view more information for details about a particular item before
deciding to add it to the scrap sell cart by clicking on the cart icon next to the item. The user
can then decide to either continue scrap sell by clicking the continue scrap sell button or can
check out by clicking on the checkout option. If there are no items in the cart, then the user
does not have an option to click checkout.

The user can check out after doing the user authentication by logging in with the
username and password. Once the user successfully logins/registers, the order form, where
the user can put the correct information to place the order appears. If the user includes
incorrect or incomplete information, then placing the order is not allowed. After the user
successfully inputs the correct information, placing order is successful, and the user can see
the success message. The additional flow step for the administrators is that they can view the
user’s information, the user’s checkout, and the product details by using the database after
the user successfully places an order.

Activity in Unified Modeling Language (UML) is a major task that must take
place in order to fulfill an operation contract.

State defines current condition of an event or activity. State diagram is often used
to describe state changes triggered by events.

Decision activity is introduced in UML to support conditionals in

activities. A decision activity is modeled as a diamond on a UML Activity diagram.
Decision activity should reflect the previous activity.
Control flow in computer science refers to the order in which the
individual statements, instructions or function calls of an imperative or a declarative
program are executed or evaluated. Object flow is a path along which objects or data
can pass.

Object flow is a path along which objects or data can pass.

Bars represent the start (split) or end (join) of concurrent activities.

Initial state shows the initial state of the workflow, meanwhile, final state
displays the final state of the workflow.
 Constraint is an extension mechanism that enables you to refine the semantics of
a UML model element.

Activity Diagram (Scrap App)

 Fig. 3.2.1 Activity Diagram

3.3.1 Sequence Diagram

Shows sequence of interactions between objects and flow of events in a single

use case.
 Focuses on message

details. Used more frequently in

industry.

SSD Notation

Actor represented by stick figure person (or role) that “Interacts” with system by
entering input data and receiving output data.

Object notation is rectangle with name of object underline shows

individual object and not class of all similar objects.

Lifeline is vertical line under object or actor to show passage of time for object.

Messages use arrows to show messages sent or recovered by actor or system.

Actor symbol

Object symbol

……………… Lifeline symbol

Sequence Diagram (Scrap App)

 Fig.3. 3.1 Sequence Diagram

3.4 WEB APLLICATION

1. BUS BOOKING LOGIN
PAGE(Screen Shot View)

2. BOOK PAGE
 3. HOME PAGE.

4.SCHEDULE PAGE
 6. BOOKED LIST PAGE

7.MAINTENANCE PAGE

8.AFTER SELECTING MAINTENACE OPTIONS ARE BOOK/LOACTION LIST

9. When Clicked On Location list .
10. ADMINISTRATOR OPTION SHOWS USERS, MANAGE
ACCOUNT AND LOGOUT.

4. Result and Analysis:

System Testing: (Software Testing Approach and Methodology)
Software testing is the process of evaluating the system by Manual or Automatic
System. Verifies the system satisfies the specified requirements or not. Identifies the
 differences between expected and actual results. Testing analyzes the entire system with the
intent of finding problems and errors that measures system functionalities and quality.
Testing includes inspection and structured peer reviews of requirements and design as well as
execution test of code.
The code developed during coding activity is likely to have some requirement
errors and design errors in addition to the errors introduced during the coding activity.
Testing performs a very critical role for quality assurance and for ensuring the reliability of
software. The system must be tested to evaluate the actual system functionality.

Levels of system testing:

1. Unit Testing: The module interface is tested to ensure that information properly flows into
and out of the program unit under test. The local data structure is examined to ensure that
data stored temporarily maintains its integrity during all steps in an algorithm's execution.
Boundary conditions are tested to ensure that the module operates properly at boundaries
established to limit or restrict processing. All independent paths (basis paths) through the
control structure are exercised to ensure that all statements in a module have been executed at
least once. And finally, all error handling paths are tested. Following are some types of errors
commonly found during unit testing

2. Integration Testing: Unit that otherwise seem to be working fine individually, starts causing
problems when integrated together. Data can be lost across an interface; one module can have
an inadvertent, adverse effect on another; sub-functions, when combined, may not produce
the desired major function; individually acceptable imprecision may be magnified to
unacceptable levels; global data structures can present problems.

Integration testing is a systematic technique for constructing the program

structure while at the same time conducting tests to uncover errors associated with
interfacing.

3. System testing: In this level of testing we are testing the system as a Whole after integrating
all the main modules of the project. We are testing whether system is giving correct output or
not. All the modules were integrated and the flows of information among different modules
were checked the flow of data is as per the requirements or not it was also checked that
whether any particular module is non - functioning or not i.e. once the integration is over
each and every module is functioning in its entirely or not.
In this level of testing we test the
following:- Whether all the forms are properly working
or not.
Whether all the forms are properly linked or not.
Whether all the images are properly displayed or
not. Whether data retrieval is proper or not.

4. Acceptance Testing: To verify that the system meets the user requirements, it is the system
testing performed by the customer him/herself after the product delivery, to determine
whether to accept or reject the delivered product. It is conducted by end user after system
testing through black box technique.
5. Regression Testing: Each time a new module is added as part of integration testing, the
software changes. New data flow paths are established, new I/O may occur, and new control
logic is invoked.
These changes may cause problems with functions that previously worked
flawlessly. In the context of an integration test strategy, regression testing is the re-
execution of some subset of tests that have already been conducted to ensure that
changes have not propagated unintended side effects. Regression testing is the activity
that helps to ensure that changes (due to testing or for other reasons) do not introduce
unintended behavior or additional errors.

Error Handling
An Exception occurs when a program encounter any unexpected problems. Such as running
out of memory or attempting to read from a file that no longer exists. These problems are not
necessarily caused by a programming error but they mainly occur because of violation of
assumption that you might have made about the execution environment. When a program
encounters an exception the default behavior is to throw the exception which generally
translates to abruptly, terminating the program after displaying an error message. But this is
not a characteristic of a robust application. But the best way is to bindle the exception
situations if possible, gracefully recover from them. This is called “exception handling”. I
used try, catch, finally and throw in my project to handle the exception.

(a) The Try Block:

Place the code that might cause exception in a try block. A typical try block looks
like this Try
{
//Code that may cause exception
}
A try block can have another try block inside when an exception occurs at any point rather
than executing any further lines of code, the CLR (Common Language Runtime)
Secures for the nearest try block that enclosure this code. This code. The control is
then passed to a matching catch block if any and then to the kindly block associated with this try
block.

(b) Catch Block:

There can be no of catch blocks immediately following a try block. Each catch
block handles an exception of a particular type. When an exception occurs in a statement
placed inside the try block the CLR looks for a mainly block that is capable of handling the
type of exception. (c) Throw block:
A throw statement explicitly generates an exception in code. You can throw when
a particular path in code results in an anomalous situation.

(d) Finally Block:

The finally block contains the code that always executes whenever or not any exception
occurs.

(e) Testing: Test Case Execution

 The workflow diagram below depicts the high level steps necessary to follow in
order to set up and execute test based on the Test Case Template.

Fig. 1.5 Test Case Diagram

Legend
1 – Railway Concession System Test Case Template.doc. The Test Case template used to
define and set up the Test Case Description.
2 – The test object specification provides a reference to the object subject to test or if required,
enter a copy of the object description excerpted from the object description for the test object.
When referenced, the reference should include at least :

(f) Debugging and Code Improvement

In ideal worlds, all programmers would be so skilled and attentive to detail that
they would write bug-free code. Unfortunately, we do not live in an ideal world. As such,
debugging, or tracking down the source of errors and erroneous result, is an important task
that all developers need to perform before they allow end-user to use their applications. We
will discuss some techniques for reducing the number of bugs in code up front.

(g) Checking three categories of bugs

i. Syntax error:
These errors occur when code breaks the rule of the language, such as visual
Basic sub statement without a closing End sub, or a forgotten closing curly braces ({}) in
java. Theses error the easiest to locate. The language complier or integrated development
environment (IDE) will alert you to them and will not allow you to compile your program
until you correct them.

ii. Semantic error

These errors occur in code that is correct according to rules of the compiler, but
that causes unexpected problems such as crashes or hanging on execution. A good example is
code that execute in a loop but never exists the loop, either because the loop depends on the
variable whose values was expected to be something different than it actually was or because
the programmer forget to increment the loop counter. Another category of errors in this area
includes requesting a field from a dataset, there is no way to tell if the field actually exists at
compile time. These bugs are harder to detect and are one type of running error.
 iii. Logic error
Logic errors are like semantic errors, logic errors are runtime error. That is, they
occur while the program is running. But unlike semantic errors, logic errors do not cause the
application to crash or hang. Logic error results in unexpected values or output. This can be a
result of something as simple as a mistyped variables name that happens to match another
declared variable in the program.

(h) Overview of Testing

i. System Testing:
System testing is the expensive and time-consuming process. There are two
strategies for testing software that we use for testing our system: Code Testing and
Specification Testing. In Code testing, we developed those cases to execute every instructions
and path in the program. In specification testing, we examined the program specification and
then wrote test data to determine how the program operates under specified condition.

Client Acceptance
Needs Testing

Requirements System
Testing

Design Integration

Code Unit Testing

Testing
ii. Defect Testing:
Defect testing is testing for situation where the program does not meet its
fictional specification. Performance testing tests a system's performance or reliability under
realistic loads. This may go some way to ensuring that the program meets its non-functional
requirements.

iii. Debugging:

Debugging is a cycle of detection, location, repair and test.

Debugging is a hypothesis testing process. When a bug is detected, the tester
must form a hypothesis about the cause and location of the bug. Further
examination of the execution of the program (possible including many returns
of it) will usually take place to confirm the hypothesis. If the hypothesis is
demonstrated to be incorrect, a new hypothesis must be formed. Debugging
tools that show the state of the program are useful for this, but inserting print
statements is often the only approach. Experienced debuggers use their
knowledge of common and/or obscure bugs to facilitate the hypothesis testing
process. After fixing a bug, the system must be reset to ensure that the fix has
worked and that no other bugs have been introduced. This is called regression
testing. In principle, all tests should be performed again but this is often too
expensive to do.

Test Report (Event Table)

TES TEST CASE ACTUAL

T EXPECTED OUTPUT RESUL
OUTPUT T
CAS
E
1. Login The seller should Login Passed
provide login credentials
credentials are
respectively and validated
they should be and verified.
authenticated
based on their
 authority.
2. Seller Registration The seller adds The seller is Passed
profile details should authenticated
be created in the and a new entry
database. in the database
is found.
3. View Cart Record View the items Items are Passed
added to the cart. successfully
viewed by the
seller.
4. View Order Status View the Order Order Status is Passed
Status successfully
viewed by the
Seller
5. Confirm Order Confirm the order It inserts the data in Passed
made by the seller database as Orders
and keep record.

Project Maintenance and Evaluation

The term maintenance covers virtually everything that happens to a system

delivery except total replacement or abandonment. Maintenance involves change to adapt to a
new environment, to adapt changing user requirements, and fixing problem as they occur or
are discovered.

Maintenance Activity:

⮚ Monitoring system performance.

 ⮚ Updating hardware and software.

⮚ Increasing the performance and maintaining the access controls.

Maintenance related responsibilities on the team:

⮚ The project team must visit the organization and implement changes. ⮚ The project

team must monitor system performance and system software.

5. Features and Applications

Our web application is a user-friendly, flexible and full featured web application
for booking the bus which allows the customer to book the bus tickets fast via E-
TICKETING which is very useful for the customers and best. It’s has also use database to
manage the no of tickets to be booked so that’s why it’s is very important to for the database
to be there. The process of booking the ticketing is very fast.
Apart from that, the web application would support strong user authentication
and quick transmission of data. It also enhances the speed of performing booking task easily.

Module Description

▪ Seller Details
This module helps to store the seller details such as name, email,
password.
 ▪ Order Add To Cart
This module used by seller to add a product into cart so that if
further seller wishes to buy them he/she can do so.

▪ Order Confirmed
This module used by seller to confirm selling the product that was
previously added into cart.

▪ Login
The login module is used for maintain security part of the project
using emailed and password.

▪ Order Status
This module is used for maintain show details of particular order
made by seller.

6. Limitations:
There are certain drawbacks related to app. One of the most basic aspects of app design, the
typeface selection for the text of the site, is also one of its most limiting design features. Not
every computer has the ability to display every font, and if the font you’ve chosen for your
site is not available for the viewer, an alternative will be displayed instead. This substitution
can cause distortions to appear in the viewer’s version, with misaligned text -- or just a subtly
different set of visual characteristics -- that can throw off the entire look of the site. Designers
can choose among the more common fonts available like Times New Roman or Arial to try to
remain within the limitations, or a designer can instead choose to invoke a programming
workaround, using JavaScript or Flash to display the font of choice.

7. Future Enhancement:
Since, most of activities are covered in the app the most important aspect of
including real-time order tracking where seller can easily track his/her orders so that it
becomes reliable to the user instead of continuously calling the shipping agent.
 8 Conclusion
We have successfully developed an WEB application which is very helpful to
reduce the communication and it’s very less time consuming difficulty between for buying
the tickets for bus . By developing an Web application that typically runs the server, and
allows the users to do things such as booking for in the catalog, you can also select the option
of you can book the bus ticketing via E-COMMERCE which will be helpful for the
passengers.

9 Bibliography

Books referred Authors

1. HTML,CSS Thomas A Powell
2. PHP Steven Holzner

3. MySQL Vikram Vasvani

Sites visited Topic
l. https://www.google.com/ Web application.
2. https://www.apachefriends.org/index.html Xampp server