You are on page 1of 20

Online Railway Reservation System

Presented ByAkshat Kale Anubhav Bhargava Aman Arora

Contents

Conventional & online railway reservation system. How does the system work? Basic technology Development Methodology: Suitable software process model Conclusion

Conventional Reservation System

Customer has to go to the ticket window to book a ticket. Time taken to book a ticket is too much. Customer has to wait in queue for his/her turn. Absence of ticketing windows in small stations

Online Railway Reservation

More convenient than the conventional system. Easy access from anywhere on the internet. No waiting time. Less chances of human error. Easy enquiry and cancellation. Complete information of the railway network.

How does it work ?

The user logins into the site and is then authenticated by the server. User is given a choice to either book, cancel or make an enquiry. The user is then logged out of the system.

Working Contd.

Book a Ticket
User can plan his travel by providing travel dates , source and destination of his journey. The list of trains is displayed according to the details filled by the user. The user selects the preferred train and then enters the details of the passengers travelling. User is directed to the payment gateway and on a successful transaction the ticket is booked and can be printed at any time.

Working Contd.

Enquiry
The user can make three types of enquiries. 1. Train Enquiry User enters the train no. or name and the server gives the estimated time of the arrival and departure of train. 2. PNR Enquiry User gives the PNR no. of the ticket and the current status is displayed. 3. Seat Enquiry User gives the train no. or name and the seat availability of each class is displayed.

Working Contd.

Cancellation User enters the PNR no. of the ticket to be cancelled. After a confirmation message the ticket is cancelled. The payment is returned after the processing is done. The no. of seats in the database is updated.

Development Methodology

This project is carried out using SPIRAL DEVELOPMENT MODEL. The spiral model is a software development process combining elements of both design and prototyping-in-stages This model of development combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive and complicated projects.

Spiral Model

Spiral Model :

A spiral model is divided into a number of framework activities Typically, there are six task regions as shown in figure. Customer communicationtasks required to establish effective communication between developer and customer. Planningtasks required to define resources, timelines, and other project related information.

Spiral Model :

Risk analysistasks required to assess both technical and

management risks. Engineeringtasks required to build one or more representations of the application. Construction and releasetasks required to construct, test, install, and provide user support (e.g., documentation and training). Customer evaluationtasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation stage

Spiral Model:

The decision to use the spiral model methodology is due to the following characteristics of the project: Early iterations of the project are the cheapest, enabling the highest risks to be addressed at the lowest total cost. This ensures that as costs increase, risks decrease. Each iteration of the spiral can be tailored to suit the needs of the project.

Other details

The other details about the project is given in the following document : Software Project Management Plan (SPMP) Software Requirements Specifications (SRS)

Snapshots

Registration Page

Login Page

You might also like