Professional Documents
Culture Documents
(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
M.Tech.*
MCA
M.Sc.*
MBA
B-Tech
PHP 5.5.12
Apache 2.4.9
MySql 5.6.17
Wampserver
3.....................................
Date:.......................
.................................................
signature,
Approved
Not Approved
Date: .
Group
No.
Sl .No.
Responsibility
1.
Avijit Ghosh
2.
Santosh Bhattacharya
Desigining
3.
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
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)
..
Signature of the students
This to certify that the above made by the candidates is correct to the best of
my knowledge
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
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
2. Project Category
Web Application
Platform
1. Windows 7/8/10
13
200 MB
Server Machine
HDD
Processor
Memory
1 GB
Memory
320 GB
Dual Core
or Newer
Processor
4 GB
Server Machine
Browser
Apache
Client Side
markup/scripting
languages
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)
15
Technical Feasibility Study can answered the following question
i)
ii)
iii)
16
Feasibility Study
Technical Feasibility
Economic
Feasibility
Logical
Feasibility
Operational
Feasibility
Schedule
Feasibility
1.
Existing System
The existing system is not digital. A User has to physically go and Booking ticket.
17
Figure 1: DFD-Level
18
AA-001 Login
Goal
Preconditions
19
8.
Admin, User.
Trigger
Login button
Login:
DESCRIPTION
Related
Information/Use cases
Priority
Performance
Frequency
Assumptions
Step
1
2
3
Action
Step
1
Branching Action
20
Use Case Descriptions for ADD Food Details Operation for Admin only
USE CASE #
Goal
Preconditions
Trigger
DESCRIPTION
Related
Information/Use cases
Priority
Performance
Frequency
Assumptions
Step
1
2
Step
1
2
Action
21
9. System Design
ER Diagram
Normalization :
All the tables are normalized up to 3NF.
22
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
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
25
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
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
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) Failure Message
30
Tested By:
Test Type
Test Case Number
Test Case Name
Test Case Description
Santosh Bhattacharya
Unit Testing
2
Booking Identification
Item(s) to be tested
1
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.
31
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.
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.