RAILWAY RESERVATION

PROJECT REPORT
Submitted by
Arihant Saxena (18BIT0133)
Aman Kumar Das (18BIT0482)
Prepared For
DATABASE MANAGEMENT SYSTEMS (ITE1003) – PROJECT COMPONENT

Submitted To
Dr. Bimal Kumar Ray
School of Information Technology and Engineering
 Introduction
In this rising world of computers, nearly all-manual system has switched to machine-
controlled and computerized system. Therefore, we are developing the software
system for “Railway Reservation System” to model the current system and to get rid
of the drawbacks of the current system. This project explore show technology can
be used to solve the matter of user. This being an enormous step in terms of
improvement within the railway it's widely accepted across the country. instead
of planning manually, we've got created use of computer.
Use of computer has resolved several issues, which are faced throughout manual
calculation. Once information are fed, it will perform correct functions. Therefore, to cut
back the complexness and potency a flexible and an out sourcing railway reservation
system has been developed. This project introduces railway reservation system. It
explains how reservation is being done in Indian Railways. The systematic procedure is
explained. we will build an application for this reservation system.
Currently in our application we've some further options like providing the SPECIAL
OFFERS to the users booking their tickets. The users can apply for ola cab services as
well. We gave our main focus on the back end portion and tried to
make the information as user friendly as possible. but in our project initially we are
going to solely cover the trains from Katpadi to Chennai, Bengaluru, Madurai,
Bhubaneshwar, Trichy, Hyderabad, Kodaikanal.
 Implementation

•All the manual work would be converted into computerized system and the
work of the employees should decrease a lot.
•The records should be stored in databases in place of files which will reduce
the inconsistency and redundancy of data.
•We also have included an option for special offers which the passengers can
apply for booking the tickets. It will automatically provide special discounts
and offers to the registered customers based on our sponsors.
•Users will be able to see the timings and available seats of all the trains for
their respective destinations
•Passengers can reserve and cancel the tickets any time as they want. The
available seats will be updated with appropriate queries.
•The main objective of the project is to make the application of train
reservation as much user friendly as possible and any type of suggestions to
improve the application from the users or other people is always welcome.
 Data Requirements
The complete details of the trains running on a particular route.
 Availability of seats on all the trains and their running schedule.
The number of food caterers delivering food near the station on which train stops.
Fare format of different coaches in trains.
Format of the ticket.
The whole route of all the trains running on a particular route.
Number of users regularly active on a reservation system.
Functional requirements includes a set of use cases that describes all the interactions
the users will have with the software. In addition to use cases, the Software
Requirements Specification (SRS) also contains non functional (or supplementary)
requirements. Non Functional Requirements are requirements which impose constraints
on the design or implementation (such as performance engineering requirements,
quality standards or design constraints).
 Functional Requirements
 User Satisfaction :- The system is such that it stands up to the user expectations.

 Response Time :- The response of all the operation is good. This has been made possible
by careful programming.

 Error Handling :- Response to user errors and undesired situations has been taken
care of to ensure that the system operates without halting.

 Safety and Robustness :- The system is able to avoid or tackle disastrous action. In
other words, it should be foul proof. The system safeguards against undesired events,
without human intervention.

 Portable :- The software should not be architecture specific. It should be easily

transferable to other platforms if needed.

 User Friendliness :- The system is easy to learn and understand. A native user can also
use the system effectively, without any difficulties.
 Design Constraint

 Standard Compliance :- This specifies the requirements for the standard the system
must follow. The standards may include the report format and accounting properties.

 Hardware Limitation :- The software may have to operate on some existing or

predetermined hardware, this imposing restrictions on the design. Hardware limitation
can include the types of machines to be used, operating system available on the system,
languages supported and limits on primary and secondary storage.

 Reliability and Fault Tolerance :- Fault tolerance requirements can place a major
constraints on how the system is to be designed. Fault tolerance requirements often
make the system more complex and expensive. Requirements about system behavior in
the face of certain kinds of faults are specified.
 Recovery requirements are often an integral part here, detailing what the system should
do I some failure occurs to ensure certain properties. Reliability requirements are very
important and critical applications.

 Security :- Security requirements are particularly significant in defence systems and

database systems. They place restrictions on the use of certain commands, control access
to data, provide different kinds of access requirements for different people, require the
use of passwords and cryptography techniques and maintain a log of activities in the
system.
Security
The system use SSL in all transactions that include any confidential customer information. The system must automatically
log out all customers after a period of inactivity. The system should not leave any cookies on the customer’s computer
containing the user’s password/ The system back end servers shall only be accessible to authenticated management.

Reliability
The reliability of the overall project depends on the reliability of the separate components. The main pillar of reliability of
the system is the backup of the database which is continuously maintained and updated to reflect the most recent changes.
Also the system will be functioning inside a container. Thus the overall stability of the system depends on the stability of
container and its underlying operating system.

Availability

The system should be available at all times, meaning the user can access it using a sweb browser, only restricted by the
down time of the server on which the system runs. A customer friendly system which is in access of people around the world
should work 24 hours. In case of a hardware failure or database corruption, a replacement page will be shown. Also in case
of a hardware failure or database corruption, backups of the database should be retrieved from the server and saved the
organizers. Then the service will be restarted. It means 24X7 availability.
Maintainability
A commercial database is used for maintaining the database and the application server takes care of the site. In case of a
failure, a re-initialization of the project will be done. Also the software design is being done with modularity in mind so that
maintainability can be done efficiently.

Supportability

The code and supporting modules of the system will be well documented and easy to understand. Online User
Documentation and Help System Requirements.
ER DIAGRAM
Thank You