MOBILE BASED FEEDBACK SYSTEM

FOR RAILWAY

CERTIFICATE OF

APPROVAL

This is to certify that project synopsis entitled asMOBILE BASED FEEDBACK

SYSTEM FOR RAILWAY, submitted in partial fulfillment for the degree of Bachelor
of Engineering in Computer Science of Rajiv Gandhi Proudyogiki Vishwavidyalaya,
Bhopal for academic year 2013 of TIETECH, Jabalpur has been duly completed as
record of genuine work in TIETECH, Jabalpur.

EXTERNAL EXAMINER
Date:

INTERNAL EXAMINER

Date:

DECLARATION

Ihereby declare that the work presented in this project entitledMOBILE BASED
FEEDBACK SYSTEM FOR RAILWAY,is the outcome of my own work and correct
to the best of my knowledge. This work has been carried out taking care of engineering
2

ethics. The work presented does not infringe upon any patented work and has not been
submitted to any other University or anywhere else for award of any degree or any
professional diploma.

Date:

/ 2014PratikshaPachori

- 0207CS111047
SayadaBano - 0207CS111067
SilisapnaMohanty- 0207CS111077

Meenakshi Mishra 0207cs111036

ACKNOWLEDGEMENT

The project defines and signifies the shear mannerism in which numerous interacted
tasks are performed by a team composed of committed members.Each member
bearing their own importance and providing contribution, which is nothing short of being
invaluable.
The day which marked the beginning of our project bears a special status to all of us,
we begin with the proceeding and blessing if our parents and good wishes of our
friends of our friends if our friends on the project work entitled MOBILE BASED
FEEDBACK SYSTEM FOR RAILWAY We are thankful to Prof. JAVED AKTAR
KHAN (DEPARTMENTAL CO-ORDINATOR) Under whose support we have been able
to make this project a great success. We also give thanks to all of our teachers of
Computer Science and Engineering Department for their valuable support in the
operation of this project.Last but not the least, we wish to remember with the deep
sense of gratitude the encouragement provided to us by our friends and batch mates.

PratikshaPachori
SilisapnaMohanty
SayadaBano
Meenakshi Mishra

INDEX
Content

Page No.
4

1. Abstract

2. Introduction

3. System Requirements

10

Software Requirement

10

Hardware Requirement

10

4. Analysis

11

Feasibility Study

11

Technical Feasibility

11

BehavioralFeasibility

12

Schedule Feasibility

12

Operational Feasibility

12

System Design

13

Model Used

14

5. Overall Description

17

System analysis

17

Problem statement

18

Problem in existing system

18

Proposed solution

18

6. Data Flow Diagram

19

7. E-RDiagram20

8. Use Case Diagram& tables

21

9. About Android25
9.1. Introduction
9.1.1The birth of android
Google Acquires Android Inc.

Open Handset AllianceFounded

Hardware
9.1.2. features

25
25

25
25
26

Application Framework

26

Dalvik Virtual Machine

27

Integrated Browser

Optimized Graphics

SQLite

27

Handset Layouts

27

Data Storage

28

Connectivity
Messaging
Web browser
Java virtual machine
Media support
Additional hardware support
Development environment

27

28
28
28
28
28
29

9.2 DETAILED DESCRIPTION OF THE TOPIC

9.2.1
OPERATION

29

Android runtime
Linux kernel

10.Testing

32

11.Snapshots

34

12.Future Scope

37
6

13.Conclusion

38

14.Bibliography

1.ABSTRACT
The Mobile Based feedback System for Railway is aimed at creating efficient software for
addressing the problems of the passenger for various purposes like-bedrolls complain, catering
and vending services, electricity issues, and other related problems etc.
Mobile Based Feedback System This system is generally used by two kinds of users:

Passenger
Admin

We have developed Mobile Based Feedback System to provide feedback in an easy and
quickMannerto therailway department and railway employee. So

we call it

as Mobile

BasedFeedback System which delivers via the passenger interface as Mobile Based system
which Acting as a Service Provider. The passengers can first make a register a feedback related
to a particular complaint by entering its PNR NO. anduid. The system provides the passenger
with a complain number which gives him access to check the status of its complain and
passenger can check the status of the complain by entering PNR NO also.
This system acts as an interface between the customers and railway department thereby enabling
them to forward their complaints to the appropriate railway department. Hence, making the work
easy for both the complaint raiser and the person who resolves the complaint. Here, in complaint
tracking, it fulfills different requirements of administrator and customer more efficiently.

2. INTRODUCTION
The objective of the project is to develop an application in which any passenger can feed their
complaint report. If anybody wants to complaint about the railway facilities which were given in
the train fill the Mobile Based feedback . The Mobile Based Feedback System make easier for
the passenger to complaint and also for the railway department to know about the passengers
complaint. This project will be useful for the railway passenger. Only the Administrator will be
able to access and change status of the complaint.
The complaints can be assigned to different persons and will get tracked to closure. The person
handling the complaint will have the facility to communicate with the customer via emails
through the system.
In the administration module each of the administrator must enter ID and PASSWORD in
administrator login page.In the passenger module each passenger must enter the PNR NO, uid,
phone no, e-mail, name, date of complaint, complaint detail.

3. SYSTEM REQURIMENT
Operating Environment Hardware and Software

Software Requirements:
Operating System

Any

Windows

Browser

Internet Explorer.

Web Server

A p a c h e Tom c a t 7 . 0 . 3 4 . 0

IDE

NetBeans

Language

JAVA (JSP )& HTML,CSS.

Back End

Processor

I n t e l

Ram

Communication Channel

Hard Disk

OS.

IDE

7..3

Hardware Requirements:

5
n

6
t

c o r e
M

n
G

B
e

t
B

4. ANALYSIS
4.1 FEASIBILITY STUDY
A feasibility study is a test of system proposal according to its workability, impact on the
organization, ability to meet user needs and effective use of resources.
The objective of feasibility study is not to solve the problem, but to acquire a sense of its scope.
During the study, the problem definition is crystallized and aspects of the problem to be included
in the system are determined, consequently costs and benefits are estimated with greater detail at
this stage. The result of the feasibility study is a system formal proposal. This is simply a form of
documenting or detailing the nature and scope of proposed solutions. The proposal summarizes
what is known and what is going to be done. Three key considerations involved in the feasibility
analysis:

Technical feasibility
Behavioral feasibility
Schedule feasibility
Operational feasibility

TECHNICAL FEASIBILITY:
The feasibility center on the existing computer system (software, hardware) and to what extend it
can support the proposed addition. In the proposed system, data can be easily stored and
managed in database management system software.
10

The results for various queries can be generated easily. Therefore, the system is technically
feasible.

BEHAVIORAL FEASIBILITY:

People are inherently resistant to change and computer has known to facilitate change. An
estimate should be made of how strong a reaction the user staff is likely to have towards the
developments of computerized system.
In the existing system more manpower is required and time factor is more but in theproposed
system, manpower and time factors are reduced .So, the remaining numbers are engaged with
some other important works.

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 the
system.

OPERATIONAL FEASIBILITY

It is mainly related to human organizations and political aspects. The points to be

considered are:
What changes will be brought with the system?
What organization structures are disturbed?
What new skills will be required? Do the existing staff members have theseskills?
If not, can they be trained in due course of time?
11

The system is operationally feasible as it very easy for the End users to operate it.

4.2 SYSTEM DESIGN

SOFTWARE DEVELOPMENT LIFE CYCLE

The system development life cycle (SDLC) follows a project through from the
initial idea to the point where it is a functional system. It is a core part of the
methodology that is used when defining a project.

Life cycles fall into a number of different categories, iterative being the most
common but they also include waterfall, spiral and chaos models. Common

12

methodologies include Structured Systems Analysis and Design Method

(SSADM) and Microsoft Solutions Framework (MSF).
The aim of SSADM is to provide logical data modeling to identify, model and
document the data requirements of the system being designed. The data is split
into entities and relationships. Data flow modeling documents how data moves
through a system and examines processes, entities, data flow and data stores.

4.3 MODEL
In our project we are using WATER FALL MODEL.

Waterfall Strengths

Easy to understand, easy to use

Provides structure to inexperienced staff
Sets requirements stability
Good for management control (plan, staff, track)
Works well when quality is more important than cost or schedule

When to use the Waterfall Model

Requirements are very well known

Product definition is stable
Technology is understood
New version of an existing product
Porting an existing product to a new platform.

13

Stages in WATER FALL MODEL:

Requirement Gathering
Analysis
Designing
Coding
Testing
Maintenance

Requirements Gathering stage:

The requirements gathering process takes as its input the goals identified in the highlevel
requirements section of the project plan. Each goal will be refined into a set of one or more
requirements. These requirements define the major functions of intended application define
operational data areas and reference data areas, and define the initial data entities.
Major functions include critical processes to be managed, as well as mission critical inputs,
outputs and reports. A user class hierarchy is developed and associated with thesemajor
functions, data areas, and data entities. Each of these definitions is termed a Requirement.

Analysis Stage:
14

The planning stage establishes a bird's eye view of the intended software product,and uses this to
establish the basic project structure, evaluate feasibility and risksassociated with the project, and
describe appropriate management and technicalapproaches .The most critical section of the
project plan is a listing of high-level product requirements, also referred to as goals. The
minimum information for each goal consists of a title and textual description, although additional
information and references to external documents may be included.

Designing Stage:
The design stage takes as its initial input the requirements identified in the approvedrequirements
document. For each requirement, a set of one or more design elements will be produced as a
result of interviews, workshops, and/or prototype efforts. Design elements describe the desired
software features in detail, and generally include functional hierarchy diagrams, screen layout
diagrams, tables of business rules, business process diagrams, pseudo code, and a complete
entity-relationship diagram with a full data dictionary. These design elements are intended to
describe the software in sufficient detail that skilled programmers may develop the software with
minimal additional input.

Development (Coding) Stage:

The development stage takes as its primary input the design elements described in theapproved
design document. For each design element, a set of one or more softwareartifacts will be
produced. Software artifacts include but are not limited to menus,dialogs, data management
forms, data reporting formats, and specialized procedures and functions. Appropriate test cases
will be developed for each set of functionally related software artifacts, and a Mobile Based help
system will be developed to guide users in their interactions with the software.

Integration & Test Stage:

15

During the integration and test stage, the software artifacts, Mobile Based help and test dataare
migrate from the development environment to a separate test environment. At this point, all test
cases are ,run to verify the correctness and completeness of the software. Successful execution of
the test ,suite confirms a robust and complete migration capability. During this stage, reference,
data is ,finalized for production use and production users are identified and linked to their
appropriate roles.

Maintenance:
Outer rectangle represents maintenance of project .Maintenance team start withrequirement
study, understanding of documentation later employees will be assignedwork and they will
undergo training on that particular assigned category.

5.OVERALL DESCRIPTION

SYSTEM ANALYSIS
System analysis is an important phase of any system development process. The system is studied
to the minute details and analyzed. The system analyst plays the role of an interrogator and
dwells deep in to the working of the present system. In analysis, a detailed study of these
operations performed by a system and their relationships within and outside the system is done.
A key question considered here is, what must be done to solve the problem? The system is
viewed as a whole and the inputs to the system are identified. Once analysis is completed the
analyst has a firm understanding of what is to be done.
The project mainly aims to develop an application for the Railway Department to handle their
complaint process in an easy way.

16

PROBLEM STATEMENT
In the current scenario there is very less system operating for the registration of complaints.
Presently complaint register process is done through telephone where a complaint is raised by
calling the administration. This can lead to confusions for the passengers. The existing system is
carries more time to do a piece of work.
For this reason the Mobile Based system feedback is implemented. This is the major advantage
of the existing system for giving feedback about the railway services. To make train travel
hassle-free, the Railways have decided to accept complaints registered electronically.
The Railways are developing software that would enable passengers to post their grievances by
email or SMS. The Railways will monitor Mobile Based the complaint, forwarding it internally
and responding to it forthwith. The agency at fault will be hauled up.

PROBLEM IN EXISTING SYSTEM

As we know telephonic system are quite tedious, time consuming and less efficient and accurate
in comparison to the computerized system.
So following are some disadvantages of the old system:
1. Time consuming.
2. Less accurate.
3. Less efficient.
4. Slow data processing.
5. Not user friendly environment.
6. Difficult to keep old records.

17

PROPOSED SOLUTION
The idea is to automate the entire complaint process from telephonic medium to electronic
medium in order to increase efficiency and reduce the response time.
There would be basically 3-4 main categories for the selection of complaint type.

Validation is done for unique user id and pnr no.

A unique complaint number would be generated for a particular complaint. User would
be able to check the status of his/her complaint.

Basically this would be a one stop solution for passengers to make authority aware of
existing issue at a particular time.

The specific purpose of the system is to gather and resolve complaints that arise in
different passenger handled by the railway department.

6. DATA FLOW DIAGRAMS

A data flow diagram (DFD) is a graphical representation of the "flow" of datathrough

information system. A data flow diagram can also be used for thevisualization of data processing
(structured design).

18

FIG 1

FIG 2

7.E-R DIAGRAM
The ER diagram is drawn to have a better understanding of the whole scenario, itwas used to
conceptualize the phenomena, actions and interactions between various entities and to arrive at
the specific requirements in a comprehensive manner. The ER diagram is attached with this SRS.
19

username

FIG 3:E-R DIAGRAM OF MFSR

8.USECASE DIAGRAM AND TABLES:PASSENGERS TABLE

F i e l d
I
d
P n r
n o
U
i
d
N a m e
Contact no
E m a i l

Data Typ e
i n t e g e r
Var c h a r ( 2 0 )
Var c h a r ( 3 0 )
Var c h a r ( 3 0 )
Var c h a r ( 1 5 )
Var c h a r ( 3 0 )

K
e
y
P r i m a r y k e y Auto increment

20

c D

a
t
e
TABLE NO 1

ADMIN TABLE
F

d D a t a

U s e r n a m e

T y p e

v a r c h a r ( 3 0 ) ,

P a s s w o r d v a r c h a r ( 3 0 ) ,
TABLE NO 2

COMPLAINT TABLE
F
i
e
l
d
C o m p l a i n t n o
Complaint detail
Detailed response

D a t a
T y p e
V a r c h a r ( 3 0 )
V a r c h a r ( 2 5 5 )
v a r c h a r ( 2 5 5 )

TABLE NO 3

UML Diagram

21

K
e
y
P r i m a r y
k e y

FIG 4

FIG 5

22

FIG 6

FIG 7
23

9.About Android
9.1INTRODUCTION
Android is a software stack for mobile devices that includes an operating system, middleware
and key applications.Android is a software platform and operating system for mobile devices
based on the Linux operating system and developed by Google and the Open Handset Alliance. It
allows developers to write managed code in a Java-like language that utilizes Google-developed
Java libraries, but does not support programs developed in native code.
The unveiling of the Android platform on 5 November 2007 was announced with the founding of
the Open Handset Alliance, a consortium of 34 hardware, software and telecom companies
devoted to advancing open standards for mobile devices. When released in 2008, most of the
Android platform will be made available under the Apache free-software and open-source
license.
9.1.1THE BIRTH OF ANDROID

Google Acquires Android Inc.

In July 2005, Google acquired Android Inc., a small startup company based in Palo Alto,
CA. Android's co-founders who went to work at Google included Andy Rubin (cofounder of Danger), Rich Miner (co-founder of Wildfire Communications, Inc), Nick
Sears (once VP at T-Mobile), and Chris White (one of the first engineers at WebTV). At
the time, little was known about the functions of Android Inc. other than they made
software for mobile phones.
At Google, the team, led by Rubin, developed a Linux-based mobile device OS which
they marketed to handset makers and carriers on the premise of providing a flexible,
upgradeable system. It was reported that Google had already lined up a series of
hardware component and software partners and signaled to carriers that it was open to
various degrees of cooperation on their part.

24

Open Handset AllianceFounded

On 5 November 2007, the Open Handset Alliance, a consortium of several companies

which include Google, HTC, Intel, Motorola, Qualcomm, T-Mobile, Sprint Nextel and
NVIDIA, was unveiled with the goal to develop open standards for mobile devices.
Along with the formation of the Open Handset Alliance, the OHA also unveiled their first
product, Android, an open source mobile device platform based on the Linux operating
system.

Hardware

Google has unveiled at least three prototypes for Android, at the Mobile World Congress
on February 12, 2008. One prototype at the ARM booth displayed several basic Google
applications. A 'd-pad' control zooming of items in the dock with a relatively quick
response.
A prototype at the Google IO conference on May 28, 2008 had a 528 MHz Qualcomm
processor and a Synaptics capacitive touch screen, and used the UMTS cellular standard.
It had 128 MB of RAM and 256 MB of flash, showing that Android's memory
requirements are reasonable. The demo was carried out using a 3.6 Mbit/s HSDPA
connection.
9.1.2FEATURES

Application Framework

It is used to write applications for Android. Unlike other embedded mobile

environments, Android applications are all equal, for instance, an applications
which come with the phone are no different than those that any developer
writes.The framework is supported by numerous open source libraries such as
openssl, SQLite and libc. It is also supported by the Android core libraries. From
the point of security, the framework is based on UNIX file system permissions that
assure applications have only those abilities that mobile phone owner gave them at install
time.
25

Dalvik Virtual Machine

It is extremely low-memory based virtual machine, which was designed especially for
Android to run on embedded systems and work well in low power situations. It is also
tuned to the CPU attributes. The Dalvik VM creates a special file format (.DEX)
that is created through build time post processing. Conversion between Java classes
and .DEX format is done by included dx tool.

Integrated Browser

Google made a right choice on choosing WebKit as open source web browser. They
added a two pass layout and frame flattening. Two pass layout loads a page without
waiting for blocking elements, such as external CSS or external JavaScript and after
a while renders again with all resources downloaded to the device. Frame flattening
converts founded frames into single one and loads into the browser. These features
increase speed and usability browsing the internet via mobile phone.

Optimized Graphics

As Android has 2D graphics library and 3D graphics based on OpenGL ES 1.0,

possibly we will see great applications like Google Earth and spectacular games
like Second Life, which come on Linux version. At this moment, the shooting legendary
3D game Doom was presented using Android on the mobile phone.

SQLite

Extremely small (~500kb) relational database management system, which is integrated in

Android. It is based on function calls and single file, where all definitions, tables and data
are stored. This simple design is more than suitable for a platform such as Android.

Handset Layouts

The platform is adaptable to both larger, VGA, 2D graphics library, 3D graphics library
based on OpenGL ES 1.0 specifications, traditional smart phone layouts. An underlying
26

2D graphics engine is also included. Surface Manager manages access to the display
subsystem and seamlessly composites 2D and 3D graphic layers from multiple
applications

Data Storage

SQLite is used for structured data storage .SQLite is a powerful and lightweight relational
database engine available to all applications.

Connectivity

Android supports a wide variety of connectivity technologies including GSM, CDMA,

Bluetooth, EDGE, EVDO, 3G and Wi-Fi.

Messaging

SMS, MMS, and XMPP are available forms of messaging including threaded text
messaging.

Web Browser

The web browser available in Android is based on the open-source WebKitapplication

framework. It includesLibWebCore which is a modern web browser engine which powers
both the Android browser and an embeddable web view.

Java Virtual Machine

Software written in Java can be compiled into Dalvikbytecodes and executed in the
Dalvik virtual machine, which is a specialized VM implementation designed for mobile
device use, although not technically a standard Java Virtual Machine.

Media Support

Android will support advanced audio/video/still media formats such as MPEG-4, H.264,
MP3, and AAC, AMR, JPEG, PNG, GIF.
27

Additional Hardware Support

Android is fully capable of utilizing video/still cameras, touchscreens, GPS, compasses,

accelerometers, and accelerated 3D graphics.

Development Environment

Includes a device emulator, tools for debugging, memory and performance profiling, a
plugin for the Eclipse IDE.There are a number of hardware dependent features, for
instance, a huge media and connections support, GPS, improved support for Camera
and simply GSM telephony. A great work was done for the developers to start work
with Android using device emulator, tools for debugging and plugin for Eclipse
IDE.

9.2DETAILED DESCRIPTION OF THE TOPIC

9.2.1 OPERATION

Android Runtime

Android includes a set of core libraries that provides most of the functionality available in
the core libraries of the Java programming language.Every Android application runs in its
own process, with its own instance of the Dalvik virtual machine. Dalvik has been written
so that a device can run multiple VMs efficiently.
The Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized
for minimal memory footprint. The VM is register-based, and runs classes compiled by a
Java language compiler that have been transformed into the .dex format by the included
"dx" tool.TheDalvik VM relies on the Linux kernel for underlying functionality such as
threading and low-level memory management.

Linux Kernel

Android relies on Linux version 2.6 for core system services such as security, memory
management, process management, network stack, and driver model. The kernel also acts
as an abstraction layer between the hardware and the rest of the software stack.
28

It helps to manage security, memory management, process management, network stack and
other important issues. Therefore, the user should bring Linux in his mobile device as the
main operating system and install all the drivers required in order to run it.
Developers have full access to the same framework APIs used by the core applications.

The application architecture is designed to simplify the reuse of components; any

application can publish its capabilities and any other application may then make use of
those capabilities (subject to security constraints enforced by the framework). This same
mechanism allows components to be replaced by the user.Underlying all applications is a
set of services and systems.
At the same level there is Android Runtime, where the main component Dalvik Virtual
Machine is located. It was designed specifically for Android running in limited
environment, where the limited battery, CPU, memory and data storage are the main
29

issues. Android gives an integrated tool dx, which converts generated byte code from
.jar to .dex file, after this byte code becomes much more efficient to run on the small
processors.

Figure 2.2 : Conversion from .java to .dex file

As the result, it is possible to have multiple instances of Dalvik virtual machine running
on the single device at the same time. The Core libraries are written in Java language and
contains of the collection classes, the utilities, IO and other tools.

How Android interacts with Web Server

30

10.TESTING

What is testing?
Testing is the process of evaluating a system or its component(s) with the intent to find that
whether it satisfies the specified requirements or not.
This activity results in the actual, expected and difference between their results. In simple words
testing is executing a system in order to identify any gaps, errors or missing requirements in
contrary to the actual desire or requirements.
It involves the identification of bug/error/defect in the software without correcting it. Normally
professionals with a Quality Assurance background are involved in the identification of bugs.

When to Start Testing

In Software Development Life Cycle (SDLC) testing can be started from the Requirements
Gathering phase and lasts till the deployment of the software.

When to Stop Testing

Testing is a never ending process and no one can say that any software is 100% tested. Following
are the aspects which should be considered to stop the testing:

Testing Deadlines.

Completion of test case execution.

Completion of Functional and code coverage to a certain point

.
Bug rate falls below a certain level and no high priority bugs are identified.

Management decision.

31

TYPES OF TESTING
I.

BLACK BOX TESTING

II.

WHITE BOX TESTING

III.

GREY BOX TESTING

In our project we are considering UNIT TESTING.

Unit Testing
This type of testing is performed by the developers before the setup is handed over to the testing
team to formally execute the test cases. Unit testing is performed by the respective developers on
the individual units of source code assigned areas. The developers use test data that is separate
from the test data of the quality assurance team.
The goal of unit testing is to isolate each part of the program and show that individual parts are
correct in terms of requirements and functionality.

32

11.SNAPSHOTS
HOME PAGE

PASSENGER S FEEDBACK

33

PASSENGER COMPLAINT STATUS

CHECK STATUS

34

ADMIN PAGE

35

11. FUTURE SCOPE

The following features may be added in future for the enrichment of this software.

We can also add some other complaints .

We can also generate a bar graph at the admin side.

However this is our one of the earliest effort in making such a software in such platform, we
hope for future betterment.This software can be easily implemented under various situations.

SOFTWARE SCOPE:
Extensibility: This software is extendable in ways that its originaldevelopers may not expect.
The following principles enhancesextensibility like hide data structure, avoid traversing multiple
links or methods, avoid case statements on object type anddistinguish public and private
operations.
Reusability: Reusability is possible as and when require in thisapplication. We can update it
next version. Reusable softwarereduces design, coding and testing cost by amortizing effort over
several designs. Reducing the amount of code alsosimplifies understanding, which increases the
likelihood thatthe code is correct.
Understandability: A method is understandable if someone otherthan the creator of the
method can understand the code (aswell as the creator after a time lapse). We use the
method,which small and coherent helps to accomplish this.
Cost-effectiveness: Its cost is under the budget and make withingiven time period. It is
desirable to aim for a system with aminimum cost subject to the condition that it must satisfy the
entire requirement.
36

Scope of this document is to put down the requirements, clearlyidentifying the information
needed by the user, the source of theinformation and outputs expected from the system.

12.CONCLUSION

From a proper analysis of positive points and constraints on the components, it can be concluded
that the product is highly efficient WEB GUI based software. This software is working properly
and meeting to all user requirements. The solution is suitable for all range of railway
organizations. This software is Effective, Efficient, Integrated and Comprehensive Management
Solution for any passenger.

37

11.BIBLIOGRAPHY
[1] Pressman, Roger S., Software Engineering, sixth edition, McGraw-Hill Higher Education,
2001.
[2] Elmasri | Navathe, Fundamentals of Database Systems, third edition, Addison-Wesley, 2000.
[3] www.irctc.com
[4] www.w3schools.com/html

38