1

(Online E-ticket Booking system)

Under Guidance Of
Prabir Sarkar
(Subject Matter Expert- PHP and Java)
A
Project Report
Submitted In Partial Fulfilment of the Requirements
For The Award Of the Degree
DIPLOMA IN COMPUTER SCIENCE AND TECHNOLOGY
Project Carried Out At

Gobindapur sephali Memorial Polytechnic

(AN ISO 9001:2008 CERTIFIED)
Submitted By
Avijit Ghosh
(Diploma In Computer Science and Technology)
Department Of Computer Science and Technology
Gobindapur sephali Memorial Polytechnic

(Note: All entries of the proforma of approval should be filled up with appropriate and complete
information. Incomplete proforma of approval in any respect will be summarily rejected.)
1. Title of the Project
2. Name of the Guide

: Railway Tourism(Online E-Ticket Booking System )

: Prabir Sarkar (Subject Matter Expert - PHP and Java)
: Prabir Sarkar (Department HOD)
Ph.D(Reg)*

M.Tech.*

MCA

M.Sc.*

MBA

B-Tech

3. Educational Qualification of the Guides :

Y

4. Working / Teaching experience of the Guides :

Prabir Sarkar (2years Experience in Web Page Development)

5. Software used in the Project

:
Dreamweaver CC 2015

PHP 5.5.12

Apache 2.4.9

MySql 5.6.17

Wampserver

Signature of the Student: 1.....................................

2....................................

Signature of the Guide.

Date:

3.....................................

Date:.......................

.................................................
signature,

For Office Use Only

Approved

Not Approved

Designation, Stamp of the Project Proposal Evaluator

Date: .

Project Responsibility Form

Railway Tourism (Online E-Ticket Booking System)

Group
No.

Sl .No.

Name of the Member

Responsibility

1.

Avijit Ghosh

Group leader, Coding,PPT

2.

Santosh Bhattacharya

Desigining

3.

Surya Sakhar Bhattacharya

Analysis , PPT & Testing

Each group member must participate in project developing the ideas for the required elements. Individual
group members will be responsible for completing tasks which help to finalized the project and the
performance. All group members must be assigned a task.

Self Certificate
This is to certify that the dissertation/project proposal entitled Railway Tourism (Online ETicket Booking system) is done by me, is an authentic work carried out for the partial
fulfillment of the requirements for the award of the degree of Master of Computer Application
by West Bengal University of Technology, under the guidance of Prabir Sarkar. The matter
embodied in this project work has not been submitted earlier for award of any degree to the
best of my knowledge and belief.
Name of the Student : Avijit Ghosh

Signature of the student :...............................................

Date.....................................

Certificate By Guide
This is to certify that this project entitled Railway Tourism (Online E-Ticket Booking system)
submitted in partial fulfilment of the degree of Diploma in Computer Science and
Technology by West Bengal State Council of Technical & Vocational Education and Skill
Devolopment through, Gobindapur Sephali Memorial Polytechnic done by Avijit Ghosh.
Students, Department of Computer Science and technology, Gobindapur Sephali Memorial
Polytechnic.
Is an authentic work carried out under my guidance & best of our knowledge and belief.

......................................
Signature of the student

.
Signature of the Guide(s)

Certificate of Approval
This is to certify that this documentation of Major project, entitled Railway Tourism (Online ETicket Booking System) is a record of bona-fide work, carried out by Avijit Ghosh under my
supervision and guidance.
In my opinion, the report in its present form is in fulfilment of all the requirements, as
specified by the West Bengal State Council of Technical Education & Vocational Education
and Skill Devolopment and as per regulations of the Gobindapur Sephali Memorial
Polytechnic. In fact, it has attained the standard, necessary for submission. To the best of my
knowledge, the results embodied in this report, are original in nature and worthy of
incorporation in the present version of the report for Diploma in Computer Science and
Technology.

----------------------------------External Examiner(s)

------------------------------------------------Head of the Department

Department of Computer Science and Technology
Gobindapur Sephali Memorial Polytechnic
Gobindapur, Keleti, Burdhwan
(An ISO 9001:2008 Certified)

( Affiliated to WBSCTE West Bengal )

Railway Tourism (online E-ticket booking System)

A Project Report submitted for the Approval of
Minor Project
In
Diploma in Computer Science and Technology (DCST)
By
Avijit Ghosh
Under The Guidance Of
Prabir Sarkar

Department Of Computer Science And Technology

Gobindapur Sephali Memorial Polytechnic
(Affiliated to WBSCTE)
Burdwan 713128
2016

Certificate Of The Project Work

This is to certify that Avijit Ghosh successfully completed the project titled " Online E-Ticket Booking System" under my
supervision during the period from July to August which is in partial fulfillment of requirements for the
award of the Diploma In Computer Science & Technology And Submitted to the Gobindapur Sephali
Memorial Polytechnic, Gobindapur is an authentic record of our own work carried out under the guidance
of Prabir Sarkar .The matter presented in this thesis has not been submitted by us for the award of any
other degree elsewhere.

..
Signature of the students

This to certify that the above made by the candidates is correct to the best of
my knowledge

Signature with date of External Examiner(s)

Signature with date of Project Guide(s)

Acknowledgement

We take this opportunity to express our profound gratitude and deep regards to our guide
Prabir Sarkar for his exemplary guidance, monitoring and constant encouragement throughout
the course of this project. The blessing, help and guidance given by him time to time shall
carry us a long way.
Lastly, we thank our friends for their constant encouragement without which this assignment
would not have been possible.

Submitted By :
Avijit Ghosh

10

Table of Contents
1. Abstract
2. Introduction
2.1 Relevance of the Topic
2.2 Problem Definition
2.3 Project Objective
3. Methodology

Page
No
6
6
6
6
6
7-8

4. System Analysis

8-15

4.1 Feasibility
4.2 Existing System
4.3 Proposed System
4.4 Data Flow Diagram
4.5 Use Case Diagram
4.6 Software Requirements
4.6.1 Front End
4.6.2 Middle End
4.6.3 Application Server
4.6.4 Database Server
4.6.7 Hardware Requirements
5. System Design
5.1 Database Design
5.1.1 ER Diagram
5.1.2 Normalization
5.2 Table Design

8-10
10
11
11-12
13-15
15
15
15
15
15
15
16-22
16-17
16
17
17-19

5.2.1 Table Definition

5.3 Form Design
5.3.1 Components of Form
5.4 Home Page
5.5Web Pages
6. Coding
6.1 Features of Coding
7.2 Coding

17-19
20
20
20
21-22
22
23
23

11

7.
8.
9.
10.
11.
12.
13.

Testing
Experimental Results
Contribution of the Work
Future Scope
Conclusion
Appendices
Bibliography

24
30
30
30
30
31
31

List Of Table
Serial_No.
1.
2.
3.
4.
5.

Table_Name
Credentials Table
User profile Table
Reservation Table
Payment Table
Booked Ticket Table

Section
5.2.1
5.2.1
5.2.1
5.2.1
5.2.1

Page_No
17
17
17-18
18
18

List Of Figures
Serial_No
1.
2.
3.
4.
5.

Figure_Name
DFD-level 0
DFD-level 1
Use Case Diagram for Admin
Use Case Diagram for Customer
ER diagram

Sections
4.4
4.4
4.5
4.5
5.1

Page_No
11
12
13
13
16

1.Abstract
The project planned to automate "Online E-Ticket Booking System" is a Railway Tourism Web application
intended to be used by user for ordering of Railway Tourism . The ordering mechanism is fairly easy as the
system becomes computerized.

1. Introduction
1.1 Relevance of the Topic
The project is very much relevant in todays world. Customers can very easily
Railway Tourism through the web portal.
1.2 Problem Definition
The project Online E-Ticket Booking System is surely going to make booking of
Ticket a lot easier. Users can now booking ticket from the comforts of their

12

1.3 Project Objective

To provide online ordering facilities
Support services in an integrated fashion so as to provide a simple and hassle free
ordering platform.
The system interacts to the users (User, admin) by means of some front-end form. To enter the system a login
form will appear where Email & Password, Username & Password for both Admins and for the Customers
will have to be entered to log into the system and then this will check the Type of that user. According to type
the System is loaded.
After login , User enters into their profile . Customer can check the E-ticket menu and Booking it.
After login , admin can enter into its profile. Admin can view the Train List, Payment Details and Booked
Ticket Details . Admin can also update/insert/view the details of Train and Ticket.
New users must have to register before log in.
Every stage data is stored in the database. This is why the system is very easy to use and every user can accept
the system by thinking its utility in present and by applying the idea of Prototyping Model the system can be
developed with more features in future.

2. Project Category
Web Application

3. Tools/Platform, Hardware and Software Requirement

Specification
Tools
1.
2.
3.
4.
5.

Adobe Dreamweaver. CC 2015

Apache 2.4.9
PHP 5.5.12
MySQL 5.6.17
Wampserver

Platform
1. Windows 7/8/10

13

Hardware Requirement Specification

Client Machine
HDD

200 MB

Server Machine
HDD

Processor

Intel Inside CORE Processor

i3 Processor

Memory

1 GB

Memory

320 GB
Dual Core
or Newer
Processor
4 GB

Software Requirement Specification

Client Machine

Server Machine

Browser

Any standard browser Software

with java script

Apache

Client Side
markup/scripting
languages

HTML, Java script

Database
Management
System Software

MySQL

Specification

MySQL-4.1

14
The prototyping paradigm begins with requirements gathering. Developer and customer meet and define the
overall objectives for the software, identify whatever requirements are known, and outline areas where further
definition is mandatory. A "quick design" then occurs. The quick design focuses on a representation of those
aspects of the software that will be visible to the customer/user (e.g., input approaches and output formats).
The quick design leads to the construction of a prototype. The prototype is evaluated by the customer/user
and used to refine requirements for the software to be developed. Iteration occurs as the prototype is tuned to
satisfy the needs of the customer, while at the same time enabling the developer to better understand what
needs to be done.
Ideally, the prototype serves as a mechanism for identifying software requirements. If a working prototype is
built, the developer attempts to use existing program fragments or applies tools (e.g., report generators,
window managers) that enable working programs to be generated quickly.

5. System Analysis
5.1 Feasibility Study
An important outcome of preliminary investigation is to find that the system feasible or not. The feasibility of
a project for the system development process is thoroughly examined during system investigation stages.
FEASIBILITY STUDY is a test of system proposal according to its workability, impact of the organization,
ability to meet needs and effective use of the resources. The feasibility study can be addressed by answering
the following question.

i)
ii)
iii)
iv)

What resources available for the given system?

What are the risks involved in the system?
What are the impacts of the system on the organization?
Is the problem associated with a system worth solving?

6. Purpose of the Feasibility Study

The feasibility study is conducted to assist the decision-makers in making the decision that will be in
the best interest of the system. The extensive research, conducted in a non-biased manner, will provide
data upon which to base a decision.
It is defined as an evaluation or analysis of the potential impact of a proposed project or program.
A feasibility study is conducted to assist decision-makers in determining whether or not to implement a
particular project or program. The feasibility study is based on extensive research on both the current
practices and the proposed project/program and its impact on the school foodservice operation.
Types of Feasibility Study:
There are five types of Feasibility study needs to develop a project. The acronym TELOS refers to the five
areas of this feasibility - Technical, Economic, Logical, Operational, and Scheduling.

6.1.1. Technical Feasibility:

This is concerned with specifying equipment and software that will successfully satisfy the user requirement.
This evaluation determines whether the technology needed for the proposed system is available or not.

15
Technical Feasibility Study can answered the following question
i)
ii)
iii)

Can the all work of the project be done with equipment?

Can the system be upgraded if required?
Can a solution be supported with existing technology?

This Portal is being developed using PHP 5.5.12, MySQL 5.6.17.

6.1.2. Economic Feasibility:

Economic justification is generally the Bottom Line consideration for most systems. Economic justification
includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the
benefits associated with the system. The purpose of the economic feasibility assessment is to determine the
positive economic benefits to the organization that the proposed system will provide. It includes quantification
and identification of all the benefits expected.
The financial and the economic questions during the preliminary investigation are verified to estimate the
following:
i)
The cost to conduct a full system investigation.
ii)
The cost of hardware and software for the class of application being considered.
iii)
The benefits in the form of reduced cost.
This feasibility checks whether the system can be developed with the available funds. The Online E-Ticket
Booking System does not require much amount of money to be developed. This can be done economically if
all execute in a planned manner, so it is economically feasible.

6.1.3 Logical Feasibility:

It checks that the system is logically correct or not. The system should not contain any unnecessary logical
constraints that are not in requirement specification. It should help user to understand easily the function of
the system.

6.1.4 Operational Feasibility:

It is mainly related to human organizations and political aspects. It is a measure of how well a proposed system
solves the problems, and takes advantage of the opportunities identified during scope definition and how it
satisfies the requirements identified in SRS. The points which are considered are:
i)
ii)
iii)

What changes will be brought with the system?

What new skills will be required?
Do the existing staff members have these skills? If not, can they be trained in due course of
time?
It fulfills all the aspect of operational feasibility study as all the member of the project is well skilled, and there
are no organizational and political constraints.

16

6.1.5 Schedule Feasibility:

Time evaluation is the most important consideration in the development of project. The time schedule
required for the developed of this project is very important since more development time effect machine time,
cost and cause delay in the development of other systems.

Feasibility Study

Technical Feasibility

Economic
Feasibility

Logical
Feasibility

Operational
Feasibility

Schedule
Feasibility

Figure: Feasibility Study

1.

Existing System
The existing system is not digital. A User has to physically go and Booking ticket.

7.1 Proposed system

The proposed system is fully digital. A customer does not need to visit for booking Ticket . User
can booking a Ticket even from email by visiting the website

7.2 Data Flow Diagram

Context Analysis Diagram (Level 0 DFD):

17

Figure 1: DFD-Level

New User Registration

18

Use Case Descriptions for Login Operation for all users

USE CASE #

AA-001 Login

Goal

All users logging into the system should be authenticated using a

unique login-id and password (operations to be supported based
on type of user)

Preconditions

If the user type is Admin, credential details should exist.

If the user type is Customer, he/she should be registered by the
administrator.

19
8.

Success End Condition

If the user type is Admin, then redirect to the Admin page.

If the user type is User, then redirect to the Customer page.

Failed End Condition

The end user is redirected to an Error Page, and/or is asked to

re-enter login credentials.

Primary, Secondary Actors

Admin, User.

Trigger

Login button

Login:

DESCRIPTION

Related
Information/Use cases
Priority
Performance
Frequency
Assumptions

Step
1
2
3

Action

Step
1

Branching Action

Enter Login credentials (id & password)

Click on Login button
If id & password is Success, then identify user type
Display appropriate(Admin/User) home page

If 'id' is not existing then return with requesting for

registration
2
If password is not matching return with suitable error
message say 'Re-enter id & password'
Not Applicable
P1
5 seconds
10 / hour
Admin/User login credentials are available in the database and
others are already registered with their credentials

20

Use Case Descriptions for ADD Food Details Operation for Admin only
USE CASE #
Goal
Preconditions

AD-001 The admin should be able to modify food items details

Success End Condition

Redirect to Admin home page

Failed End Condition

Primary, Secondary Actors

"Redirect to Error Page"

Administrator

Trigger
DESCRIPTION

'Add train button

Related
Information/Use cases
Priority
Performance
Frequency
Assumptions

To enable Administrator to create and add new train details

Administrator must be logged in to be able to create a new train.

Step
1
2
Step
1
2

Action

Provide appropriate train details

Click on Add train button
Branching Action

If failed to add train details

Display appropriate message to the admin
Not applicable
P1
Approx. 4 sec
2 / Month
Admin login credentials are available in the database

21

9. System Design
ER Diagram

Normalization :
All the tables are normalized up to 3NF.

22

9.2 Table Design

9.2.1 Table Definition

1. Table:
CREDENTIALS
This table contains Authentication Information for Administrator & User
Field Name
Data Type
Description
User id *
VARCHAR2(6)
Foreign Key*
Password
VARCHAR2(20)
Not Null
User type
VARCHAR2(1)
Either ['A,'C']
Login status
NUMBER(1)
Either [1 ,0]
* Id is an auto generated number .
2. Table:
USERPROFILE
This table contains User specific details entered during User Registration.
Field Name

Data Type
Id*
VARCHAR2(50)
Name
VARCHAR2(50)
Email
VARCHAR2(50)
Password
VARCHAR(50)
Address
VARCHAR2(50)
Pincode
VARCHAR2(30)
Gender
VARCHAR2(15)
Date of Birth
VARCHAR2(50)
* Id is an auto generated number .

Description
Primary Key
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null

2. Table:
Ticket
This table contains Food specific information.
Field Name
Data Type
Transaction Id*
VARCHAR2(50)
Name
VARCHAR2(50)
PNR
VARCHAR2(50)
Confirm
VARCHAR2(50)
Quantuty
NUMBER(50)
Price
NUMBER(50)
* Id is an auto generated number .

Description
Primary Key
Not Null
Not Null
Not Null
Not Null

23

4. Table:
Booked Ticket History
This table contains Order details like Name, address , License number etc.
Field Name

Data Type

Description

Transaction id*

VARCHAR2(50)

Primary Key

UserID

VARCHAR2(25)

Foreign Key

PNR

VARCHAR2(30)

Foreign Key

Booked Date

VARCHAR2(15)

Not Null

Reservation Status

VARCHAR2(15)

Foreign Key

* Id is an auto generated number .

5. Table:
Train Details
This table contains details about route, distance, duration etc.
Field Name
Train Number
Train Name
Source Station
Destination Station
Arrival Time
Depart Time
* Id is an auto generated number .

Data Type
VARCHAR2 (100)
VARCHAR2(100)
VARCHAR2 (100)
VARCHAR2 (100)
VARCHAR(100)
INT(100)

Description
Primary Key
Not Null
Not Null
Not Null
Not Null
Not Null

24

9.3 Form Design

9.3.1 Components of Form
HTLM - 5

9.4 Home Page

9.4.1 Links and Web Pages

User Registration:

25

9.4.2 Reservation Page

such as the following:

These Style sheets represent a major breakthrough for Web page designers, expanding their ability to improve
the appearance of their pages. In the scientific environments in which the Web was conceived, people are
more concerned with the content of their documents than the presentation. As people from wider walks of life
discovered the Web, the limitations of HTML became a source of continuing frustration and authors were
forced to sidestep HTML's stylistic limitations. While the intentions have been good -- to improve the
presentation of Web pages -- the techniques for doing so have had unfortunate side effects techniques work
for some of the people, some of the time, but not for all of the people, all of the time. They include:
Using proprietary HTML extensions
Converting text into images
Using images for white space control

26
Use of tables for page layout
Writing a program instead of using HTML

These techniques considerably increase the complexity of Web pages, offer limited flexibility, suffer from
interoperability problems, and create hardships for people with disabilities.
JavaScript Features
In this JavaScript tutorial, you will learn about features of JavaScript, JavaScript as a programming tool,
dynamic effects, browser detection, DOM control and other popular JavaScript features.
A Great Programming Tool for HTML
Professional Web designers are undoubtedly adept in using HTML and proficient in website design but not
necessarily skillful in computer programming. JavaScript is a programming tool for such a situation. JavaScript
is a powerful scripting language that helps HTML designers to effectively and interactively design websites and
web pages in a very simple and efficient way.
Handles Dynamic Effects
JavaScript is such a powerful scripting language which has features to achieve dynamic effects in web pages.
Using the features available in JavaScript, the designer can decide to have dynamically placed text at run time.
Browser Detection
One of the powerful feature of JavaScript is its ability to detect client browser. Browser detection feature of
JavaScript helps to achieve independent platforms. JavaScript can detect the type of browser the visitor is using
and programmatically switch the page to show customized pages designed for different browsers. Thus by
making use of browser detection feature of JavaScript, the designer gets better control over the browser.
Saves Time
JavaScript also has the feature of validating data submitted at the client level. This helps in saving the
processing time of the server because JavaScript initially creates the validation on the client side.6.2 Coding

11. Testing

Team Interaction

The following describes the level of team interaction necessary to have a successful product.
The Test Team will work closely with the Development Team to achieve a high quality design and
user interface specifications based on customer requirements. The Test Team is responsible for
visualizing test cases and raising quality issues and concerns during meetings to address issues early
enough in the development cycle.
The Test Team will work closely with Development Team to determine whether or not the
application meets standards for completeness. If an area is not acceptable for testing, the code
complete date will be pushed out, giving the developers additional time to stabilize the area.

27

Since the application interacts with a back-end system component, the Test Team will need to include
a plan for integration testing. Integration testing must be executed successfully prior to system testing.

Test Objective
The objective our test plan is to find and report as many bugs as possible to improve the integrity of our
program. Although exhaustive testing is not possible, we will exercise a broad range of tests to achieve our
goal. We will be testing a Binary Search Tree Application utilizing a pre-order traversal format. There will be
eight key functions used to manage our application: load, store, clear, search, insert, delete, list in ascending
order, and list in descending order. Our user interface to utilize these functions is designed to be user-friendly
and provide easy manipulation of the tree. The application will only be used as a demonstration tool, but we
would like to ensure that it could be run from a variety of platforms with little impact on performance or
usability.

Process Overview

The following represents the overall flow of the testing process:

1. Identify the requirements to be tested. All test cases shall be derived using the current Program
Specification.
2. Identify which particular test(s) will be used to test each module.
3. Review the test data and test cases to ensure that the unit has been thoroughly verified and that the test
data and test cases are adequate to verify proper operation of the unit.
4. Identify the expected results for each test.
5. Document the test case configuration, test data, and expected results.
6. Perform the test(s).
7. Document the test data, test cases, and test configuration used during the testing process. This
information shall be submitted via the Unit/System Test Report (STR).
8. Successful unit testing is required before the unit is eligible for component integration/system testing.
9. Unsuccessful testing requires a Bug Report Form to be generated. This document shall describe the
test case, the problem encountered, its possible cause, and the sequence of events that led to the
problem. It shall be used as a basis for later technical analysis.
10. Test documents and reports shall be submitted. Any specifications to be reviewed, revised, or updated
shall be handled immediately.

28

Testing Process

b. Design
System Test
a. Organize
Project

c.
Design/Build
Test Proc.
d. Organize
Project

e.
Design/Build
Test Proc.

f. Signoff

The diagram above outlines the Test Process approach that will be followed.

a. Organize Project involves creating a System Test Plan, Schedule & Test Approach, and assigning
responsibilities.
b. Design/Build System Test involves identifying Test Cycles, Test Cases, Entrance & Exit Criteria, Expected
Results, etc. In general, test conditions/expected results will be identified by the Test Team in conjunction
with the Development Team. The Test Team will then identify Test Cases and the Data required. The
Test conditions are derived from the Program Specifications Document.
c. Design/Build Test Procedures includes setting up procedures such as Error Management systems and
Status reporting.
d. Build Test Environment includes requesting/building hardware, software and data set-ups.
e. Execute System Tests The tests identified in the Design/Build Test Procedures will be executed. All
results will be documented and Bug Report Forms filled out and given to the Development Team as
necessary.
f. Signoff - Signoff happens when all pre-defined exit criteria have been achieved.

Testing Strategy
The following outlines the types of testing that will be done for unit, integration, and system testing. While it
includes what will be tested, the specific use cases that determine how the testing is done will be detailed in the
Test Design Document. The test cases that will be used for designing use cases is shown in Figure below.

29

Test Case
Tested By:
Test Type
Test Case Number
Test Case Name
Test Case Description

Surya Sakhar Bhattacharya

Unit Testing
1
User Identification
The user should enter his/ her accurate Email and password so
that he/she can able to go for the further options. The test case
will check the application for the same since a user can only
login with the correct Email, Password.

Item(s) to be tested
1

Verification of the Email and Password with the record in the database.

Specifications
Input
1) Correct Email and Password

Expected
Output/Result
1) Successful login

2) Incorrect Email or Password

2) Failure Message

30
Tested By:
Test Type
Test Case Number
Test Case Name
Test Case Description

Santosh Bhattacharya
Unit Testing
2
Booking Identification

User submitted booking Details for Ticket

Item(s) to be tested
1

Verification of the all information is filled up.

Specifications
Expected
Input
Output/Result
3) Correct order id, Location and Pin 3) Booking Successful.
code.
4) Incorrect order id, Location and Pin 4) Failure Message
code.

Unit Testing
Unit Testing is done at the source or code level for language-specific programming errors such as bad syntax,
logic errors, or to test particular functions or code modules. The unit test cases shall be designed to test the
validity of the programs correctness.

White Box Testing

In white box testing, the UI is bypassed. Inputs and outputs are tested directly at the code level and the results
are compared against specifications. This form of testing ignores the function of the program under test and
will focus only on its code and the structure of that code. Test case designers shall generate cases that not only
cause each condition to take on all possible values at least once, but that cause each such condition to be
executed at least once. To ensure this happens, we will be applying Branch Testing. Because the functionality
of the program is relatively simple, this method will be feasible to apply.
Each function of the binary tree repository is executed independently; therefore, a program flow for each
function has been derived from the code.

31

Black Box Testing

Black box testing typically involves running through every possible input to verify that it results in the right
outputs using the software as an end-user would. We have decided to perform Equivalence Partitioning and
Boundary Value Analysis testing on our application.

System Testing
The goals of system testing are to detect faults that can only be exposed by testing the entire integrated system
or some major part of it. Generally, system testing is mainly concerned with areas such as performance,
security, validation, load/stress, and configuration sensitivity. But in our case well focus only on function
validation and performance. And in both cases we will use the black-box method of testing.
12. Experimental Results
Results turned out to be successfully and the project is fully functional as all the methods are working fine .
13.System Security measure(Implementation of security for the Project developed):
Only authorized users are allowed.
Without signing in users are not allowed to go an intermediate page by typing an URL.
For all such efforts. Users will be redirected to the homepage.

14. Database/Data security:

Database is present in remote machine.
Oracles default security are applied.

15. Creation of user profiles and access rights

The admin cant booking ticket manually.
The admin can create more admin.

16. Future scope and further enhancement of the Project

Railway Toursiam has lot of enhancement options. In future documents may be classified category-wise. It
may try to analysis the user behaviour and preferences and according suggest document categories. All
concepts can be applied to make intelligent.

17. Conclusion
This new system is surely to benefit the user and let the user book a ticket in a much faster and
efficient way.