Online Railway Reservation System

Submitted To: Sir Sagheer

Submitted By: Ali Rizwan (2113268) Rehan Shafiq (2113222) Salman Karim (2113023)

National College of Business Administration & Economics

School of Computer Science

Contents
Online Railway Reservation System............................................................................................................. 1 Railway Reservation System ........................................................................................................................ 3 Introduction ................................................................................................................................................... 3 Objective ....................................................................................................................................................... 3 Current System.............................................................................................................................................. 3 Limitations of Current System ...................................................................................................................... 3 Proposed System ........................................................................................................................................... 3 Phases............................................................................................................................................................ 4 Planning: ............................................................................................................................................... 4 Risk Analysis Phase: ............................................................................................................................. 4 Engineering Phase:................................................................................................................................ 5 Evaluation Phase: .................................................................................................................................. 5

Requirement Specification ............................................................................................................................ 5 Security Specifications.................................................................................................................................. 5 Data Flow Diagrams ..................................................................................................................................... 6 Level-0 DFD ............................................................................................................................................. 6 Why Spiral Model? ....................................................................................................................................... 7 Spiral Diagram .............................................................................................................................................. 7 Coding ........................................................................................................................................................... 8 Case Diagram ................................................................................................................................................ 9 Sequence Diagram ...................................................................................................................................... 10 Activity Diagram ........................................................................................................................................ 11

Railway Reservation System

Introduction
The Pakistan Railway carries about 1 lakh passengers in reserved accommodation every day. The Computerized Passenger Reservation System (PRS) facilitates the booking and cancellation of tickets from any of the 2000 terminals (i.e. PRS booking window all over the countries). These tickets can be booked or cancelled for journeys commencing in any part of Pakistan and ending in any other part, with travel time as long as 72hours and distance up to several thousand kilometers.

Objective
The objective of Computerized Passenger Railway System (PRS) was to provide reserved accommodations on any train from any counter, preparation of train charts and accounting of the money collected.

Current System
The existing system has many shortcomings associated with it. In the existing system railways used to set railway reservation levels higher than seating capacity to compensate for passenger cancellations. If the traveler had to make / cancel the reservation he had to visit the railway office thus wasting time and money. In the existing system due to non-availability of central server the airline and agents suffered from unwanted delays in booking and payments.

Limitations of Current System

With the current system the database is not centralized so information is not available from anywhere in the world. Inconvenience for ticket booking and payments. Integration of different railways on a single platforms was not met.

Proposed System
The main objective is to develop a user-friendly system which enables the customer to book & purchase online ticket conveniently. This system maintain the database centrally giving the clients the information required from anywhere in the world. Providing journey details. This system facilitates the railway booking for a particular destination, date & time and also provides a pin code.

Phases Planning:
1. 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. 2. The number of the reservation counters available to the passengers and customers are very less. 3. On most of the reservation systems there are long queues, so it takes a long time for any individual to book the ticket. 4. As now there are no call center facilities available to solve the queries of the passengers. 5. In Online Railway Reservation System, for booking the tickets online the intended user has to enter details like username and password. 6. Once the username and passwords are verified then he is allowed to enter the main system wherein he can select the destination, date and no of tickets. 7. For the purchase of the tickets he is asked for payment details (like credit card details etc.). 8. The user is also provided with a provision of canceling the reservation where in the entire amount is credited back to his account. 9. We have to design a website for user interaction, a database and then link both of these to work together. 10. 6 month time period is given for the successful development and implementation of this system.

Risk Analysis Phase:

1. Actual development time is 4 month but chosen 6 month to avoid some unusual situations like unavailability of senior developer due to some reason, emergency leaves etc. 2. Hired an assistant software developer who can handle the development process and monitor activities of staff in the absence of senior developer. 3. Take back up of files regularly because if the system on which we are developing the software crashes, we should have backup to save our work and continue it, instead of starting again from scratch. 4. Understand the requirements of railway system very carefully to develop the right system. 5. Discuss requirements with ticketing department of railway regularly to avoid developing wrong design. 6. Design prototype of model and show it to ticketing department of railway to check it whether we are developing it according to their requirement or not? 7. If not then modify according to requirement otherwise continue with that prototype.

 Engineering Phase:
1. For the website of company, well use .Net language on which well design layout of website then code it for the behavior of the website. 2. First well design a prototype of website how it will look and will show it to the company if they satisfy then continue with it. 3. Otherwise modify according to requirement. 4. Then implement (sample) it over the web and test it through different methods. 5. Then well use SQL server for the database of records. 6. Here also well design prototype and test it through different inputs. 7. Then well attach it with the website and then will test it as a whole. 8. Well ask all our team to test it through different inputs. 9. Then well ask staff members to test it according to their requirement.

Evaluation Phase:
1. After engineering phase, refine the prototype and remove the errors. 2. The project will be tested on the basis of the refined prototype. 3. As explained above, before continuing to the next spiral well discuss it with the railway staff. 4. Modifications will be done in routine. 5. Customer evaluation is also important. 6. It is important because of to prevent large scale failure.

Requirement Specification
Software Requirement: Sql Server 2008 for Database. .Net Framework 3.5 Windows Operating System (XP/Server)

Hardware Requirement: Printer Pentium-4 OR Above PC Key Board Mouse/Pointing Device

Security Specifications
As a security point of view, authentication and authorization will be done by password checking. If correct password has been entered by the user, the user will get further access to the system, otherwise he will have to re-enter the password. The facility to change the password has also been provided but for that the user will have to first enter the old password. The password can be eight characters long.

Data Flow Diagrams

The data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data moves from input to output. The DFD may be used to represent a system or software at any level of abstraction. In fact DFD may be partitioned into levels that represent increasing information flow and functional detail.

Level-0 DFD
The level 0 DFD or a context model represents the entire software element as a single entity with input and output data indicated by incoming and outgoing arrows, respectively. In the following level-0 DFD, the passenger fills either the reservation or cancellation form as input. He gets the ticket as the output and the report is sent to the administration.

Fill Cancellation Form

Passenger

Fill Reservation Form Ticket Info

Railway Reservation

Res/Cancel Info Passenger Info Waiting Info

Admin

Why Spiral 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. And we have to deliver it in increments and alterations are needed again and again because perfect software cant be made in first attempt increments and changer are needed again and again.

Spiral Diagram

Risk analysis Prototyping

Project Code

Coding

Customer Evaluation

Testing

Coding
Class:

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();

Case Diagram

Enter user id & password

Verify Password & User Id

System

Make a Reservation

Use r
Verify Payments

Update Reservations

Cancellation of Reservation

Administrator

Sequence Diagram

User Log in

System

Administrator

Secure communication Enter date Request confirmation Enter desired destination Choose desired express Enter the no of tickets Request confirmation Confirm purchase

{Verify user}

{Verify date}

{Verify funds}

Place order {Execute order}

Activity Diagram

Verify credit cards detail

(Invalid) (Success)

Debit account Send invalid notice Settle transaction

Send confirmation

Close transaction