RAILWAY TICKET RESERVATION SYSTEM PROJECT REPORT

RAILWAY TICKET RESERVATION SYSTEM PROJECT REPORT

PROJECT REPORT

RAILWAY RESERVATION SYSTEM PROJECT REPORT

PROJECT SOURCE CODE

RAILWAY RESERVATION SYSTEM PROJECT SOURCE CODE IN JAVA

RAILWAY RESERVATION SYSTEM PROJECT SOURCE CODE

FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

ABSTRACT

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 72 hours and distance upto several thousand kilometers.

In the given project we will be developing a website which will help users to find train details, book and cancel tickets and the exact rates of their tickets to the desired destination.

With the help of online booking 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.

INDEX

1 INTRODUCTION

1.1 General Overview………….

1.2 Survey ………………………

1.3 Objectives…………………..

1.4 Analysis……………………..

1.5 Organization of the report………..

2 SOFTWERE REQUIERMENT SPECIFICATION

2.1 Development environment……………….

2.2 Operating environment……………………

3 DESIGN

3.1 Design specification……………….

3.2 Data flow diagram………………..

3.3 ER diagram…………………………

4 SDLC

4.1 Waterfall model……………………..

4.2 Development Schedule…………….

5 IMPLIMENTION DETAILS

6 RESULTS AND DESCUSION

7 SUMMARY AND CONCLUSION

8 BIBLIOGRAPHY

INTRODUCTION

1.1 General Overview

Our website has various kinds of information that helps regarding booking of tickets via railways .

Users will be able to search the train availability ,the exact fare ,the arrival and departure time of the train and they can also book the ticket by using the debit ,credit or master card and after booking the ticket if the user want to cancel it then they can easily do it also.

1.2 Survey

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.

The online railway ticket reservation system aims to develop a web application which aims at providing trains details, trains availability, as well as the facility to book ticket in online for customers.

So, we thought of developing a web based application which would provide the users all these facilities from his terminal only as well as help them in booking their tickets. The Application was to be divided into two parts namely the user part , and the administrator part. And each of these has their corresponding features.

We decided to give the name of the website “ONLINE RAILWAY TICKET RESEVATION”.

The online railway ticket reservation system is developed using ASP.NET with C# as the backend in the .NET Framework.

1.3 Objectives: RAILWAY TICKET RESERVATION SYSTEM PROJECT

The objective of the online railway ticket reservation system

Project is to design software to fully automate the process of issuing a railway ticket. That is:- 1. To create a database of the trains 2. To search the trains it’s arrival and departure time,distance between source and destination.

3.To check the availability of the ticket. 4. To calculate fare.

5.To book the ticket.

6.To cancel the ticket if necessary.

1.3 Analysis

Online railway ticket reservation is a online ticket booking website, which is capable of booking ticket and serach the train availavility . This website is mainly created to fulfil the following requirements, it comprises of the following properties:-

 A central database that will store all information.

 An online website that will provide real- time information about the availability of tickets their prices .

 Every registered user is able to view his booking id that has been made in his/her name.

 Every registered user can change his password any time he wants to change.

 Every guest user can search train availability ,price of the ticket,arrival and departure time ,distance between source and destination etc.

 Every registered user has the facilities to print his ticket any time he wishes.

Administration login

 In admin mode the administrator can make changes in train details.

 He can also view all booking that has been made by different users.

 The booking window contains all the facilities at one place, the user can simply login to his account and can book his ticket.

The report has been organized into seven sections, each section dealing with a different aspect of project and its development. A brief overview of each of the section is in order.

The Software Requirements Specification section will deal with the technical details of the proposed system. It will contain information regarding the developmental and operational environments, user interfaces, functional and requirements specifications and the exception and error handling features of the system.

The Design section will provide a detailed insight into the working of the system, how the system to be framed to make the implementation error free and to avoid a possible rework. All the features mentioned in the SRS section will be dealt with in detail through the means of architectural design, block diagram, detailed data flow diagrams, structure charts, flow chart and any other relevant method.

Through the use of pseudo-codes, the Implementation Details section will provide the final design step before actual implementation of the system. It will list all the functions that will be used in the system, parameters used by them, what results they will produce and how they will interact with the rest of the system.

All queries regarding the actual performance of the developed system will be cleared in the Results and Discussion section. It will list all the test cases, results of those tests and a discussion on whether these tests yielded the desired results or not. If negative, this section will also provide information regarding the failure.

Concluding all this will be the Summary and Conclusion section which will round up the entire discussion.

This will be followed by the Reference/Bibliography section that will tell about the books and site that have been referred by us while developing the website.

2. Software Requirements Specification - RAILWAY TICKET RESERVATION SYSTEM PROJECT

2.1 Development Environments

Hardware

Intel core 2 duo T6400 2.00 GHz with 2GB RAM, 250 GB hard disk space and other Standard accessories.

Environment and Applications:

 Microsoft Windows 7.

 Microsoft Visual Studio 2010.

 Microsoft SQL Server 2005.

 Microsoft Internet Explorer.

2.2 Operating environment:

Hardware configuration:

The minimum configuration for hardware is given below:

 Intel® Pentium® or higher processor.

 65 MB RAM or higher

Software configuration:

 Microsoft® Windows® XP or later versions

 A standard web browser.

 .Net framework.

3. DESIGN

3.1

4. SDLC (Software development Life Cycle) - RAILWAY TICKET RESERVATION SYSTEM PROJECT

Every activity has a life cycle and software development process is not an exception for the same. Even if you are not aware of SDLC you still must be following it unknowingly. But if a software professional is aware about SDLC he can execute the project in a much controlled fashion. One of the big benefits of this awareness is that hot blooded developers will not start directly execution (coding) which can really lead to project running in an uncontrolled fashion. Second it helps customer and software professional to avoid Confusion by anticipating the problems and issues before hand. In short SDLC defines the various stages in a software life cycle. But before we try to understand what SDLC is all about. We need to get a broader view of the start and end of SDLC. Any project started if it does not have a start and end then its already in trouble. It’s like if you go out for a drive you should know where to start and where to end or else you are moving around endlessly.

Below is the figure that shows typical flow in SDLC which has five main models .

· Waterfall - Big Bang and Phased model .

· Iterative - Spiral and Incremental model.

Iterative model

Iterative model was introduced because of problems faced in Waterfall model.

The iterative waterfall model is used in the development of the system. The system is developed in increments, each increments adding some functional capability to the system until the full system is fully implemented.

The advantage of this approach is that it will result in better testing, as testing of each increment is easier than testing the entire system in totality. Furthermore, this approach provided us with important feedback that was very useful in the implementation of the system.

Feasibility Study

Integration and System testing

Requirement analysis and specification

Coding and unit testing

Design

Maintenance

Development Schedule

The work on the proposed ONLINE RAILWAY TICKET RESERVATION was started on 17th June, 2011 and it was estimated to be over by 17th of Augusest, 2011.

The following Gantt chart has explained the estimated duration of the different phases of the software development work diagrammatically:

Activities

.

4.1 Implementation Details

4.1.1 System Overview

Online railway ticket reservation system is a web based application. It has been developed using ASP.NET and C# as the code end programming language. A MS SQL Server database consisting of multiple tables is used for data storage.

This Website is a online travel booking website, which is capable of booking tour of national and international destination with easy steps at the cheapest rate . It allows the Administrator to perform all operations and view bookings. The general user is however given only restricted access.

Travelmasti helps in booking tour packages. The user can’t book any tour until he is a registered user.

Feasibility Study

Requirement gathering and specification

Database Design

GUI Design

Code database part

Code GUI part

Unit & System testing

17th-30th june

1st -15th july

25th -5th auguest

5th-17th auguest

16th-25th july

4.1MySQL

MySQL server: -  RAILWAY TICKET RESERVATION SYSTEM PROJECT

MySQL server is basically a database server which is mostly used for storing user data into the required database in a specific table for easy access of these data in the future. The database server works when a local application invokes it. Before storing data into a database with the help of database server, PHP sends a SQL query to MySQL database server for establishing a connection to the server by using the loopback address, i.e., 127.0.0.1 along with the user name and password for getting authentication from the database server. Since connection is established locally with the database server by PHP, so there is no chance of getting access to database server for modifying database by the client. Also , when PHP request for information retrieval from the database server by sending SQL query then the database server sends back the result of query after executing it by the database server. Another method of accessing database server is only possible by locally, i.e., only administrator of that particular computer can get all the access facilities of the database server as well as all the database which are not available to restricted users. PHP can update information in the database server if it has the administrator username and password to access thespecific database, otherwise connection will be rejected by MySQL server and the database cannot be updated.

Since before the dawn of the computer age , people have been using databases. Before computers, a database may have been a Rolodex containing phone numbers of the important people you knew, or it was a filing cabinet that contained all the personnel records for the company. Today, databases are computer-based and are found virtually everywhere. From desktop databases of your record collection to Web-enabled databases that run large corporations.

4.1.1.2 EVOLUTION OF ASP.NET - RAILWAY TICKET RESERVATION SYSTEM PROJECT

The first beta version of ASP was code named denali. Denali allowed the developer to execute code within a web page. Advanced functions could be performed using ActiveX Data Objects. The next version of ASP was ASP 1.0, WHICH WAS available as an add-on IIS 3.0.In this version of ASP, ADO had had become faster and effective as compared with the previous version. The next version ASP 2.0, came as a part of windows NT 4.0. Now components were easier to build because of the introduction of Microsoft Transaction Server, which allowed the components to be a part of transaction. Then, ASP 3.0 was introduced which came along with windows 2000. In this version, Microsoft combined MTS with core COM into COM+ and included it as a part of windows 2000 itself.

The latest version, of ASP is ASP.NET. ASP.NET has come to us along with the .NET framework. ASP.NET is an object oriented server side scripting tool. Hence, it facilitates easy development of object oriented and granularized code.

Drawbacks of ASP

 VBScripts and JavaScript are the only two scripting languages available in ASP. These are basic non-typed languages. You cannot use strongly typed languages like Visual Basic or c++.

 ASP pages are interpreted. This makes their execution slower.

 ASP pages are very untidy. They are a spaghetti-like mixture of code. HTML and text.

 While creating a web application using ASP pages, the programmers and the designer had to work on the same life. The programmers had to write the code to provide required functionality and the designers too had to create the graphics and content, and all this had to be combined into a single file.

 In ASP, you have to write code to provide any functionality you require. For example, if you required any validations to be performed you had to write code for it to occur. A huge numbers of lines of code had to be written.

 Re-use of code was not given much focus in ASP. You could do it only by using the include statement.

 There was no debugging mechanism in ASP. You could debug ASP application only by using the response.write. This is very tedious and not very effective.

 In ASP, you had to stop the web server to install a new version of a DLL. DLL’S had to be registered in the registry to be available for usein an application. Moreover, the DLL registration process is a very complex one.

Advantage of ASP.NET

 ASP.NET supports strongly typed languages like VB, c#,and much more.

 ASP.NET pages get compiled instead of being interpreted, thus their execution speed is faster than ASP pages.

 ASP.NET pages are tidier than ASP pages. The code can be separated from the HTML design and text. Thus, programmers can work separately from the designers.

 ASP.NET provides server controls that are declarative. You just have to declare them and you can use them. Thus, the number of lines of code to be written is reused.

 ASP.NET supports re-use of code by the mechanism of inheritance. For example, you can inherit c# classes and use them to provide the required functionality.

 ASP.NET has an inbuilt method called Trace, which helps you in debugging a page. You can either display the trace information at the end of the page or re-direct it to another location to check later.

Features of ASP.NET

 ASP.NET can recognize the type of browser the client is using and accordingly display the content to the client. For example, if the client uses an uplevel browser (ie> 4.0 version), then the validation is performed on the client –side and on the server-side. However, if the client is using a downlevel browser, then the validation is performed only on the server-side.

 ASP.NET improves performance by using server-side caching. It allows you to cache the entire output of a page for re-use by other clients.

 ASP.NET functionality can be coded using different languages like C# or VB.NET. However, only one language can be used for coding in a single page.

 ASP.NET ships with many built –in server controls that have the common required functionalities. For example, the developer need not create a control for accepting data; the textbox control is provided for this purpose. Thus, the developer need not to recreate these controls to obtain the required functionality.

 A web service can be described as a function that can be deployed over the web and can be called by any application or other services. It can be a business application or a system function. ASP.NET allows you to create such web services.

Minimum Requirements

The software requirements to successfully run all the programs are

• Operating System - Windows 7, Windows XP.

• Microsoft IIS WEB server 5.0

• SQL Server 2005

• Visual Studio 2005

Database Tables

The following tables were created for the application:

Table Name

Description

Train details

Store details of each train

Booking

Stores details of user and particular train

Bank

Stores the details of all banking information of user while booking a ticket.

High-level Diagram

Following is a high-level diagram depicting the overall working of the system:

Basic System Architectural Design

The system has a three level architecture:

 The first level (front end) uses ASP.NET technology with C# at the code end, to provide the users with the front-end.

 The lower lever (back end) uses MS SQL Server to house the database.

 The middle level comes into play only when Available tours are to be searched. This is achieved through the use of Active X Components (Data Grid). This picks up the requisite data from the database (depending upon the tours available and any other required conditions) and uses them to show the available tours.

5. Results and Discussions

5.1 Test Results

5.1.1 Unit Tests

Starting from the bottom the first test level is "Unit Testing". It involves checking that each feature specified in the "Component Design" has been implemented in the component.

In theory an independent tester should do this, but in practice the developer usually does it, as they are the only people who understand how a component works. The problem with a component is that it performs only a small part of the functionality of a system, and it relies on co-operating with other parts of the system, which may not have been built yet. To overcome this, the developer either builds, or uses special software to trick the component into believe it is working in a fully functional system.

The summary of unit tests is provided below:

For User:

UNIT

PURPOSE

VERIFIED

Search Train

This unit search the trains.

Yes

Train details

This unit shows the trains of a particular source to destination in a particular date and a specific seat .

Yes

Book ticket.

This unit user can select a particular train and book ticket .

Yes

Login.

This unit login the registered user and create an account for a new user.

Yes

Fill the booking form.

User fill the form to book ticket.

Yes

payment.

User fill the form and pay the money with the help of credit card.

Yes

Ticket no

This unit allows to show his ticket no.

Yes

Cancel ticket

This unit allows user to cancel ticket.

Yes

For Administrator

UNIT

PURPOSE

VERIFIED

Administrator Login

This unit detects the authorization of the Administrator.

Yes

Change the train details

This unit allows the administrator to change the train details.

Yes

Integration Testing

As the components are constructed and tested they are then linked together to check if they work with each other. It is a fact that two components that have passed all their tests, when connected to each other produce one new component full of faults. These tests can be done by specialists, or by the developers.

Integration Testing is not focused on what the components are doing but on how they communicate with each other, as specified in the "System Design". The "System Design" defines relationships between components.

The tests are organized to check all the interfaces, until all the components have been built and interfaced to each other producing the whole system.

Thus this test was successfully done. No conflicts or inconsistencies were detected.

System Testing

Once the entire system has been built then it has to be tested against the "System

Specification" to check if it delivers the features required. It is still developer focused, although specialist developers known as systems testers are normally employed to do it.

In essence System Testing is not about checking the individual parts of the design, but about checking the system as a whole. In fact it is one giant component.

System testing can involve a number of specialist types of test to see if all the functional and non - functional requirements have been met. In addition to functional requirements these may include the following types of testing for the

non - functional requirements:

· Performance - Are the performance criteria met?

· Volume - Can large volumes of information be handled?

· Stress - Can peak volumes of information be handled?

· Documentation - Is the documentation usable for the system?

· Robustness - Does the system remain stable under adverse circumstances?

The system was found to perform its function properly under all conditions.

Acceptance Testing

Acceptance Testing checks the system against the "Requirements". It is similar to systems testing in that the whole system is checked but the important difference is the change in focus:

Systems testing checks that the system that was specified has been delivered. Acceptance Testing checks that the system will deliver what was requested.

The customer should always do acceptance testing and not the developer. The customer knows what is required from the system to achieve value in the business and is the only person qualified to make that judgment. This testing is more of getting the answer for whether is the software delivered as defined by the customer. It’s like getting a green flag from the customer that the software is up to the expectation and ready to be used.

Figure 1.4: - V model cycle flow

5.1.2 Result

Online railway ticket reservation system was successfully designed and developed as per the specifications. It was extensively tested using a database which contains data similar to what can be expected in an actual database. The system was found to work satisfactorily without any errors under all conditions.

6. Summary and Conclusions

6.1 Summary of Achievements

The following achievements were made during the project:

 We had the opportunity to learn a new technology ASP.net

 Learned to work in visual studio 2010.

 We learned to handle a project efficiently and correctly.

 Learned to tackle various adverse situations while managing and developing software.

 Learning about the functioning of the IT industry and work ethics in the corporate world.

 Learning to work with C#.NET and MS SQL Server 2005.

 Learning about the different phases of software development and the software engineering processes involved in the development of software.

6.2 Main difficulties encountered

 The main difficulty that was encountered during this project was that we had to learn a new technology ASP.net as well as a new language C# with which we were not at all familiar with earlier .

 Time constraint.

 Learning the use of triggers.

6.3 Limitations of the Project

 Print ticket option is not provided here.

 Ajax could not be used.