Electronic Chart for Indian Railways

AbstractIndian Railway (IR), one of the worlds largest railway network has
sophisticated and modern facilities for handling ticket reservation process. But the
reservation chart used for passenger verication and attendance marking carried by
TTE is printed on paper. This proposal tries to replace the existing paper chart with a
handheld device. Since chart printing holds the major share of paper usage in IR,
introduction of this idea in IR can reduce the amount of paper used by a
considerable amount. The device can be used to perform the operations like
attendance marking, ticket cancellation, etc. The device can communicate
wirelessly with the server through stations and thus the changes in the chart can be
updated at both the server and the device. This can help the user to get the live
status of seat availability. A prototype of the proposed system is implemented using
TMDSSK3358 evaluation module from Texas Instruments.
Introduction

Railway (IR) is one of the worlds largest railwaynetworks and runs through the
length and breadth of thecountry. IR carried 8224 million people in the financial
year2011-12 [1]. Table I showing the annual volume of traffichandled by IR in the
last four years also shows that the volumeof traffic is increasing with year and this
trend is going to beprevailing. Handling of such a large number of reservations
andticketing operations is a tedious task. Indian Railways and itssubsidiary Indian
Railway Catering and Tourism Corporation(IRCTC) handles the ticketing
operations. These operationsproduce a Reservation Chart for each journey of a
train.
Reservation chart for a journey is the list of people who hasreserved a ticket for the
journey. This includes list of confirmedpassengers, passengers belonging to
Waiting List (W/L) andReservation-Against-Cancellation (RAC) categories. The
chartwill be holding information related to the passenger like age,gender, ID card
number, reservation status, berth number,compartment, boarding station,
destination, etc. The TravellingTicket Examiner (TTE) obtains the chart from the
startingstation of the train. TTE carries this paper chart and usesit for passenger
verification, attendance marking, reportingcancellation and upgrading the ticket
against cancellation.Since there can be changes in the chart even after the train
hasstarted, the charts need to be updated in between the journey.The printout of the
updated chart is taken from in betweenstations and is handed over to the TTE. This
is a commonscenario found in long-route trains.In appearance, reservation chart is
a paper bundle of about70 pages. The copies of chart can be foundin the hands of
a TTE, at the starting and other main stations of the journeyand on the train next to
carriage doors. In December 2010, IRdecided to implement the five-digit train
numbering schemebecause the then existing one (four-digit numbering scheme)

had exhausted as there are more than 10,000 trains runningevery day [2]. Out of
which 7000 train are passenger trains.The trains with reservation facility has to
take print out of atleast3-5 copies of the chart for a journey. Hence the dailypaper
usage for chart print-out is more than 10 lakh sheetswhich is approximately
equivalent to 10 pine trees accordingto statistics shown in [3].Figure 1 is a screen
shot taken from IRCTC website. Thisis an appeal from IR to the passengers not to
take the printout of the Electronic Reservation Slip (ERS) by doing whichcan save
3 lakhs of A4 paper a day. This shows the goodintention of IR to reduce paper
usage. But IR cannot makeall the passengers to use Virtual Reservation Message
(VRM)instead of paper print-out. Instead they can lead the way byreplacing their
chart completely by some other eco-friendlysystem. Since the amount of paper
used for chart is more thanthat used for ERS, it would be more paper saving if IR
doesthis.According to railway rules, the hard copy of the reservationchart must be
stored for atleast 6 months. In case of anydispute related with reservation or
journey, the chart has to
be stored till it is resolved. Hence the storage of hard copy isanother issue
associated with the reservation chart. Currently,the upgrading of seat from RAC or
W/L category is solelydecided by the TTE. This is done manually and hence
errorscan occur in the process. Also the TTE has to find out thatpassenger to
inform about the upgradation. At present oncethe chart is prepared, there will not
be any change in seatavailability shown in the IR or IRCTC website.The above
mentioned disadvantages in the existing systemmotivated to think about an
electronic charting system. In theproposed system, the chart is kept at the central
railway serverand is accessed by the TTE through a handheld portable device.Since
this device replaces the paper chart, a huge amount ofpaper can be saved.
LITERATURE SURVEY

In appearance, reservation chart is a paper bundle of about 70 pages. The

copies of chart canbe found in the hands of a TTE, at the starting and other
main stations of the journey and onthe train next to carriage doors. In
JANUARY 2015, IR decided to implement the ve-digittrain numbering scheme
because the then existing one (four-digit numbering scheme) hadexhausted
as there are more than 10,000 trains running every day.

Out of which 7000 train are passenger trains. The trains with reservation
facility have to take print out of at least 3-5 copies of the chart for a journey.
Hence the daily paper usage for chart print-out is more than10 lakh sheets
which is approximately equivalent to 10 pine trees.

EXISTING SYSTEM DISADVANTAGES

The disadvantages in the existing system motivated to think about an

electronic charting system.

In the proposed system, the chart is kept at the central railway server and is
accessed by the TTE through a handheld portable device.

Since this device replaces the paper chart, a huge amount of paper can be
saved.

DISADVANTAGES

In manually update errors can occur in the process.

At present once the chart is prepared, there will not be any change in seat
availability shown in the IR or IRCTC website.

Drastically use of paper

Proposed System
The proposed system is a battery operated handheld portable device meant to
replace
the
existing
paper
chart.
In
the
same
wayastheexistingpaperchartsystem,theTTEgetsthee-chart from the starting station
of the journey and he/she carries it throughout the journey. With the help of this
device, the TTE can access the chart, view the list of passengers in a better way
than its paper alternative. The normal chart operations such as reporting passenger
status, passenger identity verication, cancelling a passenger, ne collection, etc,
can be performed on the device in an easier way. It has option to view the chart in
different ways which can help the TTE to make his job fast and efcient. This device
also incorporates the option to view the photo of those passengers who has
registered their photo on the railway web site. This helps those passengers to
remove the burden of carrying an identity card while travelling. This device can
dynamically update the chart in it to sync device with the updates happened on the
server. Also the operations done on the chart in the device are reported to the
central server. This communication between the server and the device happens at
railway stations with the help of wireless access points kept there. Since the device
and the server are connected only at the stations, the operations happening on the
chart
are
recorded
at
both
the
ends
and
are
communicatedtoeachotheroncetheconnectionisestablished.
Ticket
cancellation,
which can be done from both the server as well as the device, reported on the the
server will be conrmed only after getting message from the device saying that the
passenger is not on board. Figure 3 shows the simplied server - E-chart
communication. The central server is the place where the charts of all the trains as
well as the user data are stored. At the start of the journey, the reservation chart of
the corresponding train is downloaded to the device from the server. The server
does auto upgrading of passengers on cancellation of another passenger who has a
conrmed ticket or whose position is higher in the chart. Along with auto upgrading,
both the cancelled passenger as well as the passenger whose class of journey has
changed on upgrading will be informed personally, through Short Message
Service(SMS). E-chartworksbytakingpowerfromtherechargeablebattery included in
the system. A charger along with the system can be used for charging this battery

from an AC supply. Since trains have plug points for mobile charging the same can
be used for charging e-chart also.
ADVANTAGES

Dynamic update

No wastage of paper

More efficient and effective

SYSTEM STUDY

2.1 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is
put forth with a very general plan for the project and some cost estimates.
During system analysis the feasibility study of the proposed system is to be
carried out. This is to ensure that the proposed system is not a burden to the
company. For feasibility analysis, some understanding of the major
requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

 ECONOMICAL FEASIBILITY
TECHNICAL FEASIBILITY
SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that

the system will have on the organization. The amount of fund that
the company can pour into the research and development of the
system is limited. The expenditures must be justied. Thus the
developed system as well within the budget and this was
achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY

This study is carried out to check the technical

feasibility, that is, the technical requirements of the system. Any
system developed must not have a high demand on the available
technical resources. This will lead to high demands on the
available technical resources. This will lead to high demands
being placed on the client. The developed system must have a
modest requirement, as only minimal or null changes are required
for implementing this system.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of

the system by the user. This includes the process of training the
user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity.
The level of acceptance by the users solely depends on the

methods that are employed to educate the user about the system
and to make him familiar with it. His level of condence must be
raised so that he is also able to make some constructive criticism,
which is welcomed, as he is the nal user of the system.

INPUT DESIGN
The input design is the link between the information
system and the user. Itcomprises the developing
specication and procedures for data preparation and
those stepsare necessary to put transaction data in to a
usable form for processing can be achieved byinspecting
the computer to read data from a written or printed
document or it can occur byhaving people keying the
data directly into the system. The design of input focuses
oncontrolling the amount of input required, controlling the
errors, avoiding delay, avoidingextra steps and keeping
the process simple. The input is designed in such a way
so that itprovides security and ease of use with retaining
the privacy. Input Design considered thefollowing things:
What data should be given as input?
How the data should be arranged or coded?
The dialog to guide the operating personnel in
providing input.
Methods for preparing input validations and steps to
follow when error occur.

OBJECTIVES

1.Input Design is the process of converting a useroriented description of the inputinto a computer-based
system. This design is important to avoid errors in the
datainput process and show the correct direction to the
management for getting correctinformation from the
computerized system.
2.It is achieved by creating user-friendly screens for the
data entry to handle largevolume of data. The goal of
designing input is to make data entry easier and to befree
from errors. The data entry screen is designed in such a
way that all the datamanipulates can be performed. It
also provides record viewing facilities.
3.When the data is entered it will check for its validity.
Data can be entered with thehelp of screens. Appropriate
messages are provided as when needed so that the user
will not be in maize of instant. Thus the objective of input
design is to create aninput layout that is easy to follow
OUTPUT DESIGN
A quality output is one, which meets the requirements of
the end user andpresents the information clearly. In any
system results of processing are communicated tothe
users and to other system through outputs. In output
design it is determined how theinformation is to be
displaced for immediate need and also the hard copy
output. It is themost important and direct source
information to the user. Efficient and intelligent

outputdesign improves the systems relationship to help

user decision-making.
1.Designing computer output should proceed in an
organized, well thought outmanner; the right output must
be developed while ensuring that each output elementis
designed so that people will nd the system can use
easily and effectively. Whenanalysis design computer
output, they should Identify the specic output that
isneeded to meet the requirements.
2.Select methods for presenting information.
3.Create document, report, or other formats that contain
information produced by thesystem.
The output form of an information system should
accomplish one or more of thefollowing objectives.
Convey information about past activities, current
status or projections of the
Future.
Signal important events, opportunities, problems, or
warnings.
Trigger an action.
Conrm an action.
Architectural Design

USE CASE DIAGRAM

SEQUENCE DIAGRAM

A Sequence diagram is an interaction diagram that shows how processes operate with
one another and in what order. It is a construct of a Message Sequence Chart. A sequence
diagram shows object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. Sequence diagrams are typically associated with use
case realizations in the Logical View of the system under development. Sequence diagrams are
sometimes called event diagrams or event scenarios.
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the

order in which they occur. This allows the specification of simple runtime scenarios in a
graphical manner.

Data flow diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a preliminary step
to create an overview of the system, which can later be elaborated. DFDs can also be used for the
visualization of data processing (structured design).
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).

Software Environment

Java Technology
Java technology is both a programming language and a
platform.

The Java Programming Language

The Java programming language is a high-level language that can be
characterized by all of the following buzzwords:

 Simple
Architecture neutral
Object oriented
Portable
Distributed
High performance
Interpreted
Multithreaded
Robust
Dynamic
Secure

With most programming languages, you either compile or interpret a

program so that you can run it on your computer. The Java programming language
is unusual in that a program is both compiled and interpreted. With the compiler,
first you translate a program into an intermediate language called Java byte codes
the platform-independent codes interpreted by the interpreter on the Java
platform. The interpreter parses and runs each Java byte code instruction on the
computer. Compilation happens just once; interpretation occurs each time the
program is executed. The following figure illustrates how this works.

You can think of Java byte codes as the machine code

instructions for the Java Virtual Machine (Java VM). Every Java
interpreter, whether its a development tool or a Web browser
that can run applets, is an implementation of the Java VM. Java
byte codes help make write once, run anywhere possible. You
can compile your program into byte codes on any platform that
has a Java compiler. The byte codes can then be run on any
implementation of the Java VM. That means that as long as a
computer has a Java VM, the same program written in the Java
programming language can run on Windows 2000, a Solaris
workstation, or on an iMac.

The Java Platform

A platform is the hardware or software environment in
which a program runs. Weve already mentioned some of the
most popular platforms like Windows 2000, Linux, Solaris,
and

MacOS.

Most

platforms

can

be

described

as

combination of the operating system and hardware. The Java

platform differs from most other platforms in that its a
software-only platform that runs on top of other hardwarebased platforms.
The Java platform has two components:
The Java Virtual Machine (Java VM)
The Java Application Programming Interface (Java API)
Youve already been introduced to the Java VM. Its the
base for the Java platform and is ported onto various
hardware-based platforms.
The Java API is a large collection of ready-made software components
that provide many useful capabilities, such as graphical user interface (GUI)
widgets. The Java API is grouped into libraries of related classes and
interfaces; these libraries are known as packages. The next section, What
Can Java Technology Do? Highlights what functionality some of the
packages in the Java API provide.

The following figure depicts a program thats running on the Java

platform. As the figure shows, the Java API and the virtual machine insulate
the program from the hardware.

Native code is code that after you compile it, the compiled code runs on a
specific hardware platform. As a platform-independent environment, the Java
platform can be a bit slower than native code. However, smart compilers, welltuned interpreters, and just-in-time byte code compilers can bring performance
close to that of native code without threatening portability.

What Can Java Technology Do?

The most common types of programs written in the Java
programming language are applets and applications. If
youve surfed the Web, youre probably already familiar with
applets. An applet is a program that adheres to certain
conventions that allow it to run within a Java-enabled
browser.
However, the Java programming language is not just for writing cute,
entertaining applets for the Web. The general-purpose, high-level Java
programming language is also a powerful software platform. Using the
generous API, you can write many types of programs.

An application is a standalone program that runs directly on the Java

platform. A special kind of application known as a server serves and
supports clients on a network. Examples of servers are Web servers, proxy
servers, mail servers, and print servers. Another specialized program is a
servlet. A servlet can almost be thought of as an applet that runs on the
server side. Java Servlets are a popular choice for building interactive web
applications, replacing the use of CGI scripts. Servlets are similar to applets
in that they are runtime extensions of applications. Instead of working in
browsers, though, servlets run within Java Web servers, configuring or
tailoring the server.
How does the API support all these kinds of programs? It does so with
packages of software components that provides a wide range of
functionality. Every full implementation of the Java platform gives you the
followingfeatures:
The essentials: Objects, strings, threads, numbers,
input and output, data structures, system properties,
date and time, and so on.
Applets: The set of conventions used by applets.
Networking:

URLs,

TCP

(Transmission

Control

Protocol), UDP (User Data gram Protocol) sockets, and

IP (Internet Protocol) addresses.
Internationalization: Help for writing programs that
can be localized for users worldwide. Programs can
automatically adapt to specic locales and be displayed
in the appropriate language.

 Security: Both low level and high level, including

electronic

signatures,

public

and

private

key

management, access control, and certicates.

Software components: Known as JavaBeansTM, can
plug into existing component architectures.
Object serialization: Allows lightweight persistence
and communication via Remote Method Invocation
(RMI).
Java

Database

Connectivity

(JDBCTM):

Provides

uniform access to a wide range of relational databases.

The Java platform also has APIs for 2D and 3D graphics,
accessibility,

servers,

collaboration,

telephony,

speech,

animation, and more. The following gure depicts what is

included in the Java 2 SDK.

How Will Java Technology Change My Life?

We cant promise you fame, fortune, or even a job if you learn the Java
programming language. Still, it is likely to make your programs better and requires
less effort than other languages. We believe that Java technology will help you do
the following:
Get started quickly: Although the Java programming
language is a powerful object-oriented language, its
easy to learn, especially for programmers already
familiar with C or C++.
Write less code: Comparisons of program metrics
(class counts, method counts, and so on) suggest that a
program written in the Java programming language can
be four times smaller than the same program in C++.
Write better code: The Java programming language
encourages good coding practices, and its garbage
collection helps you avoid memory leaks. Its object
orientation, its JavaBeans component architecture, and
its wide-ranging, easily extendible API let you reuse
other peoples tested code and introduce fewer bugs.
Develop programs more quickly: Your development
time may be as much as twice as fast versus writing
the same program in C++. Why? You write fewer lines
of code and it is a simpler programming language than
C++.

 Avoid platform dependencies with 100% Pure

Java: You can keep your program portable by avoiding
the use of libraries written in other languages. The
100% Pure JavaTM Product Certication Program has a
repository of historical process manuals, white papers,
brochures, and similar materials online.
Write once, run anywhere: Because 100% Pure Java
programs are compiled into machine-independent byte
codes, they run consistently on any Java platform.
Distribute software more easily: You can upgrade
applets easily from a central server. Applets take
advantage of the feature of allowing new classes to be
loaded on the fly, without recompiling the entire
program.
ODBC
Microsoft Open Database Connectivity (ODBC) is a standard programming
interface for application developers and database systems providers. Before ODBC
became a de facto standard for Windows programs to interface with database
systems, programmers had to use proprietary languages for each database they
wanted to connect to. Now, ODBC has made the choice of the database system
almost irrelevant from a coding perspective, which is as it should be. Application
developers have much more important things to worry about than the syntax that is
needed to port their program from one database to another when business needs
suddenly change.

Through the ODBC Administrator in Control Panel, you can specify the
particular database that is associated with a data source that an ODBC application
program is written to use. Think of an ODBC data source as a door with a name on
it. Each door will lead you to a particular database. For example, the data source
named Sales Figures might be a SQL Server database, whereas the Accounts
Payable data source could refer to an Access database. The physical database
referred to by a data source can reside anywhere on the LAN.
The ODBC system les are not installed on your system by
Windows 95. Rather, they are installed when you setup a separate
database application, such as SQL Server Client or Visual Basic
4.0. When the ODBC icon is installed in Control Panel, it uses a le
called ODBCINST.DLL. It is also possible to administer your ODBC
data

sources

through

stand-alone

program

called

ODBCADM.EXE. There is a 16-bit and a 32-bit version of this

program and each maintains a separate list of ODBC data
sources.

From a programming perspective, the beauty of ODBC is that the

application can be written to use the same set of function calls to interface with any
data source, regardless of the database vendor. The source code of the application
doesnt change whether it talks to Oracle or SQL Server. We only mention these
two as an example. There are ODBC drivers available for several dozen popular
database systems. Even Excel spreadsheets and plain text files can be turned into
data sources. The operating system uses the Registry information written by ODBC
Administrator to determine which low-level ODBC drivers are needed to talk to
the data source (such as the interface to Oracle or SQL Server). The loading of the

ODBC drivers is transparent to the ODBC application program. In a client/server

environment, the ODBC API even handles many of the network issues for the
application programmer.
The advantages of this scheme are so numerous that you are probably
thinking there must be some catch. The only disadvantage of ODBC is that it isnt
as efficient as talking directly to the native database interface. ODBC has had
many detractors make the charge that it is too slow. Microsoft has always claimed
that the critical factor in performance is the quality of the driver software that is
used. In our humble opinion, this is true. The availability of good ODBC drivers
has improved a great deal recently. And anyway, the criticism about performance is
somewhat analogous to those who said that compilers would never match the
speed of pure assembly language. Maybe not, but the compiler (or ODBC) gives
you the opportunity to write cleaner programs, which means you finish sooner.
Meanwhile, computers get faster every year.

JDBC
In an effort to set an independent database standard API for Java; Sun
Microsystems developed Java Database Connectivity, or JDBC. JDBC offers a
generic SQL database access mechanism that provides a consistent interface to a
variety of RDBMSs. This consistent interface is achieved through the use of plugin database connectivity modules, or drivers. If a database vendor wishes to have
JDBC support, he or she must provide the driver for each platform that the
database and Java run on.

To gain a wider acceptance of JDBC, Sun based JDBCs framework on

ODBC. As you discovered earlier in this chapter, ODBC has widespread support
on a variety of platforms. Basing JDBC on ODBC will allow vendors to bring
JDBC drivers to market much faster than developing a completely new
connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public
review that ended June 8, 1996. Because of user input, the final JDBC v1.0
specification was released soon after.
The remainder of this section will cover enough information about JDBC for you
to know what it is about and how to use it effectively. This is by no means a
complete overview of JDBC. That would fill an entire book.

JDBC Goals
Few software packages are designed without goals in mind. JDBC is one
that, because of its many goals, drove the development of the API. These goals, in
conjunction with early reviewer feedback, have finalized the JDBC class library
into a solid framework for building database applications in Java.
The goals that were set for JDBC are important. They will give you some
insight as to why certain classes and functionalities behave the way they do. The
eight design goals for JDBC are as follows:

1. SQL Level API

The designers felt that their main goal was to dene a SQL
interface for Java. Although not the lowest database interface
level possible, it is at a low enough level for higher-level tools
and APIs to be created. Conversely, it is at a high enough level
for application programmers to use it condently. Attaining this
goal allows for future tool vendors to generate JDBC code and
to hide many of JDBCs complexities from the end user.
2. SQL Conformance
SQL syntax varies as you move from database vendor to
database vendor. In an effort to support a wide variety of
vendors, JDBC will allow any query statement to be passed
through it to the underlying database driver. This allows the
connectivity module to handle non-standard functionality in a
manner that is suitable for its users.
3. JDBC

must

be

implemental

on

database

top

of

common
interfaces

The JDBC SQL API must sit on top of other common SQL
level APIs. This goal allows JDBC to use existing ODBC level
drivers by the use of a software interface. This interface
would translate JDBC calls to ODBC and vice versa.
4. Provide a Java interface that is consistent with the
rest of the Java system
Because of Javas acceptance in the user community thus
far, the designers feel that they should not stray from the
current design of the core Java system.

5. Keep it simple
This goal probably appears in all software design goal
listings. JDBC is no exception. Sun felt that the design of JDBC
should be very simple, allowing for only one method of
completing

task

per

mechanism.

Allowing

duplicate

functionality only serves to confuse the users of the API.

6. Use strong, static typing wherever possible
Strong typing allows for more error checking to be done at
compile time; also, less error appear at runtime.
7. Keep the common cases simple
Because more often than not, the usual SQL calls used by the
programmer are simple SELECTs, INSERTs, DELETEs and
UPDATEs, these queries should be simple to perform with JDBC.
However, more complex SQL statements should also be
possible.

Finally we decided to proceed the implementation using Java Networking.

And for dynamically updating the cache table we go for MS Access
database.
Java ha two things: a programming language and a platform.
Java is a high-level programming language that is all of the
following

Simple

Architecture-neutral

Object-oriented

Portable

Distributed

High-performance

Interpreted

multithreaded

Robust

Dynamic

Secure
Java is also unusual in that each Java program is both compiled and
interpreted. With a compile you translate a Java program into an
intermediate language called Java byte codes the platform-independent
code instruction is passed and run on the computer.

Compilation happens just once; interpretation occurs each time the

program is executed. The figure illustrates how this works.

JavaProgram

Compilers

Interpreter

My Program

You can think of Java byte codes as the machine code instructions for
the Java Virtual Machine (Java VM). Every Java interpreter, whether its a
Java development tool or a Web browser that can run Java applets, is an
implementation of the Java VM. The Java VM can also be implemented in
hardware.

Java byte codes help make write once, run anywhere possible. You
can compile your Java program into byte codes on my platform that has a
Java compiler. The byte codes can then be run any implementation of the
Java VM. For example, the same Java program can run Windows NT,
Solaris, and Macintosh.

Networking
TCP/IP stack
The TCP/IP stack is shorter than the OSI one:

TCP is a connection-oriented protocol; UDP (User Datagram

Protocol) is a connectionless protocol.

IP datagrams
The IP layer provides a connectionless and unreliable delivery system.
It considers each datagram independently of the others. Any association
between datagram must be supplied by the higher layers. The IP layer
supplies a checksum that includes its own header. The header includes the
source and destination addresses. The IP layer handles routing through an
Internet. It is also responsible for breaking up large datagram into smaller
ones for transmission and reassembling them at the other end.

UDP
UDP is also connectionless and unreliable. What it adds to IP is a
checksum for the contents of the datagram and port numbers. These are
used to give a client/server model - see later.

TCP
TCP supplies logic to give a reliable connection-oriented protocol
above IP. It provides a virtual circuit that two processes can use to
communicate.

Internet addresses
In order to use a service, you must be able to find it. The Internet uses
an address scheme for machines so that they can be located. The address is
a 32 bit integer which gives the IP address. This encodes a network ID and
more addressing. The network ID falls into various classes according to the
size of the network address.

Network address
Class A uses 8 bits for the network address with 24 bits left over for
other addressing. Class B uses 16 bit network addressing. Class C uses 24
bit network addressing and class D uses all 32.

Subnet address
Internally, the UNIX network is divided into sub networks. Building 11
is currently on one sub network and uses 10-bit addressing, allowing 1024
different hosts.

Host address
8 bits are finally used for host addresses within our subnet.
This places a limit of 256 machines that can be on the subnet.

Total address

The 32 bit address is usually written as 4 integers separated by dots.

Port addresses
A service exists on a host, and is identified by its port. This is a 16 bit
number. To send a message to a server, you send it to the port for that
service of the host that it is running on. This is not location transparency!
Certain of these ports are "well known".

Sockets
A socket is a data structure maintained by the system to handle network
connections. A socket is created using the call socket. It returns an
integer that is like a file descriptor. In fact, under Windows, this handle can
be used with Read File and Write File functions.

#include <sys/types.h>
#include <sys/socket.h>
int socket(int family, int type, int protocol);
Here "family" will be AF_INET for IP communications, protocol
will be zero, and type will depend on whether TCP or UDP is used. Two
processes wishing to communicate over a network create a socket each.
These are similar to two ends of a pipe - but the actual pipe does not yet
exist.

SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process

of trying to discover every conceivable fault or weakness in a
work product. It provides a way to check the functionality of
components, sub assemblies, assemblies and/or a nished
product It is the process of exercising software with the intent of
ensuring that the
Software system meets its requirements and user expectations
and does not fail in an unacceptable manner. There are various
types of test. Each test type addresses a specic testing
requirement.

TYPES OF TESTS

Unit testing

Unit testing involves the design of test cases that validate

that the internal program logic is functioning properly, and that
program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of
individual software units of the application .it is done after the
completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and
is invasive. Unit tests perform basic tests at component level and
test a specic business process, application, and/or system
conguration. Unit tests ensure that each unique path of a
business

process

performs

accurately

to

the

documented

specications and contains clearly dened inputs and expected

results.

Integration testing

Integration tests are designed to test integrated software

components to determine if they actually run as one program.
Testing is event driven and is more concerned with the basic
outcome of screens or elds. Integration tests demonstrate that
although the components were individually satisfaction, as shown
by successfully unit testing, the combination of components is
correct and consistent. Integration testing is specically aimed at
exposing the problems that arise from the combination of
components.

Functional test
Functional tests provide systematic demonstrations that functions
tested are available as specied by the business and technical
requirements, system documentation, and user manuals.
Functional testing is centered on the following items:
Valid Input

: identied classes of valid input must be

accepted.
Invalid Input

: identied classes of invalid input must be

rejected.
Functions
Output
be exercised.

: identied functions must be exercised.

: identied classes of application outputs must

Systems/Procedures: interfacing systems or procedures must be

invoked.

Organization and preparation of functional tests is focused on

requirements, key functions, or special test cases. In addition,
systematic coverage pertaining to identifyBusiness process flows;
data elds, predened processes, and successive processes must
be considered for testing. Before functional testing is complete,
additional tests are identied and the effective value of current
tests is determined.

System Test
System testing ensures that the entire integrated software system
meets requirements. It tests a conguration to ensure known and
predictable results.

An

example of system testing is the

conguration oriented system integration test. System testing is

based on process descriptions and flows, emphasizing pre-driven
process links and integration points.

White Box Testing

White Box Testing is a testing in which in which the software
tester has knowledge of the inner workings, structure and
language of the software, or at least its purpose. It is purpose. It is
used to test areas that cannot be reached from a black box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge
of the inner workings, structure or language of the module being
tested. Black box tests, as most other kinds of tests, must be
written from a denitive source document, such as specication
or requirements document, such as specication or requirements
document. It is a testing in which the software under test is
treated, as a black box .you cannot see into it. The test provides
inputs and responds to outputs without considering how the
software works.

6.1 Unit Testing:

Unit testing is usually conducted as part of a combined code

and unit test phase of the software lifecycle, although it is not
uncommon for coding and unit testing to be conducted as two
distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written
in detail.
Test objectives
All field entries must work properly.
Pages must be activated from the identified link.
The entry screen, messages and responses must not be delayed.
Features to be tested
Verify that the entries are of the correct format
No duplicate entries should be allowed
All links should take the user to the correct page.

Integration Testing
Software integration testing is the incremental integration
testing of two or more integrated software components on a
single platform to produce failures caused by interface defects.
The task of the integration test is to check that components
or software applications, e.g. components in a software system or
one step up software applications at the company level
interact without error.

Test Results: All the test cases mentioned above passed

successfully. No defects encountered.

6.3 Acceptance Testing

User Acceptance Testing is a critical phase of any project and
requires signicant participation by the end user. It also ensures
that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed

successfully. No defects encountered.

System Configuration:H/W System Configuration:Processor

Pentium IV

Speed
RAM

2.1 Ghz
1GB(min)

Hard Disk

80 GB

S/W System Configuration: Operating System

:Windows XP/ 7/ 8

Front End

: java, jdk1.7

Database

: Mysql

Database Connectivity

: JDBC.

Eclipse
Android SDK
Tomcat Server
Client Side
Client side has a database for holding the local copy of the chart on the server. The function
of the software part of the client side is to update the database based on the actions
performed there and according to the data received from the server. Figure 4 shows a
simplied block diagram of the client side. The database stores the passenger information as
tables and the les stores the offline actions. The database on the client side is the offline
replica of the database kept at the server. The communication control block does the job of
synchronising the server and client databases.
Server Side
The server side has a database managed by scripts. The server stores the reservation
charts, user data and login details as tables in the database. As shown in Figure 5 the server
also holds the scripts and webpages. The client update the database at server by calling and
executing the scripts. On the other side, the web browsers can access the server database
through the web pages and scripts stored in the server.

As explained above, the operations done at the client side are stored in a local database.
These logged operations are communicated to the server on establishing the client-server
connection. The same operations reported by the client are done at the server after handling
conflicting operations. When a passenger cancels a ticket, positions of all the passengers in
the list after this cancelled passenger are upgraded automatically. During this operation,
passengers may move from waiting list to RAC or from RAC to conrmation according to
their position. The cancelled passenger as well as the upgraded passenger, whose category
has changed due to this up-gradation will be informed by sending a SMS if the passenger.
CONCLUSION

A demo version of the proposed system which includesa single client and one server
is implemented and tested.This is done based on lot of assumptions taken based
onour experiences as common people travelling in train andsome informal
discussions with very few railway officials. Butthrough this work, it could be proven
that such a system can beimplemented in Indian Railways. The actual system
should bedesigned with more thorough study about the real procedures,rules etc.
existing in Indian Railways regarding the reservation,chart preparation, attendance
marking, cancellation etc. Thereal scenarios like the number of devices required,
complexityof the network, security aspects etc. also need to be analysedthoroughly.
Improvements like attaching a printer which canbe used for ne collection, extra
charge collection etc. can alsobe thought about.Implementation of such a system
will reduce the manualintervention at many places of chart management tasks
whichwill make the process more efficient and effective. This systemcan replace the
existing paper chart in IR with a handheldelectronic device which drastically reduces
the use of paper.It is sure that such a system would be benecial to
railways,common man, nature and the country as a whole.