Railway Reservation System: Background

RAILWAY RESERVATION SYSTEM
BACKGROUND:
The Indian Railways (IR) carries about 5.5 lakhs passengers in reserved accommodation
every day. The Computerised Passenger Reservation System (PRS) facilitates the booking and
cancellation of tickets from any of the 4000 terminals (i.e. PRS booking window all over the
countries). These tickets can be booked or cancelled for journeys commencing in any part of
India and ending in any other part, with travel time as long as 72hours and distance up to several
thousand kilometers.
The project of PRS was launched on 15 th November 1985, over Northern Railway with
the installation of Integrated Multiple Train Passenger Reservation System (IMPRESS), an
online transaction processing system developed by Indian Railways in association with
Computer Maintenance Corporation Ltd., at New Delhi. The objective was to provide reserved
accommodations on any train from any counter, preparation of train charts and accounting of the
money collected. The application was implemented in 1987 Mumbai, Chennai, Kolkata,
Secunderabad subsequently.
PROBLEM DEFINITION
• Railway passengers frequently need to know about their ticket reservation status, ticket
availability on a particular train or for a place, train arrival or departure details, special
trains etc.. Customer information centers at the railway stations are unable to serve such
queries at peak periods.
• The number of the reservation counters available to the passengers and customers are
very less.
• On most of the reservation systems there are long queues, so it takes a long time for any
individual to book the ticket.
• As now there are no call centers facilities available to solve the queries of the passengers.
High Level Design:

• ONLINE BOOKING: With the help of this people can book their tickets online through
internet, sitting in their home by a single click of mouse. Using their credit cards people
can easily get their tickets done within minutes. There are certain charges for online
booking as well.
• COUNTER BOOKING: This is the oldest method of booking the tickets. The reservation
counters are there at railway department from where people can get the tickets to their
respective destinations.
Detailed Design:
SPIRAL MODEL DIAGRAM
• The spiral model, originally proposed by Boehm [BOE88], is an evolutionary software

process model that couples the iterative nature of prototyping with the controlled and
systematic aspects of the linear sequential model.
• It provides the potential for rapid development of incremental versions of the

software. Using the spiral model, software is developed in a series of incremental
releases.
• During early iterations, the incremental release might be a paper model or

prototype. During later iterations, increasingly more complete versions of the engineered
system are produced.
• A spiral model is divided into a number of framework activities, also called task
regions. Typically, there are between three and six task regions.
Figure depicts a spiral model that contains six task regions:
Customer communication—tasks required to establish effective communication between

developer and customer.
Planning—tasks required to define resources, timelines, and other project related

information.
Risk analysis—tasks required to assess both technical and management
risks.
Engineering—tasks required to build one or more representations of the
Application.
Construction and release—tasks required to construct, test, install, and
Provide user support (e.g., documentation and training).
Customer evaluation—tasks required to obtain customer feedback based
On evaluation of the software representations created during the engineering
Stage and implemented during the installation stage.
CLASS DIAGRAM
class a
private:
int c, n, a, i, s;
char id[50];
char pasw[50];
char date[10];
char d1[15], d2[15];
public:
getLogin();
train();
USE CASE DIAGRAM
Enter user id and password
verify password and user id

system
Make a reservation
user
Verify payments
Update reservations
cancellation of reservation administrator
SEQUENCE DIAGRAM
:User :System :Administrator
Log in
{verify user}
Secure communication
Enter date {verify date}
Request confirmation
Enter desired destination
Choose desired express

Enter the no of tickets
Request confirmation {verify funds}
Confirm purchase
Place order
{execute
order}
STATE TRANSITION DIAGRAM
Online reservation system
Enter user id and password
invalid
Make reservation
Confirm reservation
For cancellation
Cancellation of reservation Make payments
exit
ACTIVITY DIAGRAM
Verify credit cards

detail
(invalid)
(success)
Debit
account Send
invalid
Send
notice
confirmation
Settle
transaction
Close
transaction
0 LEVEL DFD DIAGRAM:
Transaction
User website
Process
1 LEVEL DFD DIAGRAM
Enter userid and

password
verify userid and password

Enter date
Enter no of Online train

tickets
reservation
Check for the
Enter express name system availability of date
Make
purchases
TESTING:
• Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design, and code generation.
• The types of the testing are as follows:
1. Unit testing
2. System testing
3. Validation testing and etc etc.
But however due to the time constraint we could not perform various types of testing.
Hence we just applied alpha testing which is a part of validation test to our project.

Railway Reservation System: Background

Uploaded by

Copyright:

Available Formats

Railway Reservation System: Background

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Railway Reservation System: Background

Uploaded by

Copyright:

Available Formats

RAILWAY RESERVATION SYSTEM

High Level Design:

• The spiral model, originally proposed by Boehm [BOE88], is an evolutionary software

• It provides the potential for rapid development of incremental versions of the

• During early iterations, the incremental release might be a paper model or

Customer communication—tasks required to establish effective communication between

Planning—tasks required to define resources, timelines, and other project related

Risk analysis—tasks required to assess both technical and management

Engineering—tasks required to build one or more representations of the

Construction and release—tasks required to construct, test, install, and

Provide user support (e.g., documentation and training).

Customer evaluation—tasks required to obtain customer feedback based

On evaluation of the software representations created during the engineering

Stage and implemented during the installation stage.

Enter user id and password

verify password and user id

cancellation of reservation administrator

:User :System :Administrator

Choose desired express

Online reservation system

Enter user id and password

Verify credit cards

1 LEVEL DFD DIAGRAM

Enter userid and

verify userid and password

Enter no of Online train

• The types of the testing are as follows:

3. Validation testing and etc etc.

You might also like